GITHUB-ISSUES — Session enforcement + sc exit bug — 2026-03-16

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

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

Operation 1 — close #292 (sc-session-start skill already written)

gh issue close 292 --comment "sc-session-start SKILL.md written to templates/claude-skills/sc-session-start/SKILL.md via filesystem MCP on 2026-03-16. Closes this issue."

Operation 2 — close #293 (sc-session-end skill already written)

gh issue close 293 --comment "sc-session-end SKILL.md written to templates/claude-skills/sc-session-end/SKILL.md via filesystem MCP on 2026-03-16. Closes this issue."

Operation 3 — close #295 (CHAT-REFERENCE.md already updated)

gh issue close 295 --comment "CHAT-REFERENCE.md updated in D:\Claude\_system\ via filesystem MCP on 2026-03-16. Reflects MCP access, new session file names (CURRENT-CHAT.md, CURRENT-CODE.md), issue operations flow, and session start/end process. Closes this issue."

Operation 4 — close #294 (PROJECT-INSTRUCTIONS.md template already stripped)

gh issue close 294 --comment "templates/PROJECT-INSTRUCTIONS.md stripped to persona + file reading list on 2026-03-16. Also updated live _system/PROJECT-INSTRUCTIONS.md to v0.10.0. Closes this issue."

Operation 5 — new issue: session enforcement — Joker refuses work until session started

gh issue create \
  --title "feat: Joker refuses project work until session is started and goal confirmed" \
  --label "enhancement" \
  --milestone "v0.10.0" \
  --body "Joker must not perform any project work until the operator has explicitly confirmed the session goal. Behaviour: (1) sc-session-start skill runs automatically at start of every conversation, (2) Joker presents last session summary and open items, (3) Joker asks 'What is the goal for this session?', (4) Joker declares conversation name, (5) only then does work begin. Additionally: at natural stopping points Joker asks 'Are we done for today? I can close the session now.' If yes, sc-session-end runs automatically without operator having to remember the command. Update sc-session-start and sc-session-end skills to enforce this. Update PROJECT-INSTRUCTIONS.md standard section to document the rule."

Operation 6 — new issue: Harley refuses work until session started and goal confirmed

gh issue create \
  --title "feat: Harley refuses project work until session is started and goal confirmed" \
  --label "enhancement" \
  --milestone "v0.10.0" \
  --body "Harley must not perform any project work until the operator has confirmed the session goal. Behaviour: (1) session-start skill runs automatically, reads CURRENT-CODE.md and CURRENT-CHAT.md, reports state, (2) Harley asks 'Ready to start. What are we working on this session?', (3) only after operator confirms goal does Harley begin any work. Additionally: at natural stopping points or when wrapping up, Harley asks 'Are we done for today? I can run session-end now.' If yes, session-end skill runs automatically and Harley displays the sc end command so operator does not have to remember it. Update session-start and session-end skills to enforce this. Update CLAUDE.md template to document the rule."

Operation 7 — new issue: sc exit closes Harley without running session-end

gh issue create \
  --title "bug: sc exit closes Harley without running session-end — session state not saved" \
  --label "bug" \
  --milestone "v0.10.0" \
  --body "The /sc-exit slash command closes Claude Code immediately without running the session-end skill. This means sessions/CURRENT-CODE.md is not updated and no session log is written when the operator uses exit. Options to evaluate: (1) remove sc-exit entirely — operators should use sc-done or sc-end instead, (2) make sc-exit run session-end first then close, (3) add a warning before exit fires that reminds operator to run session-end first. Recommend option 1 or 2. The concept of closing without saving session state should not exist in the workflow."