feat(GETSITREP-51): read/report commands + fold dashboard into session-end - #19
Merged
Merged
Conversation
…old dashboard into session-end Adds three headless, read-only CLI commands layered on the existing plan adapters and cost rollup: `report` (cost-to-outcome summary from the persisted cost_rollup), `plan --phase N` (read-only phase view, source- agnostic), and `progress` (quick source-agnostic readout). All three surface which plan adapter supplied the data. Also folds dashboard regeneration into session-end (ADR-0007), gated by the same dashboardStaleTrigger threshold GETSITREP-35's nudge-check already uses, instead of leaving it fully manual (the exact drift that let 4 Stories go undocumented after Session 8) or regenerating on every session-end (commit noise). Exactly one commit per session-end call, verified by test/session-end-dashboard.js. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
viitorohit
pushed a commit
that referenced
this pull request
Jul 8, 2026
… commands) shipped, PR #19 merged; folded dashboard regeneration into session-end (ADR-0007), reusing GETSITREP-35's dashboardStaleTrigger threshold rather than leaving dashboard staleness fully manual or regenerating unconditionally. Separately discovered and resolved a parallel-session conflict: PR #18 had independently done its own Session 9 close-out before this session's own backfill landed on main; closed #18 as superseded, salvaged its one real fix (nudge-state .gitignore gap) as PR #20, merged.
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
1 participant
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.
Summary
report(cost-to-outcome summary from the persistedcost_rollup),plan --phase N(read-only phase view), andprogress(quick source-agnostic readout) — all surface which plan adapter supplied the data, per acceptance criteria.session-end, gated by the samedashboardStaleTriggerthreshold GETSITREP-35'snudge-checkalready uses (ADR-0007), instead of leaving it fully manual or regenerating unconditionally every session.session-endinvocation, regardless of whether the dashboard fold fires.Test plan
npm test— full suite green (byte-identical, cost-attribution, nudge-triggers, plan-adapters, agents-md, plan-commands, session-end-dashboard)report,plan,plan --phase N,progressagainst this repo's real dogfood dataplan --phase <unknown>,report --ticket <unknown>, external--plan-dataoverridetest/session-end-dashboard.jsverifies below-threshold (no dashboard write), at-threshold (regenerates, still exactly one commit), and forced-failure (degrades to a warning, commit still happens) casesJira: GETSITREP-51 (In Progress → ready for review)
🤖 Generated with Claude Code