Skip to content

Board round 2: readiness deepening, dev-box publish leg, autonomy strip, trend - #256

Merged
Jammy2211 merged 1 commit into
mainfrom
claude/pyautobrain-dashboard-o33z4r
Aug 23, 2026
Merged

Board round 2: readiness deepening, dev-box publish leg, autonomy strip, trend#256
Jammy2211 merged 1 commit into
mainfrom
claude/pyautobrain-dashboard-o33z4r

Conversation

@Jammy2211

Copy link
Copy Markdown
Contributor

The health/hygiene follow-ups from the human's review ("should health and hygiene have dashboard entries… more of the brain could be on the dashboard?"), all on the compose-don't-recompute rule:

  • Readiness & release — the section consumes the Heart's newly published board.json (Publish the machine surface (board.json) to Pages PyAutoHeart#160, merged): the top structured blockers render verbatim, each chip being the blocker's own /bug prompt; the Hands badge headline joins as the "shipped" line; and a ⏸ blocked-gate overnight row prints its ::warning annotation inline (no more clicking into the run to learn why the night blocked).
  • Dev boxpyauto-brain board publish (board/_publish.py, on the Heart's heart/publish.py pattern): distills the hygiene conductor's own --json pre-scan rows plus worktree state (off-default branches, unpushed, dirty, stashes — repo names only, home paths collapsed to ~) into state/devbox_board.json; main-only guard, rebase-retry push; brain_board.yml gains a push trigger on that file so the board republishes a minute later. bin/morning.sh runs it as its last step (--no-publish to skip), so the board reads "observed this morning" every day. Observations go stale at 48h and drop at 7d.
  • Autonomy strip — the tail of the Mind's autonomy_log.md, verbatim.
  • Trend — a "N need you" sparkline in the header; history is self-carrying (each render reads yesterday's published board.json, appends today, caps at 30 — no commits, no extra state).

Validation: 421 tests pass (6 new: blockers rendered verbatim with own-prompt chips, gate annotation inline, devbox fresh/expired, publish dry-run scrub, publish push/idempotence/main-only guard — the publish tests run against a fabricated repo with a bare origin); tenant-firewall gate green; real-workspace publish --dry-run verified.

Companion changes: PyAutoHeart#160 (merged) publishes the machine surface; PyAutoMind PR updates the follow-ups prompt to the remainder.

🤖 Generated with Claude Code

https://claude.ai/code/session_019U2DF4JeeuWwxfx1v72c9r


Generated by Claude Code

…nomy strip, trend

Readiness & release: the section now renders the Heart's structured
blockers verbatim from its newly-published board.json (each chip is the
blocker's OWN /bug prompt — composed, never re-derived), the Hands
badge headline joins it, and a ⏸ blocked-gate row prints its ::warning
annotation inline so the morning glance needs no click.

Dev box: `pyauto-brain board publish` (board/_publish.py, the Heart's
heart/publish.py pattern) distills the hygiene conductor's own --json
pre-scan plus worktree state (off-default branches, unpushed, dirty,
stashes — names only, home paths collapsed to ~) into
state/devbox_board.json: main-only guard, rebase-retry push, and
brain_board.yml republishes on that push. morning.sh runs it as its
last step (--no-publish to skip), so the board reads 'observed this
morning' every day; observations go stale at 48h and drop at 7d.

Also: the autonomy log's tail renders as a section, and the header
carries a self-carrying 'N need you' trend sparkline (yesterday's
published board.json hands its history forward — no commits, no state).

421 tests pass (6 new: blockers verbatim + own-prompt chips, gate
annotation inline, devbox fresh/expired render, publish dry-run scrub,
publish push/idempotence/main-guard); firewall gate green.

Co-Authored-By: Claude <noreply@anthropic.com>
@Jammy2211
Jammy2211 merged commit 183eb6f into main Aug 23, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants