os-status:fix tune-up: snooze lifecycle, config-format normalization, gitignore step, no-commit scope #23
Labels
No Label
P0
P1
P2
P3
afk-ready
hitl
next
ready-for-agent
review
semi
waiting
wayfinder:grilling
wayfinder:map
wayfinder:research
wayfinder:task
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: jared/cc-os#23
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
From the credvault smoke-test audit (session cd1ae1cd, 2026-07-12). /os-status:fix ran on-contract overall, but four gaps:
.cc-os/snooze-*files dropped by SessionStart runs outlive the condition they gate — after fix flipped all checks to ok/note, three stale snooze files remained. Add aclear_snooze(root, check_name)helper (state.py) and clear it whenever a check flips from warn to ok/note on re-run; document in SKILL.md..cc-os/configin credvault ended up withtracker=github:...(os-backlog Ruby CLI, no spaces) andversion = 1(os-status Python write_config_value, spaces). Pick ONE format (key=value, matching commit 3b9c4fb's contract), makewrite_config_valuenormalize on write, and align os-backlogconfig-writeto the same convention..gitignoreadditions (.os-adr/, then.cc-os/in a second late pass) by reading invariants.md ad hoc. Make "ensure.cc-os/(and any plugin state dirs) are gitignored" an explicit SKILL.md step or fold it into the owning init skills.Also clarify SKILL.md step 3: fixes that don't affect check-registry state (gitignore edits) don't require a checks re-run.
Acceptance: tests for clear-on-pass snooze behavior; both writers produce identical config format; SKILL.md updated; refresh-plugins run.