Releases: L3DigitalNet/Claude-Code-Plugins
Releases · L3DigitalNet/Claude-Code-Plugins
up-docs v0.9.1
Changed
- propagate-repo: the
AGENTS.md/AGENTS.reviews.md/conventions.mdmandatory audit now explicitly scans for retired V1/V2 layout-detection language — pre-v3detect layout first. V2:… V1:…Session-state conditionals,V2 repos read… / V1 legacy…review-input conditionals, and stale(V2 handoff layout)version labels — and relabels them to the v3 single-path form. The catch was previously non-deterministic: a/up-docs:reporun after v0.9.0 shipped left twoAGENTS.mdstragglers and aconventions.mdlabel that only a later/up-docs:alldrift audit caught. Newtests/prompt-conformance.batsguard (52 bats total).
Added
- README "Propagation vs. drift" section +
/up-docs:reposkill note: the propagators (/up-docs:repo|wiki|notion) run no drift auditor and will not catch pre-existing drift the current session didn't introduce; run/up-docs:driftor/up-docs:allperiodically (e.g. after a release).
up-docs v0.9.0
[0.9.0] - 2026-05-30
Fixed
- propagate-repo:
AGENTS.mdremediation now emits the handoff v3 three-line block (Session state:/Full conventions reference:/Detailed review workflows:) — prior output failedvalidate-layout.sh's Codex block. (Bug #6) - propagate-repo: new bug files include
## Lesson(handoff v3 Cause/Fix/Lesson body). (Bug #6) - propagate-repo: state.md over-cap trim is route-first (route to sessions/deployed/architecture before deleting), per handoff v3.
Added
- propagate-repo: enforces
CLAUDE.md(≤2048) andAGENTS.md(≤4096) byte caps; auditsdocs/specs-plans.md; verifies bug-index regen withgit diff --exit-code. - audit-drift: conditional handoff-layout conformance phase — runs
~/projects/agent-configs/scripts/validate-layout.shagainst the project root when present and surfaces failures aslayer: "layout"findings (read-only; never fixes).
Changed
- Relabeled handoff "v2" → "v3"; removed stale
/mnt/share/migration pointer and superseded "Phase 5 / §9.2 / ≤200-line rules cap" references (not part of the v3 contract).
up-docs v0.8.4
Fixed
- State-condition the docs/state.md 2KB cap enforcement in the repo propagator. The rule previously read "if edits push over" (transition-conditioned), so an already-over-cap state.md never triggered the trim and grew unbounded across sessions. Now enforced whenever the file exceeds 2KB after the edit; trim guidance corrected to delete the oldest "Recently closed" sections (mirrored in docs/sessions/) rather than active incidents.
up-docs v0.8.3
Changed
- De-duplicated the handoff-brief + stale-candidate blocks across the all/repo skills into a shared templates/post-propagation-steps.md (single source of truth).
- Fixed templates/drift-finding.md evidence schema: free-form string → structured {command, expected_output_signature, source_tool_use_id?} object, matching the auditor and validate_output.py.
- Deleted the orphaned skills/notion/references/notion-guidelines.md (the agent inlines its own canonical copy); repaired its dangling pointers.
- Retagged audit-drift example #3 (host-unreachable) from confidence:"low" to "unverifiable" so it satisfies the validator (null evidence is permitted only for "unverifiable").
No behavior change; documentation/structure correctness + DRY. Suites: 48 bats + 26 pytest pass.
up-docs v0.8.2
Fixed
- remove unsound deny-guard PreToolUse hook
The deny-guard.sh PreToolUse/Bash hook fired on every Bash call in every session where up-docs was enabled, adding a per-command latency tax, and its scope detection was architecturally unsound (subagents run with isolated transcripts that never contain the parent Agent block). Replaced by the engine-enforced consumer-side permissions.deny block documented in README §Security. The opt-in PostToolUse capture hook is unchanged.
up-docs v0.8.1
[0.8.1] - 2026-05-25
Fixed
- repair bats suite — neutralize global git hook + add deny-guard transcript fixture
- scope deny-guard to up-docs subagents only
test-driver v0.6.1
[0.6.1] - 2026-05-25
Changed
- test-driver: Phase 2 — profile shape + manifest guard (4 cases)
Fixed
- canonicalize TEST-003 — bypass global git config in bats helper (recovers 4 silently-failing tests; suite 53/57 → 57/57)
repo-hygiene v1.4.1
[1.4.1] - 2026-05-25
Changed
- repo-hygiene: Phase 2 — 4 new bats files (17 cases) covering 4 untested scripts
Fixed
- canonicalize TEST-003 — bypass global git config in bats helper (recovers 11 silently-failing tests; suite 29/40 → 40/40)
release-pipeline v2.2.2
[2.2.2] - 2026-05-25
Fixed
bump-version.shplugin-mode now bumpsplugins/<name>/package.jsonandplugins/<name>/pyproject.tomlwhen the manifest'snamefield matches the plugin name (was previously skipped, leaving every plugin with a top-level package.json silently drifting from release to release — e.g. plugin-test-harness/package.json stuck at 0.7.2 through three releases). Defensive name-match guard leaves sub-component manifests (gh-manager, ha-dev-mcp-server, qt-pilot) untouched. 4 new tests added; suite now 15/15 (was 11/11).
release-pipeline v2.2.1
[2.2.1] - 2026-05-25
Changed
- release-pipeline: complete v2.2.0 testing-branch migration (verify-release.sh Check #4 deletion + tests/test_helper.bash core.hooksPath fix)