Skip to content

Releases: L3DigitalNet/Claude-Code-Plugins

up-docs v0.9.1

30 May 09:13
up-docs/v0.9.1
4e52ba9

Choose a tag to compare

Changed

  • propagate-repo: the AGENTS.md / AGENTS.reviews.md / conventions.md mandatory audit now explicitly scans for retired V1/V2 layout-detection language — pre-v3 detect 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:repo run after v0.9.0 shipped left two AGENTS.md stragglers and a conventions.md label that only a later /up-docs:all drift audit caught. New tests/prompt-conformance.bats guard (52 bats total).

Added

  • README "Propagation vs. drift" section + /up-docs:repo skill 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:drift or /up-docs:all periodically (e.g. after a release).

up-docs v0.9.0

30 May 07:38
up-docs/v0.9.0
420a9af

Choose a tag to compare

[0.9.0] - 2026-05-30

Fixed

  • propagate-repo: AGENTS.md remediation now emits the handoff v3 three-line block (Session state: / Full conventions reference: / Detailed review workflows:) — prior output failed validate-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) and AGENTS.md (≤4096) byte caps; audits docs/specs-plans.md; verifies bug-index regen with git diff --exit-code.
  • audit-drift: conditional handoff-layout conformance phase — runs ~/projects/agent-configs/scripts/validate-layout.sh against the project root when present and surfaces failures as layer: "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

29 May 21:39
up-docs/v0.8.4
0d89372

Choose a tag to compare

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

29 May 21:13
up-docs/v0.8.3
15dd8a7

Choose a tag to compare

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

29 May 20:35
up-docs/v0.8.2
9c2fbdb

Choose a tag to compare

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

25 May 21:00
up-docs/v0.8.1
cbb9c7b

Choose a tag to compare

[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

25 May 21:41
test-driver/v0.6.1
5da674f

Choose a tag to compare

[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

25 May 21:37
repo-hygiene/v1.4.1
bc93937

Choose a tag to compare

[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

25 May 22:09
release-pipeline/v2.2.2
4b4e2f9

Choose a tag to compare

[2.2.2] - 2026-05-25

Fixed

  • bump-version.sh plugin-mode now bumps plugins/<name>/package.json and plugins/<name>/pyproject.toml when the manifest's name field 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

25 May 21:32
release-pipeline/v2.2.1
c0d4d46

Choose a tag to compare

[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)