Joycraft Session End

Use this format:

# Discoveries — [topic]

**Date:** YYYY-MM-DD
**Spec:** [link to spec if applicable]

## [Discovery title]
**Expected:** [what we thought would happen]
**Actual:** [what actually happened]
**Impact:** [what this means for future work]

If nothing surprising happened, skip the discovery file entirely. No discovery is a good sign — the spec was accurate.

1b. Update Context Documents

If docs/context/ exists, quickly check whether this session revealed anything about:

• Production risks — did you interact with or learn about production vs staging systems? Update docs/context/production-map.md
• Wrong assumptions — did you assume something that turned out to be false? Update docs/context/dangerous-assumptions.md
• Key decisions — did you make an architectural or tooling choice? Add a row to docs/context/decision-log.md
• Unwritten rules — did you discover a convention or constraint not documented anywhere? Update docs/context/institutional-knowledge.md

Skip this if nothing applies. Don't force it — only update when there's genuine new context.

2. Run Validation

Run the project's validation commands. Check CLAUDE.md or AGENTS.md for project-specific commands. Common checks:

• Type-check (e.g., tsc --noEmit, mypy, cargo check)
• Tests (e.g., npm test, pytest, cargo test)
• Lint (e.g., eslint, ruff, clippy)

Fix any failures before proceeding.

3. Update Spec Status

If working from an atomic spec in docs/specs/ (scan recursively — specs may be in subdirectories like docs/specs/<feature-name>/):

• All acceptance criteria met — update status to Complete
• Partially done — update status to In Progress, note what's left

If working from a Feature Brief in docs/briefs/, check off completed specs in the decomposition table.

4. Commit

Commit all changes including the discovery file (if created) and spec status updates. The commit message should reference the spec if applicable.

5. Push and PR (if autonomous git is enabled)

Check CLAUDE.md or AGENTS.md for "Git Autonomy" in the Behavioral Boundaries section. If it says "STRICTLY ENFORCED" or the ALWAYS section includes "Push to feature branches immediately after every commit":

1. Push immediately. Run git push origin <branch> — do not ask, do not hesitate.
2. Open a PR if the feature is complete. Check the parent Feature Brief's decomposition table — if all specs are done, run gh pr create with a summary of all completed specs. Do not ask first.
3. If not all specs are done, still push. The PR comes when the last spec is complete.

If CLAUDE.md or AGENTS.md does NOT have autonomous git rules (or has "ASK FIRST" for pushing), ask the user before pushing.

6. Report

Session complete.
- Spec: [spec name] — [Complete / In Progress]
- Build: [passing / failing]
- Discoveries: [N items / none]
- Pushed: [yes / no — and why not]
- PR: [opened #N / not yet — N specs remaining]
- Next: [what the next session should tackle]

Tip: Run /new before starting the next step. Your artifacts are saved to files — this conversation context is disposable.