Daily Fro Bot Report — 2026-10-22 (UTC) #4037

Daily Fro Bot Report — 2026-10-22 (UTC)

Snapshot: 2026-10-22 04:26 UTC. Categories 1–4 are carried forward from the remediation handoff; this pass performed categories 5–8, report-only.

Run Summary

Errored PRs

None remaining. Prior-pass evidence records #4036 passing check runs and the separate legacy Private Leak Scan status before independent merge. Live open-PR inventory is empty; no repair PR or follow-up comment was produced.

Security

Remediation evidence and six advisory links: no high/critical package remediation required; moderate/low findings remain Renovate-owned. GitHub Dependabot returned 0 open alerts. Scorecard #9 is an aggregate high-severity policy signal, not proof of a high-severity package advisory. Sources in that pass: npm advisory data through Bun audit, GitHub alerts, GitHub Advisory Database Actions feed; fixed-range comparisons included cross-major fixes. Latest-version drift is assessed separately below.

Control-Plane Integrity

Prior-pass verification: 153 SHA-pinned/version-commented third-party references across 34 YAML files; 81 production scripts parse strip-only. Existing writer-freshness race needs coordinated design. Scratch release-tool locking finding and Review-policy finding remain design/operator-owned. Data deletion protection was verified active without bypass actors; do not repeat the superseded protection warning.

Code Quality

Prior-pass local validation: all four required commands exited 0; 111 test files, 5,795 passed, 43 skipped, 3 todo. Latest Main at 38b95a9 succeeded. No repository files changed in this report-only pass, so local project checks were not repeated.

Oversight

Enumeration used paginated authenticated /user/repos (owner, collaborator, organization-member affiliations), /user/orgs, and every returned organization’s /orgs/{org}/repos; read access means the repository was returned with pull/read access. No enumeration request failed. The public view below contains 40 repositories; pagination was followed for issues, PR timelines, HEAD checks and alert lists. Organizations: bfra-me, pro-actions.

New = created in the preceding 24 hours. Issue stale = no update for >30 days. PR aging = created >7 days ago; PR stale = >14 days since the latest PR update or commit/review/comment/state-change timeline activity. Ages are elapsed days, rounded down in link labels; thresholds use unrounded times. Default-branch checks and legacy statuses were read separately. Scheduled-workflow context uses the latest result per workflow in a bounded 100-run window; old failures are historical signals, not proof that today’s code fails.

Top three hotspots

Ranking counts unique qualifying issues/PRs, individual open security alerts, and failing Actions runs (jobs in one run count once); issue/PR overlap counts once. It does not multiply an aging PR by its labels. Counts describe this snapshot, not severity or distinct root causes.

• marcusrbrown/extend-vscode: 109 findings; 104 dependency alerts, 0 code alerts. Start with linked security finding; confirm affected paths and reuse the existing security-update work before routine backlog triage.

• marcusrbrown/sparkle: 72 findings; 55 dependency alerts, 0 code alerts. Start with linked security finding; confirm affected paths and reuse the existing security-update work before routine backlog triage.

• marcusrbrown/containers: 52 findings; 12 dependency alerts, 34 code alerts. Start with linked security finding; confirm affected paths and reuse the existing security-update work before routine backlog triage.

Issue findings

Each new issue: triage and identify an owner. Each stale issue: reconfirm relevance and record the next concrete step. Each unassigned bug: reproduce, then assign a maintainer. These recommendations apply to every linked item; no issue was modified.

Open pull requests

Review current checks and intent for each linked PR; prioritize aging PRs, and request a concrete next action for stale ones. A = creation age >7d; S = inactivity >14d. A recently updated old PR can be aging without being stale.

Failing default-branch signals

Inspect the linked failed job and its newest rerun before acting; for historical results, rerun against current main before diagnosing a current-code regression.

Security findings

Prioritize confirmed critical/high dependency advisories with the existing Renovate/security PRs. Triage code-scanning rules separately: Scorecard policy severity and package advisory severity are different signals. No individual alert was modified.

• Dependabot unavailable on 6 public sources: fro-bot/tokentoilet, marcusrbrown/copiloting, marcusrbrown/cortexkit_anthropic-auth, marcusrbrown/encode-2024-q3-grp14-jobseeker-ai, marcusrbrown/gala-chain-code, pro-actions/peter-murray_workflow-application-token-action. Responses were disabled/403 or 404 (including “no analysis found”); these are not clean readings.

