local-fs: .devwork commit opt-out must be a declaration, not a hand-revert #16
Labels
No labels
component:adapters
component:lifecycle
component:qa
component:setup
component:shared
component:worktrees
phase/accepted
phase/backlog
phase/deployed
phase/developing
phase/integrating
phase/planning
phase/qa
phase/requirements
phase/uat
priority:critical
priority:critical
priority:high
priority:high
priority:low
priority:low
priority:medium
priority:medium
type:bug
type:chore
type:docs
type:feature
type:infra
type:tech-debt
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jbr870/devwork-skills#16
Loading…
Add table
Add a link
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?
Observed failure
local-fscommits.devwork/by default. That default was rejected by the user and hand-reverted ona real project — and because it is a default rather than a declaration, a future
/setuprun wouldsilently reverse the fix.
What it needs
A
forge:block declaration read bybootstrap_project— e.g.forge.local_fs.commit_devwork: true|false— so the choice is recorded in the project's CLAUDE.md and survives re-running setup.
Why the shape matters
This is the suite's own rule applied to itself: absence is never a silent default. A hand-edit that
setup can undo is not a decision, it is a temporary state. The fix is not "change the default" — it is
"make it declared".
Source: dogfood retrospective 2026-08-07 (F5), deferred backlog.