Skip to content

chore(routines): autonomous maintenance catch-up — 7 routines (111 days overdue) - #219

Open
LastStep wants to merge 1 commit into
mainfrom
claude/routine-maintenance-2026-08-26
Open

chore(routines): autonomous maintenance catch-up — 7 routines (111 days overdue)#219
LastStep wants to merge 1 commit into
mainfrom
claude/routine-maintenance-2026-08-26

Conversation

@LastStep

Copy link
Copy Markdown
Owner

Summary

Autonomous bonsai-loop cloud routine ran all 7 overdue maintenance routines (last run 2026-05-07, 111 days ago). 7 reports written to station/Reports/Pending/. No application code changed — all edits are workspace docs (Backlog, Status, memory, routines dashboard, logs).

Changes

  • station/agent/Core/routines.md — dashboard updated: all 7 rows refreshed with today's Last Ran / Next Due dates
  • station/Logs/RoutineLog.md — 7 new log entries appended
  • station/Playbook/Backlog.md — 3 resolved items removed (Plans 37/38/41 post-ship)
  • station/Playbook/Status.md — stale Pending item flagged; Plans 40/41 cross-ref noted
  • station/Playbook/StatusArchive.md — 6 done rows archived (Plans 32–37, dated Apr–May 2026)
  • station/agent/Core/memory.md — 6 stale Research/ references marked outdated
  • station/Reports/Pending/2026-08-26-*.md — 7 new routine reports (one per routine)

Test Plan

Routine-only change — no Go code modified. No build or test steps apply.

  • All 7 routines executed and dashboarded
  • station/agent/Core/routines.md dashboard verified updated after each run
  • Reports confirmed written to station/Reports/Pending/
  • RoutineLog entries confirmed appended

Checklist

  • make build passes — N/A (no Go changes)
  • gofmt -s clean — N/A (no Go changes)
  • Tested affected commands manually — N/A (doc-only)
  • Updated docs if behavior changed — docs ARE the change

Action Items for Morning Review

These items were flagged and require human decisions — ranked by urgency:

🔴 CRITICAL

  1. HOMEBREW_TAP_TOKEN PAT expired — reminder date was 2026-07-15; token has almost certainly expired. Rotate in LastStep/Bonsai repo secrets immediately or the next release will fail at the Homebrew publish step with 401 Bad credentials.

🟠 HIGH

  1. 8 npm CVEs in website/ — 7 high-severity (astro v6.1.7: SSRF CVSS 7.5, XSS CVSS 7.1; js-yaml: quadratic DoS) + 1 low. Primary fix: evaluate npm install astro@7.2.8 (major version — prior audit flagged build-breaking risk on rebase). Confirmed via npm audit; cross-referenced by both dependency-audit and vulnerability-scan reports.

🟡 MEDIUM

  1. Plans 40 and 41 in Plans/Active/ — both shipped; move to Plans/Archive/ (git mv).
  2. Research/ directory missing — 6 memory references point to station/Research/ files that no longer exist. Restore, correct paths, or remove the reference block.
  3. MCP server (Plan 42) not in Roadmap Phase 3 — Status.md calls it the fast-follow to Plan 41 (shipped); roadmap doesn't reflect it.
  4. internal/nonint/ missing from INDEX.md and code-index.md — significant navigation gap for upcoming MCP work.

🔵 LOW / INFO

  1. Sentrux trial stalled 111 days — either install rustup and run it, demote to Backlog P3, or close.
  2. Phase 2 roadmap items may be superseded — self-update, template vars expansion, micro-task fast path have had no active plans in 111 days; confirm still on-track vs. headless/MCP direction.
  3. govulncheck / semgrep / gitleaks not installed — Go vuln scan ran on heuristics only; recommend go install golang.org/x/vuln/cmd/govulncheck@latest as minimum.
  4. 32 Go modules behind latest — no confirmed CVEs, but hygiene debt widening.

Generated by Claude Code

…1 days overdue)

Ran all overdue routines via bonsai-loop cloud dispatch (2026-08-26).
7 reports written to station/Reports/Pending/.

Key findings:
- CRITICAL: HOMEBREW_TAP_TOKEN PAT likely expired (due 2026-07-15) — rotate before next release
- HIGH: 7 npm CVEs in website/ (astro SSRF+XSS, js-yaml DoS) — needs astro v6→v7 upgrade decision
- Backlog cleaned: 3 resolved items removed (Plans 37, 38, 41 post-ship entries)
- Status archived: 6 done rows moved to StatusArchive
- Roadmap gap: MCP server (Plan 42) not represented in Phase 3
- Doc gap: internal/nonint/ missing from INDEX.md and code-index.md
- Plans 40 and 41 still in Active/ — should be archived
- Research/ directory absent — 6 memory references marked stale

Copy link
Copy Markdown
Owner Author

CI failure: govulncheck — not caused by this PR

The govulncheck check is failing, but this PR contains only doc changes in station/ — no Go code, go.mod, or go.sum was modified. The 4 CVEs it found are pre-existing in the Go dependencies on main (all published after the last main push on 2026-06-16, first surfaced now because govulncheck runs on PR heads but not on direct main commits):

# ID Package Found Fixed in
1 GO-2026-6218 net/url (stdlib) go1.25.9 go1.25.13
2 GO-2026-6088 encoding/xml (stdlib) go1.25.9 go1.25.13
3 GO-2026-5970 golang.org/x/text v0.36.0 v0.39.0
4 GO-2026-5320 github.com/yuin/goldmark v1.7.13 v1.7.17

Proposed fix (separate PR or squashed into this one — your call):

# Bump Go toolchain in go.mod (go1.25.9 → go1.25.13)
go get go@1.25.13

# Update vulnerable modules
go get golang.org/x/text@v0.39.0
go get github.com/yuin/goldmark@v1.7.17

# Tidy
go mod tidy

This is a dependency-only change with no functional impact. Goldmark v1.7.13→v1.7.17 and x/text v0.36.0→v0.39.0 are patch/minor bumps; the Go toolchain bump is a patch release. None of these change any API surface Bonsai uses.

I'll keep the PR watched. When the dep fix lands on main (or gets merged here), CI will go green.


Generated by Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

2 participants