Completes #62. The capture-routing landed in 723dab5 (#62 minimal); this fixes the one stale piece left in it.
What was stale
That commit's classification-gate prose predated #67:
claimed "no populated classification.yaml yet" — false since #67 merged + verified live (effective_classification: internal).
steered summary.repos_touchedaway from brain/ai-sessions as if they'd escalate to confidential — but #67 tagged them internal. The advice was both wrong and (since the summary always writes to ai-sessions) self-defeating: pre-#67 every closeout would've escalated to confidential and been refused via claude.ai.
Fix
Point at classification.yaml as the source of truth; list the currently-internal repos/wings as a hint.
Listing central homelab repos is now fine; reserve the refusal warning for client-*/untagged material only.
Completes #62. The capture-routing landed in `723dab5` (#62 minimal); this fixes the one stale piece left in it.
## What was stale
That commit's classification-gate prose predated #67:
- claimed "**no populated `classification.yaml` yet**" — false since #67 merged + verified live (`effective_classification: internal`).
- steered `summary.repos_touched` **away** from `brain`/`ai-sessions` as if they'd escalate to confidential — but #67 tagged them `internal`. The advice was both wrong and (since the summary always writes to `ai-sessions`) self-defeating: pre-#67 every closeout would've escalated to confidential and been refused via claude.ai.
## Fix
- Point at `classification.yaml` as the source of truth; list the currently-`internal` repos/wings as a hint.
- Listing central homelab repos is now fine; reserve the refusal warning for **`client-*`/untagged** material only.
## #62 acceptance
- [x] Phases 4–5 (+ 3's writes) route through the `capture` MCP tool (723dab5)
- [x] `context` assembled with harness + fidelity + classification
- [x] staleness-discipline prose removed (server owns it)
- [x] confirmation gates preserved (dry-run-then-execute)
- [x] classification guidance correct post-#67 (this PR)
- [ ] **live closeout test** — your dogfood from claude.ai (the skill's first real run; capture path already verified live 2026-06-24)
Docs-only. `task check` green.
Closes #62
🤖 Generated with [Claude Code](https://claude.com/claude-code)
The capture-routing in 723dab5 (#62 minimal) carried pre-#67 prose: it
warned "no populated classification.yaml yet" and steered repos_touched
away from brain/ai-sessions as if they'd escalate to confidential. #67
tagged the homelab repos internal, so that guidance is now wrong and
over-restrictive — listing the central repos is fine, and the summary's
fixed ai-sessions target no longer escalates the call. Point at
classification.yaml as the source of truth; reserve the refusal warning
for client-*/untagged material. Completes #62's veneer.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
mathias
merged commit 66a9b8e725 into main2026-06-26 14:28:49 +00:00
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.
Completes #62. The capture-routing landed in
723dab5(#62 minimal); this fixes the one stale piece left in it.What was stale
That commit's classification-gate prose predated #67:
classification.yamlyet" — false since #67 merged + verified live (effective_classification: internal).summary.repos_touchedaway frombrain/ai-sessionsas if they'd escalate to confidential — but #67 tagged theminternal. The advice was both wrong and (since the summary always writes toai-sessions) self-defeating: pre-#67 every closeout would've escalated to confidential and been refused via claude.ai.Fix
classification.yamlas the source of truth; list the currently-internalrepos/wings as a hint.client-*/untagged material only.#62 acceptance
captureMCP tool (723dab5)contextassembled with harness + fidelity + classificationDocs-only.
task checkgreen.Closes #62
🤖 Generated with Claude Code