v0.6.1: session-log fidelity, housekeeping, and polish (#8, #10, #11)#20
Merged
Conversation
#11) Doc/skill batch from the v0.4.0 audit (docs/AUDIT-v0.4.0.md, P2). No hook behavior change. Issue #8: the session-log template gains a "What we tried (including what failed)" section (record the real evidence, not a summary - a failed approach is the most expensive thing for a future session to rediscover) and a Follows chain-link so a log can name its predecessor in the same work stream. Issue #10: a new README "Housekeeping" section documents what's safe to delete (old archived buffers, a resolved .capture-errors) vs. what isn't (logs/, HANDOFF.md, unarchived buffers) - documented convention, not automated tooling, matching the plugin's zero-infrastructure identity. The handoff skill now clears .capture-errors once its contents are surfaced in a session log. Issue #11 polish batch: handoff Phase 4.4 drops "(or delete)" for consumed buffers (archive-only removes an unguarded data-loss affordance); Phase 4.3 cites the actual native auto-memory layout with an inline frontmatter example; plugin.json keywords gain git-state/cross-harness/resume/onboarding; tests/run.sh's header now states it is the single source of truth for the assertion count, after prose counts drifted across releases before. Verified: unchanged 154-assertion suite plus shellcheck under both Homebrew and an apt-get install shellcheck Ubuntu container. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Q4iokjvAbBLgrRJYwCVtqb
Three findings from an independent review pass on the v0.6.1 diff: 1. CONFIRMED: the new memory-binding frontmatter example omitted node_type and originSessionId, both present in 100% of real memory topic files under ~/.claude/projects/<slug>/memory/ (verified directly against every file in the harness). An agent following the template verbatim would have produced the exact schema-inconsistent entry the change claimed to prevent. Template now matches the observed real shape. 2/3. CONFIRMED: the new README Housekeeping section and SKILL.md additions used em-dashes, violating this user's global no-em-dash writing-style rule - in handoffs, a category the rule names explicitly. Replaced with commas, colons, periods, or spaced hyphens. Pre-existing em-dashes in SKILL.md content this PR didn't touch are left alone (out of scope). Verified: unchanged 154-assertion suite plus shellcheck under both Homebrew and an apt-get install shellcheck Ubuntu container. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Q4iokjvAbBLgrRJYwCVtqb
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Doc/skill batch from the v0.4.0 audit (docs/AUDIT-v0.4.0.md, P2). No hook behavior change.
.capture-errorsonce surfaced in a session log.plugin.jsonkeywords gaingit-state/cross-harness/resume/onboarding;tests/run.shheader states it's the single source of truth for the assertion count.Test plan
tests/run.sh: unchanged 154/154 passing (doc-only change, no new assertions expected)shellcheck -s sh hooks/*.sh tests/*.sh: clean under Homebrew AND an apt-installed Ubuntu containerjq .validates bothplugin.jsonandmarketplace.jsonCo-Authored-By: Claude Opus 5 noreply@anthropic.com