fix(view): keep archived changes off the dashboard - #2031
Conversation
openspec view is a one-screen dashboard for a person reading a terminal. #399 added every archived change to it, so projects with hundreds of archived changes pushed active work off the screen (#2030). The dashboard shows current work again; `openspec list --archived` still shows history. To catch this class of mistake earlier, the cli-view spec now states who the command serves and that it shows current work only, view.ts says the same where the code lives, and CONTRIBUTING asks how a human view grows as a project ages before anything is added to it.
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository: Fission-AI/OpenSpec/.coderabbit.yaml Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (1)
💤 Files with no reviewable changes (1)
Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 7 remain after this review. 📝 WalkthroughWalkthrough
ChangesCurrent-work dashboard
Priority: ➖ Normal Estimated code review effort: 2 (Simple) | ~10 minutes Change: Bug fix · Severity of issue fixed: Medium Merge Risk: ⚪ Minimal · up to The view remains focused on current work, while archived changes remain available through list. No actionable merge-blocking risk was established. Architecture SummaryArchitecture risk: 🔵 Low · up to The change affects 5 systems. Changed systems: Architecture concerns Review detailsSystems and components
Before / after behavior
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
No PR-relevant drift confirmed.
|
The CLI reference describes what view prints, so it goes back to its pre-#399 text. The why lives in the cli-view spec Purpose, the code comment points there, and the CONTRIBUTING rule no longer names a PR.
The CONTRIBUTING section, the cli-view spec requirement, and the view.ts comment each restated this one bug instead of guarding the general mistake. The regression test stays as the guardrail.
alfred-openspec
left a comment
There was a problem hiding this comment.
Reviewed the current-work behavior, archive-scaling regression, store-resolution coverage, changeset, and canonical CLI reference. This restores a bounded, useful dashboard while keeping archive history available through the explicit list command.
Closes #2030
What this changes
openspec viewis a one-screen dashboard for a person reading a terminal. #399 added every archived change to it. In projects with hundreds of archived changes, that list pushed the active work off the screen, which is the whole point of the command.openspec viewno longer lists or counts archived changes. The view code is back to its pre-feat(cli): show archived changes in list and view #399 state.openspec list --archivedand--allfrom feat(cli): show archived changes in list and view #399 are untouched.docs-lab/reference/cli.md: theviewentry goes back to its pre-feat(cli): show archived changes in list and view #399 text.How you verified it
Demo project: 1 draft, 2 active, 1 completed change, 4 specs, 189 archived changes.
Before: first 40 of 230 lines
After: full output
renders the same dashboard however many changes are archived (#2030)intest/core/view.test.ts: renders the dashboard, adds 200 archived changes, and asserts the output is identical. It fails onmain(222 lines vs 20) and passes here.view.pnpm build,tsc --noEmit,pnpm lintpass.pnpm test: 6401 passed, 2 failed. Both failures (artifact-workflowCursor skills,config-profileproject apply) reproduce on a cleanmaincheckout and don't touchview.openspec validate --specs --strict:cli-viewpasses.Notes
view.Archived Changes: Nsummary count is deliberate. The issue asked for a view of open work, and the spec now keeps history out entirely so there's no partial exception to argue about later.pnpm changesetif this affects users, and committed the file🤖 Generated with Claude Code