fix: correct statusline context calculation and track hooks in manifest (#769)#845
Closed
0xLeathery wants to merge 8 commits intogsd-build:mainfrom
Closed
fix: correct statusline context calculation and track hooks in manifest (#769)#8450xLeathery wants to merge 8 commits intogsd-build:mainfrom
0xLeathery wants to merge 8 commits intogsd-build:mainfrom
Conversation
added 8 commits
February 28, 2026 20:28
Command shipped in a92512a but was missing from all documentation. Added to help.md (full reference + common workflows), README.md command table, and USER-GUIDE.md command reference.
Add centralized path resolution layer (paths.cjs) that enables milestone-scoped directories for parallel milestone work. All 11 lib files refactored to use resolvePlanningPaths() instead of hardcoded .planning/ paths. Key changes: - New paths.cjs: resolvePlanningPaths(cwd, milestoneOverride) resolves abs/rel paths based on ACTIVE_MILESTONE file or --milestone CLI flag - --milestone <name> CLI flag parsed in gsd-tools.cjs - New commands: milestone create/switch/list/status - All init commands output milestone, is_multi_milestone, planning_base - Legacy mode (no ACTIVE_MILESTONE) returns identical paths to before - Auto-migration: first milestone create copies existing global state - 25 new tests for paths and milestone commands (457 total, 0 failures)
Replace hardcoded .planning/ paths in bash commands and commit
file lists with init JSON variables ({state_path}, {roadmap_path},
{planning_base}/...). Workflows without init calls gain appropriate
init calls. Global paths (PROJECT.md, codebase/) left unchanged.
…tusline, and docs (gsd-build#291) Phase 5: polish for concurrent milestone execution. - Milestone-scoped commit prefixes in execute-plan.md (v2.0/08-02) - cmdMilestoneSwitch warns about in-progress work before switching - /gsd:switch-milestone workflow and command - Statusline shows active milestone in cyan [v2.0] - new-milestone.md calls milestone create for multi-milestone mode - Help and README updated with switch-milestone and concurrent docs
…itch-warning tests (gsd-build#291) - USER-GUIDE: add /gsd:switch-milestone, concurrent milestones section, multi-milestone directory layout - CHANGELOG: add [Unreleased] entry for concurrent milestone execution - planner-subagent-prompt.md: replace hardcoded .planning/ paths with milestone-aware template variables - 4 new tests: switch in-progress warning, idle switch, same-milestone switch, and auto-migration on first milestone create (461 total)
…ration (gsd-build#99) Add structured bug reporting lifecycle: report → triage → investigate → fix → resolve. - Skill file, workflow, and bug-report template - CLI commands: bug list/update/resolve, init bugs, scaffold bugs - Severity inference from keywords (critical/high/medium/low) - Diagnostic log capture (git state, error output, log files) - Optional GitHub issue creation via gh CLI - 13 new tests across 4 test suites - Registered in help, README, USER-GUIDE, CHANGELOG - STATE.md and progress workflow track active bugs
…ion (gsd-build#210) Add fourth model profile (adaptive) that auto-selects models per-plan based on complexity scoring. Includes medium tier alignment with balanced profile, keyword regex precision fixes, enriched plan context (type, depends_on), usage logging, verifier adaptive resolution, and additional scoring signals (TDD, dependencies, test files). 528 tests passing.
…st (gsd-build#769) - Replace 80% scaling with 16.5% autocompact buffer subtraction so displayed percentage reflects when compaction is actually imminent - Update color thresholds to 50/65/80 (green/yellow/orange/red) - Switch display to toFixed(2) so small context changes are visible - Add gsd-statusline.js, gsd-check-update.js, gsd-context-monitor.js to writeManifest() so local edits are backed up before /gsd:update
This was referenced Mar 2, 2026
glittercowboy
requested changes
Mar 2, 2026
Collaborator
glittercowboy
left a comment
There was a problem hiding this comment.
Review: Split Required
The statusline fix is valid — using Claude Code's actual 16.5% autocompact buffer instead of a hardcoded 80% ceiling, plus tracking hooks in the manifest. Both are good changes.
However, this PR is 3,670 additions across 66 files, and the actual fix is a small fraction of that. The bulk is shared with #850 and #852:
- Kimi CLI support
- Adaptive model profiles
- Bug reporting system
- Switch-milestone command
- Opus model resolution fix
These three PRs (#850, #852, #845) share ~95% of the same diff and will conflict massively with each other. Only one can merge cleanly.
Requested action: Please extract the statusline + hooks manifest fix into a standalone PR (just the gsd-statusline.js changes, manifest additions, and updated thresholds). Then consolidate the shared features into a single feature PR.
This was referenced Mar 3, 2026
Contributor
Author
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
Fixes the statusline context bar calculation to reflect Claude Code's actual autocompact buffer, and adds GSD hook files to the install manifest so local edits survive
/gsd:update.Why
The old 80% scaling factor was arbitrary and produced misleading percentages — at 50% real usage the bar showed ~62%, and the orange/red thresholds fired too early. Claude Code actually reserves 16.5% (33k of 200k tokens) as an autocompact buffer, so the usable window is 83.5%. Separately,
gsd-statusline.jsand the other hook files were absent fromgsd-file-manifest.json, causing them to be silently overwritten on every update without backing up local modifications.Testing
Checklist
Breaking Changes
None
Closes #769