Add os-status lint-config-current check to trigger lint-init #131
Labels
No labels
P0
P1
P2
P3
bug
create
delete
enhancement
filed-by/agent
filed-by/user
frozen
lint-rule
needs-info
needs-triage
next
plugin/cc-architect
plugin/os
plugin/os-adr
plugin/os-aidd-lint
plugin/os-backlog
plugin/os-context
plugin/os-doc-hygiene
plugin/os-sdlc
plugin/os-vault
project/cc-os
ready-for-agent
ready-for-human
recurring
review
update
waiting
wayfinder:grilling
wayfinder:map
wayfinder:map
wayfinder:research
wayfinder:task
wayfinder:task
wontfix
worklist/deviations
worklist/lint-rule
worklist/new-implement-build
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
jared/cc-os#131
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Adoption of lint config should be invoked via an os check whose
remediation calls the os-sdlc skill, mirroring the existing 'tracker-configured' -> '/os-backlog:route' pattern. Per ADR-0026, os:fix
orchestrates and never reimplements, so the check must invoke the skill rather than duplicate it.
The check fires when the generated base config is absent, or when its 'os-sdlc-rubocop-base-version' stamp is older than the plugin's template. This also provides the update path for when the template evolves.
Reference: ADR-0066, consequence 5. (Note: os-status was merged into the
osplugin per ADR-0105; the check belongs in plugins/os/hooks/checks.py, remediation /os:fix.)Frozen in the 2026-08-16 backlog reset — see #419 for the expiry procedure. Do not work unless a live run rediscovers this issue.