GITHUB-ISSUES — Folder structure + _system cleanup — 2026-03-16
GITHUB-ISSUES — Folder structure + _system cleanup — 2026-03-16
Section titled “GITHUB-ISSUES — Folder structure + _system cleanup — 2026-03-16”What this file is
Section titled “What this file is”Issue-only doc. NOT a TASKS.md file. Harley’s job: run the operations listed below in order and stop. Do not build anything. Do not create branches. Do not write code.
Rules for Harley
Section titled “Rules for Harley”- Run operations one at a time in the order listed
- Confirm each result before moving to the next
- Report any failures to operator immediately
- Stop after all operations are complete — no other work
Operations
Section titled “Operations”Operation 1 — delete stale GITHUB-ISSUES.md from _system/
Section titled “Operation 1 — delete stale GITHUB-ISSUES.md from _system/”rm /mnt/d/Claude/_system/GITHUB-ISSUES.mdOperation 2 — delete stale handoff doc from _system/ (closes #299)
Section titled “Operation 2 — delete stale handoff doc from _system/ (closes #299)”gh issue close 299 --comment "Stale handoff file removed from _system/ directly via filesystem MCP."rm /mnt/d/Claude/_system/SCAFFOLDER-HANDOFF-2026-03-16-v2.mdOperation 3 — retitle #297 (consolidation story changed)
Section titled “Operation 3 — retitle #297 (consolidation story changed)”gh issue edit 297 --title "chore: keep GITHUB-ISSUES.md template in sync between templates/ and _system/" --body "GITHUB-ISSUES.md template lives in scaffolder/templates/ as the source of truth. A reference copy lives in _system/ for Joker to use between sessions. These must be kept in sync. This issue covers: (1) documenting the sync rule in CHAT-REFERENCE.md — template is source of truth, _system/ copy is updated whenever the template changes, (2) confirming sc create does not output GITHUB-ISSUES.md to new projects — it is a Joker/operator tool, not a project file."Operation 4 — new issue: add docs/tasks/ and docs/issues/ to sc create scaffold output
Section titled “Operation 4 — new issue: add docs/tasks/ and docs/issues/ to sc create scaffold output”gh issue create \ --title "feat: add docs/tasks/ and docs/issues/ to sc create folder structure" \ --label "enhancement" \ --milestone "v0.10.0" \ --body "Two new folders added to the scaffolder project this session: docs/tasks/ (versioned TASKS files for Harley) and docs/issues/ (dated GITHUB-ISSUES operation files from Joker). These do not exist in the sc create scaffold output or in templates/CLAUDE.md folder structure. This issue covers: (1) add docs/tasks/ and docs/issues/ with .gitkeep to sc create output, (2) update folder structure in templates/CLAUDE.md, (3) update folder structure in scaffolder's own CLAUDE.md to match."Operation 5 — new issue: update CLAUDE.md template folder structure
Section titled “Operation 5 — new issue: update CLAUDE.md template folder structure”gh issue create \ --title "docs: update folder structure in templates/CLAUDE.md" \ --label "documentation" \ --milestone "v0.10.0" \ --body "templates/CLAUDE.md folder structure section is stale. Needs to reflect: (1) docs/tasks/ added — versioned TASKS files live here, not docs/ root, (2) docs/issues/ added — dated GITHUB-ISSUES operation files live here, (3) sessions/CURRENT.md rename to CURRENT-CODE.md (per #287), (4) CURRENT-CHAT.md added to sessions/, (5) remove PLANNING.md — already removed in v0.9.1. Depends on #287 (CURRENT.md rename) being built first."Operation 6 — new issue: update scaffolder’s own CLAUDE.md folder structure
Section titled “Operation 6 — new issue: update scaffolder’s own CLAUDE.md folder structure”gh issue create \ --title "docs: update scaffolder CLAUDE.md folder structure to match templates" \ --label "documentation" \ --milestone "v0.10.0" \ --body "scaffolder/CLAUDE.md (the live project file, not the template) has a stale folder structure section. It does not include docs/tasks/, docs/issues/, or the updated session file names. Update to match templates/CLAUDE.md once that is updated. Also update the sessions/CURRENT.md reference to CURRENT-CODE.md per #287. Do this in the same pass as the template update — they should always match."