SESSION-PRIME: paste body's fenced block into a fresh Claude session to orient fast

[TortoiseWolfe]

Purpose: this issue is the durable roadmap for TortoiseWolfe/ScriptHammer. The body below is always-current — active arc, next 3 sessions queued, backlog. Comments are the audit trail. The prime prompt at the top tells a fresh Claude session to read this body first.

⚠️ Roadmap was migrated from an earlier "pointer-only" format and the current contents are INFERRED from repo state, not user-confirmed. First session that actually sits down to work in ScriptHammer should correct the active arc + queued sessions to match real intent.

---

Prime prompt (copy from here into a fresh Claude session)

/prep

Then check this issue (TortoiseWolfe/ScriptHammer#115) — its BODY is the current roadmap. Read everything below the prime prompt: active arc, next 3 sessions queued, backlog. The most recent COMMENT on this issue is the audit trail of what changed since the previous session.

Supplementary context (read if the body's roadmap references them or if the user's first message takes us off-roadmap):
1. `~/.claude/projects/-home-TurtleWolfe-repos-ScriptHammer/memory/MEMORY.md` — top of the index lists NON-NEGOTIABLE user preferences. Read these first; they're binding.
2. `git log --oneline -20` — what shipped recently.
3. Open issues (`gh issue list --repo TortoiseWolfe/ScriptHammer --state open`) — most are tagged `template-v1-out-of-scope` (Eval-Backlog / Gap-Audit). Treat those as deferred backlog, not active work.
4. Open PRs (`gh pr list --repo TortoiseWolfe/ScriptHammer --state open`).

Operational reminders from MEMORY.md / CLAUDE.md you'll trip over otherwise:
- ALWAYS prefer cleaner long-term solutions over quick hacks. Never offer a hack as the primary recommendation.
- NEVER propose shortcuts, bypasses, or workarounds — fix root cause.
- SECURITY DEFINER to bypass RLS is a hack, not a fix.
- Follow CLAUDE.md principles #1 (Proper Solutions Over Quick Fixes) and #2 (Root Cause Analysis).

Then either start on the roadmap's "next session should" item, or ask the user if they want to deviate.

Stop reading here when priming — everything below is the roadmap

---

Roadmap

Active arc

Fork-experience cleanup — make ScriptHammer cleanly forkable as a template. Currently on branch chore/fork-experience-cleanup, PR #114 open.

Status: PR #114 open; recent commits (last 24h) include dead middleware removal, rebrand documentation polish, and a fork-checklist fix. Probably close to landing.

Remaining tasks (inferred — confirm with user):

• Get PR chore: fork-experience cleanup (#112, #113, dead middleware) #114 to mergeable state and land it
• Verify the fork-experience end-to-end on a fresh clone (rebrand.sh, fresh-from-template flow)
• Close any follow-up issues spawned by chore: fork-experience cleanup (#112, #113, dead middleware) #114 review

Blockers / decisions needed:

• Whether PR chore: fork-experience cleanup (#112, #113, dead middleware) #114 is the end of the fork-experience arc or there's more queued behind it
• Confirm with the user — this is inferred from branch name + recent commits, not user-confirmed

---

Next 3 sessions queued

Inferred from recent commit cadence. Re-prioritize based on actual user intent next session.

Session +1: Land PR #114, close out fork-experience cleanup

• Why: open PR, looks close to done
• First action: gh pr view 114 --repo TortoiseWolfe/ScriptHammer to see review status. If clean, merge. If not, address feedback.

Session +2: Stripe payments Phase 0c (or whatever's next in that arc)

• Why: Phase 0a + 0b shipped recently (6180134, 174e5ac); arc is clearly mid-stream
• First action: read PAYMENT-DEPLOYMENT.md (rewrite landed at 5a9bec8). Identify what Phase 0c entails. Ask user if it's the right next step.

Session +3: Pull from Gap-Audit backlog (P2 priority)

• Why: lots of priority:p2 issues open + template-v1-out-of-scope. Some may be ready to promote.
• First action: gh issue list --repo TortoiseWolfe/ScriptHammer --state open --label priority:p2 --json number,title to surface candidates. User picks one.

---

Backlog (no scheduled position)

Categories of work that exist as open issues but aren't currently queued.

• Gap-Audit P2 issues ([Gap-Audit] 005 Security Hardening: complete session-timeout UI + audit dashboard + secret detection #23, [Gap-Audit] 012 + 014: welcome message admin gate end-to-end flow #27, [Gap-Audit] 016 Messaging Critical Fixes: 5 separate UX issues, none shipped #30, [Gap-Audit] 020 PWA Background Sync: Firefox/Safari fallback + retry UI + storage warnings #32, [Gap-Audit] 023 EmailJS Integration: provider health dashboard + rate-limit handling #34, [Gap-Audit] 026 Unified Messaging Sidebar: mobile drawer transitions + badge sync latency #35, +more) — promote individually based on user priority
• Gap-Audit P3 issues ([Gap-Audit] 010 Unified Blog: implement offline editing + sync + conflict resolution + migration tooling #25, [Gap-Audit] 011 + 043 Group Chats / Group Service: implement 8 stub member-management methods #26) — lower priority, defer until P2s clear
• Eval-Backlog ([Eval-Backlog] PAYMENT-OFFLINE-UI: UI layer for existing offline payment queue #4, [Eval-Backlog] SUBSCRIPTION-MGMT: subscription management route + 4 edge functions + grace-period wiring #5) — payment offline UI + subscription management; large scope, treat as separate arcs when surfaced
• Three.js game ([Feature] 047 Three.js Game #48, feat: #48 Three.js Game at /game/3d (047 — full SpecKit cascade) #95 shipped 2026-05-XX) — base game lives at /game/3d now; any follow-up work would queue here
• E2E test stability — recent fix-rounds 12, 13, 14a suggest this is a recurring concern; capture as a named backlog item if it surfaces again

---

Next session should

gh pr view 114 --repo TortoiseWolfe/ScriptHammer — see whether PR #114 is reviewable / mergeable / blocked, and either land it or address feedback.

Override: if the user's first message has a different priority, follow the user. The roadmap is inferred and may not match real intent.

---

Why this exists

Sessions end. The next session starts cold. Without a single canonical "what was the world like when we last stopped + here's what to do next" pointer, the new model wastes context wandering. This issue is the one URL to paste into a fresh chat. The BODY carries the plan; comments form the audit trail.

How to maintain

Run /session-prime at session-end. The skill rewrites the body to reflect what changed in the roadmap and appends a comment with the audit trail.

If the prime prompt itself becomes stale (memory file renamed, project changed shape), edit the body's prime-prompt block directly.

[TortoiseWolfe]

Issue seeded 2026-05-28 ~19:30 EDT

This is the baseline, not a session-end log. The rolling-prime issue was created via /session-prime from a different repo's session. No work happened on ScriptHammer this session. Use this comment as the starting snapshot; future /session-prime runs will add real session-end deltas on top.

Current branch: chore/fork-experience-cleanup (not main).

Last 10 commits on this branch:

• 82b264f — chore(auth): remove dead middleware; document client-side route protection
• 501567c — chore(rebrand): document the 5-reference threshold
• 8d85330 — docs(fork-checklist): fix rebrand.sh usage line
• 174e5ac — feat(payments): Phase 0b — create-stripe-subscription + fix webhook template_user_id ([Phase 0b] Stripe subscription: create-stripe-subscription (~3h) #102) (feat(payments): Phase 0b — create-stripe-subscription + fix webhook template_user_id (closes #102) #111)
• 6180134 — feat(payments): Phase 0a — create-stripe-checkout + verify-stripe-session ([Phase 0a] Stripe one-off: create-stripe-checkout + verify-stripe-session (~6h) #101) (feat(payments): Phase 0a — create-stripe-checkout + verify-stripe-session (closes #101) #110)
• 5a9bec8 — docs(payments): rewrite PAYMENT-DEPLOYMENT.md + add check-payment-config.sh (docs(payments): rewrite PAYMENT-DEPLOYMENT.md + add config verifier script #99)
• c6cb675 — fix(scroll): round 14a — data-show-scroll-button attribute for E2E observability (fix(scroll): round 14a — data-show-scroll-button attribute (E2E observability for the jump-button race) #108)
• a29d3b9 — fix(e2e): round 13 — exclude handleReAuthModal duration from SC-001 budget (fix(e2e): round 13 — SC-001 timing budget excludes handleReAuthModal duration #107)
• c24b9f6 — feat: [Feature] 047 Three.js Game #48 Three.js Game at /game/3d (047 — full SpecKit cascade) (feat: #48 Three.js Game at /game/3d (047 — full SpecKit cascade) #95)
• 95efd86 — fix(e2e): feat: #48 Three.js Game at /game/3d (047 — full SpecKit cascade) #95-blocker round 12 — handleReAuthModal retries when modal re-appears (fix(e2e): round 12 — handleReAuthModal retries when modal re-appears (WebKit Argon2id flake) #98)

Open PR: #114 — chore: fork-experience cleanup (the cleanup arc this branch is for)

Recently closed (last 7d): #101 (Phase 0a Stripe one-off), #102 (Phase 0b Stripe subscription)

Open issues: mostly template-v1-out-of-scope (Eval-Backlog + Gap-Audit categories — deferred backlog, not active work):

• [Eval-Backlog] PAYMENT-OFFLINE-UI: UI layer for existing offline payment queue #4, [Eval-Backlog] SUBSCRIPTION-MGMT: subscription management route + 4 edge functions + grace-period wiring #5 — payment offline UI + subscription management (Eval-Backlog)
• [Gap-Audit] 005 Security Hardening: complete session-timeout UI + audit dashboard + secret detection #23, [Gap-Audit] 010 Unified Blog: implement offline editing + sync + conflict resolution + migration tooling #25, [Gap-Audit] 011 + 043 Group Chats / Group Service: implement 8 stub member-management methods #26, [Gap-Audit] 012 + 014: welcome message admin gate end-to-end flow #27, [Gap-Audit] 016 Messaging Critical Fixes: 5 separate UX issues, none shipped #30, [Gap-Audit] 020 PWA Background Sync: Firefox/Safari fallback + retry UI + storage warnings #32, [Gap-Audit] 023 EmailJS Integration: provider health dashboard + rate-limit handling #34, [Gap-Audit] 026 Unified Messaging Sidebar: mobile drawer transitions + badge sync latency #35 — Gap-Audit items (P2/P3, deferred)
• And ~30+ more Gap-Audit issues open

Active work:

• Fork-experience cleanup on chore/fork-experience-cleanup (PR chore: fork-experience cleanup (#112, #113, dead middleware) #114 open)
• Payments phase arc — Phase 0a + 0b shipped, future phases TBD

Watch:

• Open PR chore: fork-experience cleanup (#112, #113, dead middleware) #114 — needs to land before fork-experience work concludes
• Phase 0c+ of Stripe payments — sequencing TBD

Next session should: Read memory/MEMORY.md (NON-NEGOTIABLE preferences at top), then check PR #114 status, then ask the user what to focus on (fork-experience cleanup, payments phase 0c, or pulling something off the Gap-Audit backlog).

[TortoiseWolfe]

Body migrated to roadmap format 2026-05-28 ~20:00 EDT

The /session-prime skill was refined to make the issue body carry an explicit roadmap (active arc → next 3 sessions → backlog) instead of just being a pointer to memory. The body above now follows that structure.

Important caveat: ScriptHammer's roadmap is inferred from repo state, not user-confirmed. I haven't actually worked in this repo this session — I'm in Eduity. The active arc (fork-experience cleanup) and queued sessions (PR #114 → Payments Phase 0c → Gap-Audit P2) are guesses based on:

• Current branch chore/fork-experience-cleanup
• Open PR chore: fork-experience cleanup (#112, #113, dead middleware) #114
• Recent commits (payments Phase 0a + 0b shipped, fork-checklist polish)
• Pattern of fix-round commits suggesting E2E stability is recurring

First real session that sits down to work in ScriptHammer should:

1. Read the inferred roadmap
2. Correct the active arc + queued sessions to match real intent
3. Run /session-prime at session-end to lock in the corrected version

The body's "Next session should" line + the "Override: if the user's first message has a different priority" note are explicit about the inference uncertainty. Don't treat the roadmap as binding until a real ScriptHammer session has validated it.