Repository navigation
Conversation
… tab focus The report stacked four reports on one long page. It is now tabs in the sticky bar: Overview (current stage, project KPIs with Changes waiting, stage rail), Build, Changes (new: the PROJECT.md Change log as a backlog, with status counts and the plan rows that name each CR), Performance (session totals, time, context, tokens, sub-agents), Pages (the project's HTML pages) and "Notes, tips and bugs". Without JavaScript every section shows on one page, as before. The chosen tab survives the 30 s reload, a link into a hidden tab switches to it, and Show all puts everything back on one page for searching and printing. Bugs: "Encountered bugs or limitations" in the Notes tab, from docs/bugs.jsonl. An open bug gets buttons that copy its file-bugs.sh command (one per repo); the person runs it, which redacts, searches for duplicates, asks y/N and files with gh. Nothing is posted from the page. file-bugs --to files the same finding to the other repo too; the row keeps its target and the second URL goes under also.<repo>. Without gh or a GitHub login --file exits 0, posts nothing and names the way out. Build tab: the phase being built (open) and the three unfinished phases with the most recent built rows as cards; other unfinished and completed phases fold into two groups. A link to a phase opens its group. Rebased onto master (squashed from six local commits). Merged with master's newer report: - top bar (#479): master's section links (Stages, Build, Pages) stay as the bar without JavaScript; the tab bar replaces them once the script runs. No stage chips; the current stage stays in the header. - one plan view (#474) and module sign-offs (#526): the phase cards keep phase_bar, sign-off lines and --phase-detail rows inside the focus/fold layout; the plan tables stay master's open section. - master's phase accordion (one phase open at a time) is kept next to the tab switch and the open-every-enclosing-details link handling. - unique ids and data-stamp lines (#479) kept, fold groups get ids so a reload keeps them open. - Project pages (#472) is its own tab. Tests: polish P7 (#479) reads the section links outside the tab bar and checks the tab list; P6c compares the set of cards (P10 pins the order); the branch's tests are renumbered P8-P10; the accordion count strips wc -l padding (failed on macOS on master too); harness-verify N5 reads each badge by phase id. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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.
What the tabs do
The progress report was four reports stacked on one long page. Now it has tabs in the sticky bar:
(part: ...).docs/bugs.jsonl. Each open bug gets buttons that copy itsfile-bugs.shcommand, one per repo. The person runs that command, which redacts, looks for duplicates, asks y/N and files throughgh. The page itself never posts anything. The method notes are folded at the bottom.Without JavaScript every section shows on one page, as before. The chosen tab survives the 30 s reload. A link into a hidden tab switches to that tab first. Show all puts everything back on one page for searching and printing.
file-bugs --to mxcli|toolkitalso files the same finding to the other repo. The row keeps its target and the second URL goes underalso.<repo>. Withoutghor a GitHub login,--fileexits 0, posts nothing and names the way out (gh auth login, or--links).How the conflicts with master were resolved
The branch was 6 local commits behind ~61 master commits. I squashed it to one commit and rebased that, so each conflict was resolved once instead of once per commit.
<nav>, and once the script runs,body.tabbedhides the plain links. Neither version has stage chips any more. The current stage stays in master's header line.openTargetthat switches tab and opens every enclosing<details>, combined with master's phase accordion (one phase card open at a time, single toggle handler). The IntersectionObserver for stage chips is dropped because master removed the chips.card()and its focus/fold layout now render master's card body (phase_bar, sign-off lines,--phase-detailrows). The plan tables stay master's open<section id=plan-tables>, and master's plan note with the sign-off rollup is kept. The fold groups get ids (fold-rest,fold-done) so a reload keeps them open.data-stamplines are kept, including the footer'srebuildnoteline. The footer is the branch's folded version.--phase-detailparse and the branch'sload_bugs.Test changes from the merge:
wc -l. This check failed on macOS on master too, 52/53.test-progress-harness-verify.shN5 reads each phase badge by phase id instead of page order.Tests (macOS; the master column is a clean origin/master worktree)
I also rendered the pages in headless Chrome to look at them: the tab bar, Build focus/folds, and the Notes tab with bugs.
#build-detailand#bugslinks switched to the right tab.Known gap: a phase made only of HARNESS sign-off rows (no build rows) never counts as "completed", so it shows among the unfinished phases.
🤖 Generated with Claude Code