complete: board-github-data-seam (PyAutoBrain#303) - #357
Merged
Conversation
PyAutoBrain#305 merged as ef887f8; issue #303 closed. Record written, prompt folded out of active/, complete/index.md refreshed (1163 records), dashboard regenerated and --check current. The board takes --github-data now: {endpoint: response}, keyed by the endpoint string exactly as gh_json() receives it, so a gh-less session's agent can fetch and hand the renderer what a subprocess cannot reach. Proved on the surface it exists for — one injected endpoint rendered a live overnight row in a session with no gh, while the uninjected legs still read "could not read". Sweep: phase 2's Blocked-by pointed at the phase-1 prompt, which this commit folds into the record, and the parent's Split-into named the same path. Both repointed at complete/2026/08/board-github-data-seam.md rather than left dangling. `intake reconcile draft/feature/pyautobrain`: 0 suspects of 134. No worktree to remove — this shipped from a remote session. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016c1SLkLDW6aEZCVf95XXeu
…dispatchable Both close-out PRs this session (#354, #357) showed zero check runs at open, on diffs matching three path filters plus spawn_drift.yml, which has none. The 2026-08-26 record logged this as a one-off GitHub-side miss; at two occurrences it belongs in the record as a repeatable condition, with what actually works. The part that is not obvious and cost a detour: of the four workflows, only firewall_gate.yml can be dispatched to verify a branch. lifecycle_drift.yml and dashboard_refresh.yml self-heal main on a manual dispatch — they reset to origin/main and push — so dispatching them says nothing about the branch and writes to main. Their commands run locally instead. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016c1SLkLDW6aEZCVf95XXeu
Main moved (PyAutoMind#355/#356). Both conflicts were in the GENERATED dashboard pages, resolved by regenerating from the merged sources with `intake --apply dashboard` rather than by picking hunks; complete/index.md auto-merged. No source-of-truth file conflicted. All gates re-run green after the merge: lifecycle check, lifecycle index --check, registry_toc --check, intake dashboard --check, 252 tests. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016c1SLkLDW6aEZCVf95XXeu
The merge brought two records in from main and left the index stale. The previous commit should have carried this: `index --check` did report DRIFT, and the shell chain ran on because the command was piped to `tail`, so the pipeline exited 0 and the `&&` never saw the failure. Worth naming rather than quietly fixing — it is the same shape as the probe defect this branch fixed this morning: a check that ran, reported, and had its answer discarded. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016c1SLkLDW6aEZCVf95XXeu
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Close-out for PyAutoLabs/PyAutoBrain#303 — PR PyAutoLabs/PyAutoBrain#305 merged as
ef887f8, issue closed.What shipped
The Brain board takes
--github-data <file>—{endpoint: response}, keyed by the endpoint string exactly asgh_json()receives it.mcp__github__*is an agent capability and_board.pyis a subprocess, so the/boardskill fetches and the renderer renders; injected and live data are interchangeable by construction, and theghpath is untouched.Proved on the surface it exists for — a session with no
gh: one injected endpoint rendered✓ PyAutoLabs/PyAutoBrain/nightly-release.yml — success (6h)while the six uninjected legs still readcould not readand the board stayed degraded and non-green.Mind state
complete/2026/08/board-github-data-seam.mdactive/;active.mdsection removedcomplete/index.mdrefreshed (1163 records)dashboard.md+dashboard.htmlregenerated,--checkcurrentSweep
Two references the merge falsified, both repointed rather than left dangling:
Blocked-by:named the phase-1 prompt this commit folds into the record → nowAfter: complete/2026/08/board-github-data-seam.md, and the phase is unblockedSplit-into:named the same path → repointed at the recordintake reconcile draft/feature/pyautobrain: 0 suspects of 134 scanned.No worktree to remove — this shipped from a remote session.
Validation
252 tests (
-n auto),lifecycle.py check,lifecycle.py index --check,intake dashboard --checkall clean.Generated by Claude Code