Wire the existing close-session skill (skills/close-session/SKILL.md) to call the now-shipped capture capability instead of doing its brain/gitea writes inline. The skill becomes the trigger + harvest veneer over capture — exactly the role the architecture (#49) assigned it.
Context
capture shipped in #49 (PRs #56–#61, v0.11.0): one CaptureService behind POST /capture (REST) and an MCP capture tool. The MCP tool is live on the claude.ai connector. The close-session skill currently does its own Phase 4/5 writes (summary commit + brain note) directly; it should instead harvest the session into a capture call and let the server own persistence, the I1 gate, the I5 audit, and the supersession/staleness discipline.
What to do
Replace close-session Phase 4 (summary commit) + Phase 5 (brain note) with a single capture invocation (MCP tool on claude.ai), passing assembled insights + tickets + summary + context (harness claudeai-chat, fidelity: live-capture).
Phase 3 (issue actions) can route through capture's tickets array rather than direct gitea:* calls — consolidates the write path and gets the audit record for free.
Keep the harvest/gating prose (Phases 1–3) and the confirmation gates; only the persistence mechanism changes from inline tools → capture.
The skill no longer needs to carry the staleness rule (no-semantic-query-after-supersede) — capture owns it server-side. Simplify the Phase 5 prose accordingly.
Update fidelity handling: live-capture from claude.ai; note that a later transcript-parse capture supersedes it (the collision rule, now server-enforced).
Acceptance
close-session Phases 4–5 (and 3's writes) route through the capture MCP tool
Skill assembles context with harness + fidelity + (optional) classification
Staleness-discipline prose removed from the skill (server owns it now)
Confirmation gates preserved
Tested against a real session closeout (this is also the skill's first live test)
**Parent epic:** #49 (capture, complete, v0.11.0) · deferred follow-up
## Scope
Wire the existing `close-session` skill (`skills/close-session/SKILL.md`) to call the now-shipped `capture` capability instead of doing its brain/gitea writes inline. The skill becomes the **trigger + harvest veneer** over `capture` — exactly the role the architecture (#49) assigned it.
## Context
`capture` shipped in #49 (PRs #56–#61, v0.11.0): one `CaptureService` behind `POST /capture` (REST) and an MCP `capture` tool. The MCP tool is live on the claude.ai connector. The `close-session` skill currently does its own Phase 4/5 writes (summary commit + brain note) directly; it should instead **harvest** the session into a `capture` call and let the server own persistence, the I1 gate, the I5 audit, and the supersession/staleness discipline.
## What to do
- Replace close-session Phase 4 (summary commit) + Phase 5 (brain note) with a single `capture` invocation (MCP tool on claude.ai), passing assembled `insights` + `tickets` + `summary` + `context` (harness `claudeai-chat`, `fidelity: live-capture`).
- Phase 3 (issue actions) can route through `capture`'s `tickets` array rather than direct `gitea:*` calls — consolidates the write path and gets the audit record for free.
- Keep the harvest/gating prose (Phases 1–3) and the confirmation gates; only the **persistence mechanism** changes from inline tools → `capture`.
- The skill no longer needs to carry the staleness rule (no-semantic-query-after-supersede) — `capture` owns it server-side. Simplify the Phase 5 prose accordingly.
- Update `fidelity` handling: live-capture from claude.ai; note that a later transcript-parse capture supersedes it (the collision rule, now server-enforced).
## Acceptance
- [ ] close-session Phases 4–5 (and 3's writes) route through the `capture` MCP tool
- [ ] Skill assembles `context` with harness + fidelity + (optional) classification
- [ ] Staleness-discipline prose removed from the skill (server owns it now)
- [ ] Confirmation gates preserved
- [ ] Tested against a real session closeout (this is also the skill's first live test)
- [ ] Committed to `skills/close-session/SKILL.md`
## Related
- #49 (capture epic), `specs/capture-bdd-spec.md`, `specs/capture-implementation-report.md`
- `skills/close-session/SKILL.md` (the veneer target)
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Parent epic: #49 (capture, complete, v0.11.0) · deferred follow-up
Scope
Wire the existing
close-sessionskill (skills/close-session/SKILL.md) to call the now-shippedcapturecapability instead of doing its brain/gitea writes inline. The skill becomes the trigger + harvest veneer overcapture— exactly the role the architecture (#49) assigned it.Context
captureshipped in #49 (PRs #56–#61, v0.11.0): oneCaptureServicebehindPOST /capture(REST) and an MCPcapturetool. The MCP tool is live on the claude.ai connector. Theclose-sessionskill currently does its own Phase 4/5 writes (summary commit + brain note) directly; it should instead harvest the session into acapturecall and let the server own persistence, the I1 gate, the I5 audit, and the supersession/staleness discipline.What to do
captureinvocation (MCP tool on claude.ai), passing assembledinsights+tickets+summary+context(harnessclaudeai-chat,fidelity: live-capture).capture'sticketsarray rather than directgitea:*calls — consolidates the write path and gets the audit record for free.capture.captureowns it server-side. Simplify the Phase 5 prose accordingly.fidelityhandling: live-capture from claude.ai; note that a later transcript-parse capture supersedes it (the collision rule, now server-enforced).Acceptance
captureMCP toolcontextwith harness + fidelity + (optional) classificationskills/close-session/SKILL.mdRelated
specs/capture-bdd-spec.md,specs/capture-implementation-report.mdskills/close-session/SKILL.md(the veneer target)