• Code scanning unavailable on 25 public sources: bfra-me/github-app, fro-bot/fro-bot.github.io, fro-bot/systematic, fro-bot/tokentoilet, marcusrbrown/.dotfiles, marcusrbrown/.github, marcusrbrown/copiloting, marcusrbrown/cortexkit_anthropic-auth, marcusrbrown/dev-like, marcusrbrown/encode-2024-q3-grp14-jobseeker-ai, marcusrbrown/esphome.life, marcusrbrown/extend-vscode, marcusrbrown/gala-chain-code, marcusrbrown/gpt, marcusrbrown/ha-config, marcusrbrown/marcusrbrown, marcusrbrown/marcusrbrown.com, marcusrbrown/marcusrbrown.github.io, marcusrbrown/opencode-copilot-delegate, marcusrbrown/panthea, marcusrbrown/Presentations, marcusrbrown/sparkle, marcusrbrown/tokentoilet, marcusrbrown/vbs, pro-actions/peter-murray_workflow-application-token-action. Responses were disabled/403 or 404 (including “no analysis found”); these are not clean readings.

• Secret scanning unavailable on 33 public sources: bfra-me/.github, bfra-me/github-action, bfra-me/github-app, bfra-me/ha-addon-repository, bfra-me/renovate-action, bfra-me/renovate-config, bfra-me/works, marcusrbrown/.dotfiles, marcusrbrown/.github, marcusrbrown/containers, marcusrbrown/copiloting, marcusrbrown/cortexkit_anthropic-auth, marcusrbrown/dev-like, marcusrbrown/encode-2024-q3-grp14-jobseeker-ai, marcusrbrown/esphome.life, marcusrbrown/extend-vscode, marcusrbrown/gala-chain-code, marcusrbrown/gpt, marcusrbrown/ha-config, marcusrbrown/infra, marcusrbrown/marcusrbrown, marcusrbrown/marcusrbrown.com, marcusrbrown/marcusrbrown.github.io, marcusrbrown/mothership, marcusrbrown/opencode-copilot-delegate, marcusrbrown/panthea, marcusrbrown/Presentations, marcusrbrown/renovate-config, marcusrbrown/sparkle, marcusrbrown/systematic, marcusrbrown/tokentoilet, marcusrbrown/vbs, pro-actions/peter-murray_workflow-application-token-action. Responses were disabled/403 or 404 (including “no analysis found”); these are not clean readings.

• No HEAD check-run evidence: fro-bot/tokentoilet, marcusrbrown/encode-2024-q3-grp14-jobseeker-ai, marcusrbrown/gala-chain-code, pro-actions/peter-murray_workflow-application-token-action. Empty check lists do not prove CI health; see repository workflows before calling a job missing.

Cross-Project Intelligence

Partial coverage. Every named tracked entry in metadata/repos.yaml was attempted at its current default-branch SHA; this is not an example-subset scan. Matching workflow, manifest and guidance files were read without executing repository code. fro-bot/fro-bot.github.io and fro-bot/systematic returned no files in those source classes, so no automation pattern was inferred from them. marcusrbrown/copiloting was accessible despite its recorded lost-access state; reconcile that metadata only through the data-branch owner.

Adoptable findings (recommendations only):

• Dashboard exact-head checkout: PR jobs explicitly bind head repository + immutable head SHA and disable credential persistence. Evaluate the same explicit binding for this repo’s read-only CI checkout steps; retain fork and authority boundaries.

• Systematic decision/credential/attestation split: a read-only decision job emits the exact inspected SHA; credentialed jobs run no repository code, and publication re-verifies exact-head evidence. Reuse the separation/evidence binding for privileged handoffs; automated approval is not a recommendation for this repo.

• Infra cancellation readback: separate request acceptance from terminal cancellation with a bounded readback budget. Useful for control-plane dispatch, but its fail-open warning behavior cannot certify containment. Preserve the distinction documented in existing wiki guidance.

Progressive Improvement

Authoritative current-version source: npm registry latest endpoints, read during this pass. Major drift included. Comparisons use declared pins in package.json, not cached wiki versions.

