Repository navigation
[implement] Do not commit structure.md; drop tasks.md once work items exist on the board #36
Description
Recurring problem across projects.
Observed behavior
- A temporary
structure.mdfile was created and committed. tasks.mdremains committed even after the work items have been created on the board (GitHub Issues or Azure DevOps).
Desired behavior
structure.mdis treated as temporary and never committed.- When work items are created on the board,
tasks.mdis either not committed or is removed automatically once the items land as issues/work items.
Acceptance criteria
- Implementation flow does not commit
structure.md. - After board sync,
tasks.mdis cleaned up automatically or its non-creation is enforced.
Activity
fedeoliv commentedon Oct 16, 2026
Implementation verified, pending merge.
Moved optional generated structure caches to ignored .memory storage and made board-backed decomposition keep drafts session-local or ignored rather than create versioned tasks.md files. Handoffs use verified board URLs. Local-only task lists remain durable, partial synchronization preserves drafts and created IDs, and existing authored documents are not automatically deleted. Commit guidance stages explicit reviewed paths and excludes generated caches and board-mode drafts.
Validation:
npm --prefix docs run buildandgit diff --checkpassed. Independent lifecycle review confirmed local-only, partial-sync, and staging paths. Changed Markdown has no new lint diagnostics compared with HEAD.Branch:
feature/36-temporary-artifact-hygiene.Commit:
dbd9c9bbe87e4ee3d628e5e7cf22cee264778cc2.PR: #82.
Changes are committed and pushed. Merge the dependency first: #81. Retarget this PR to main if GitHub has not done so automatically. The issue remains open until merge.