• CI/conventions: Latest Main succeeded; main.yaml retains lint, types, tests, built-dist, strip-only, workflow validation, wiki-authority and conditional mutation lanes. The documented read-only private-leak scratch install remains intentional; do not replace it with lifecycle-enabled shared bootstrap. No newly missing/degraded main CI job identified; writer race #4031 remains the known convention-integrity issue.

• TODO/FIXME: no stale actionable source annotation found. Source matches were the oversight prompt wording and a synthetic leak-test fixture; wiki matches are historical survey prose, not deferred work in this control plane.

• Preserve the TypeScript hold: .github/renovate.json5:35–46 names the TypeScript 7 parser break and its lift condition. The authoritative parser registry metadata still excludes 7.x at version 8.72.0. Applied prior learning: docs/solutions/best-practices/dependency-holds-need-lift-conditions-2026-08-31.md.

• Compounding: open learning-proposal inventory = 0, ages = None. Open qualifying docs/drafted-solutions PRs = 0, ages = None. Latest drafted PR #4013 merged and closed Learning proposal: (e826ccb2) #4008. No 14-day/two-proposal stall signal; #3674 was not used as evidence of proposal health.

Gateway operator rollout tracker (category 8)

Compared the #3512 body, all 29 live Project 1 items, latest tracker comments, release/deployment evidence and live operator health. Drift remains:

Needs Human Attention

• Reuse #4031: full-file wiki handoffs currently attest the receiving sync SHA rather than the agent’s derivation snapshot. Coordinate .github/workflows/fro-bot.yaml, scripts/wiki-handoff-{baseline,build,apply,core}.ts, .github/actions/sync-wiki/action.yaml, packages/wiki-write-core/src/wiki-ingest.ts and scripts/wiki-repair.ts. Carry the derivation SHA end-to-end, distinguish absent data, reload retry state from current HEAD. Verify conflicting same-path writes refuse, disjoint writes survive, bootstrap races fail closed, and repair retries refresh state. Multi-file contract work exceeds the autoheal cap. Preserve privacy/authority gates; do not delete/reseed data, force-push or weaken dirty-tree refusal.

• Reuse agent#1889: operator “Cancelled” was followed by eleven minutes of execution/writes. The report establishes a containment gap, not its exact code-level cause. Trace packages/gateway/src/execute/cancel.ts, packages/gateway/src/execute/run-core.ts, packages/gateway/src/workspace-api/client.ts and apps/workspace-agent/src/opencode-proxy.ts; target explicit session-cancel propagation and confirmed teardown before reuse. After release/deploy verify execution and writes stop and the next launch succeeds without manual cleanup. Preserve dirty-tree refusal and human work; do not equate UI status or GitHub cancellation admission with containment.

• Tracker reconciliation: #3512 and Project 1 have the mismatches above. .github/workflows/gateway-rollout-tracker.yaml owns reconciliation. Keep credited approval/question/checkout/prompt-rendering/P7 passes; retain unobserved provider-quota presentation, real iOS cold-start/reconnect, timeout/idempotency, CSRF/logout invalidation and privacy/policy-unavailable gates. Verify against linked authenticated evidence, not health alone.

• Routine tool drift: package.json Vitest 4.1.11 trails 5.0.5; review Renovate-owned Vitest/coverage-v8/Stryker compatibility as one coordinated update. Verify types, lint, all tests, strip-only smoke and relevant mutation guards together. Do not open a non-security bump from this pass. Preserve .github/renovate.json5’s TypeScript <6.1.0 hold until the documented parser peer condition changes.

• Security visibility: unavailable sources are enumerated above. Recheck only with an appropriately scoped read credential or enabled analysis; 403/404/no-analysis is not zero alerts. Do not change organization settings or token scopes from this report path.

• Release tooling policy: Scorecard #45 points to .github/workflows/release-wiki-write-core.yaml:171; scratch tool versions, lifecycle disabling and release-age floor already exist. Any transitive-lock design must retain those guards and validate the release path. Review-count finding #1 is operator-owned policy.

Knowledge persistence: None — this snapshot adds operational evidence to already documented principles; no new durable wiki claim was warranted. knowledge/** and metadata/** remain untouched. No code delivery actions or individual oversight mutations performed.