v9.30 - reunify Rules plugin under one package

Summary

• re-unify the Rules plugin under RULES/plugin
• ship compact helper behavior and the session-coordination skill from the same Rules-owned package again
• keep the public install target as claude-code-rules@darkwingtm

What changed

Unified package model

• restored compact lifecycle hooks and helper scripts into RULES/plugin
• kept session-coordination-bridge in the same package
• removed the split package story from RULES docs

Marketplace/install model

• kept claude-code-rules@darkwingtm as the public install target
• kept claude-code-rules@claude-code-rules as local development/testing only
• updated the shared darkwingtm marketplace so claude-code-rules resolves from the unified Rules-owned package source
• removed duplicate maintained package copies from the shared plugin workspace

Governance sync

• added patch/unified-rules-plugin-rollout.patch.md
• added phase/phase-043-01-reunify-rules-plugin-source.md
• added phase/phase-043-02-sync-unified-plugin-surfaces.md
• synchronized README.md, TODO.md, design/design.md, design/rules-plugin-extension.design.md, changelog/changelog.md, changelog/rules-plugin-extension.changelog.md, and phase/SUMMARY.md

Verification

• validated the unified Rules plugin package with claude plugins validate
• confirmed claude-code-rules@darkwingtm is installed and enabled
• confirmed the unified plugin scripts now use claude-code-rules runtime identity and schema prefixes
• confirmed wave 043 is fully present in the phase summary, including the review summary

v9.29 - finalize plugin topology correction docs

Summary

• finalize the two-plugin topology docs after the wave 042 correction
• keep rules-compact-extension as the compact/context helper
• keep claude-code-rules as the session-coordination skill plugin

What changed

Final topology wording cleanup

• tightened the RULES-side plugin package docs so claude-code-rules is described consistently as a skill-only package
• removed remaining compact-helper drift from the skill-plugin docs
• kept rules-compact-extension as the explicit owner of compact helper behavior

Install guidance cleanup

• kept the public install target as claude-code-rules@darkwingtm
• kept claude-code-rules@claude-code-rules only as local development/testing
• tightened shared-doc wording so public install guidance uses portable placeholders instead of workstation-specific defaults

Governance sync

• finalized design/rules-plugin-extension.design.md at v1.12
• finalized changelog/rules-plugin-extension.changelog.md at v1.12
• advanced the master changelog and design inventory to v9.29
• completed the remaining wave 042 sync details in README/TODO/patch/master surfaces

Verification

• validated the RULES-side skill plugin package with claude plugins validate
• confirmed claude-code-rules@darkwingtm is installed and enabled
• confirmed rules-compact-extension@darkwingtm remains installed and enabled
• confirmed the final topology docs are aligned to the corrected two-plugin model

v9.28 - topology correction for rules skill plugin

Summary

• keep rules-compact-extension as the active compact/context helper
• narrow claude-code-rules into the session-coordination skill plugin only
• correct wave 042 docs, install guidance, and release surfaces to the two-plugin model

What changed

Topology correction

• claude-code-rules no longer ships compact hooks or compact persistence behavior
• rules-compact-extension remains the active compact helper
• claude-code-rules now owns only the session-coordination-bridge skill surface

Install model

• public install target is now claude-code-rules@darkwingtm
• local claude-code-rules@claude-code-rules is retained only for local development/testing
• the shared darkwingtm marketplace was restored and refreshed

Governance sync

• added patch/plugin-topology-correction.patch.md
• added phase/phase-042-01-correct-plugin-topology.md
• added phase/phase-042-02-sync-plugin-topology-surfaces.md
• synchronized README.md, TODO.md, design/rules-plugin-extension.design.md, design/design.md, changelog/changelog.md, changelog/rules-plugin-extension.changelog.md, and phase/SUMMARY.md

Verification

• validated the finalized RULES skill plugin package with claude plugins validate
• restored the shared darkwingtm marketplace
• confirmed rules-compact-extension@darkwingtm remains installed and enabled
• confirmed claude-code-rules@darkwingtm installs successfully and is enabled
• removed the local claude-code-rules@claude-code-rules install from active use

v9.27 - session coordination bridge skill rollout

Summary

Wave 041 turns the optional RULES plugin companion from a compact-hook-only helper into a broader but still bounded claude-code-rules support package.

What changed

• renamed the optional plugin companion from rules-compact-extension to claude-code-rules
• added claude-code-rules:session-coordination-bridge as an operator-facing support skill for multi-session coordination workflow
• kept the plugin in the support layer only, without moving semantic authority away from root RULES
• synchronized wave 041 governance artifacts across patch, phase, design, README, TODO, and changelog surfaces

Detailed improvements

1. New coordination support skill

Added plugin/skills/session-coordination-bridge/ with:

• SKILL.md
• overview.md
• capability-detection.md
• coordination-flow.md
• request-contract.md
• examples.md

This skill now gives a bounded front door for:

• shared-board-first coordination
• request-layer vs execution-layer separation
• receiving-side remap into the local execution structure
• sync-back discipline
• availability-first handling for optional memsearch and optional peer signaling

2. Coordination model made operator-visible

The new skill documents one explicit stack:

1. shared task list
2. phase / phase/SUMMARY.md / TODO.md / checked implementation state
3. native memory
4. memsearch
5. claude-peers-mcp

Practical effect:

• board = coordination state
• phase/TODO/design/code = semantic truth
• memory = continuity help only
• memsearch = optional recall accelerator
• claude-peers-mcp = optional live signaling layer

3. Plugin identity and install path aligned

The plugin package metadata and marketplace manifest now use:

• plugin name: claude-code-rules
• marketplace name: claude-code-rules
• package version: 1.3.1

The documented install/update shape is now:

• claude-code-rules@claude-code-rules

Migration guidance was also added for older installs that still use:

• rules-compact-extension@darkwingtm

4. Compact runtime identity aligned with the new package name

The visible compact resume signal changed from:

• [rules-compact-extension] ...

to:

• [claude-code-rules] ...

This keeps runtime-visible output aligned with the renamed plugin package.

5. Persisted compact-state schema contract updated

Compact state schema prefixes were changed from:

• rules-compact-extension/*

to:

• claude-code-rules/*

This applies to:

• pending state
• precompact context
• selected carry-forward state
• sessionstart proof
• sessionstart directive proof

6. Plugin design contract expanded

design/rules-plugin-extension.design.md now explicitly allows one operator-facing coordination skill in the plugin companion while preserving these boundaries:

• plugin may expose support skill(s)
• plugin may not become semantic owner of shared execution coordination
• memsearch stays optional
• claude-peers-mcp stays optional and non-required

7. Master repo surfaces synced

Wave 041 was added and synchronized in:

• patch/session-coordination-bridge-skill-rollout.patch.md
• phase/phase-041-01-add-session-coordination-bridge-skill.md
• phase/phase-041-02-sync-session-coordination-skill-surfaces.md
• phase/SUMMARY.md
• design/rules-plugin-extension.design.md
• design/design.md
• README.md
• TODO.md
• changelog/rules-plugin-extension.changelog.md
• changelog/changelog.md

What did not change

• active root runtime rule count remains 40
• no new first-class root runtime rule chain was created
• claude-peers-mcp was not activated as required infrastructure
• shared execution semantics still remain owned by root RULES, not by the plugin

Verification

• validated the plugin package manifest with claude plugins validate
• installed the plugin locally as claude-code-rules@claude-code-rules
• confirmed the installed package exposes skills/session-coordination-bridge/
• confirmed the plugin is already at latest version 1.3.1
• confirmed wave 041 governance surfaces were synchronized and cross-linked

v9.26 - memsearch availability-first intake fallback

Summary

• make receive-side optional recall intake check whether memsearch is actually available before relying on it
• fall back immediately to native memory plus checked execution surfaces when the optional extension is absent or the availability/probe step fails
• keep memsearch supplemental and non-authoritative instead of turning missing plugin state into a blocker
• sync touched design/runtime/changelog/master surfaces and reinstall the touched runtime rules while keeping the active runtime count at 40

Included wave

• wave 040: memsearch availability-detection and fallback-intake refinement

v9.25 - universal session-owned task title grammar

Summary

• make visible session ownership the default task-list standard for session-owned work across usage modes
• keep request, held, and blocked title forms semantically distinct instead of forcing one ambiguous prefix everywhere
• align phase-linked execution work to held-owner titles once the task is already locally owned
• sync touched design/runtime/changelog/master surfaces and reinstall the touched runtime rules while keeping the active runtime count at 40

Included wave

• wave 039: universal session-owned task title grammar

v9.24 - shared-board operating detail refinement

Summary

• make session-held shared-board work more visibly identifiable
• add a clearer handoff lifecycle and retention-matrix model for shared execution boards
• clarify that optional memsearch-style recall is supplemental and should follow stronger execution-surface identification
• sync touched design/runtime/changelog/master surfaces, resync installed runtime rules, and clear stale historical phase-review drift so the repo is release-clean again

Included waves

• wave 038: shared-board visibility, retention, and memsearch operating detail refinement
• bounded cleanup: coordination-companion reference sync and legacy phase review-state normalization

v9.23 - handoff request vs receiving phase boundary

Summary

• separate shared-board request naming from receiving-side execution phase ownership
• keep sender phase out of default visible handoff titles
• move source trace into handoff notes and let the receiving session remap accepted work into its own phase/objective structure
• sync master surfaces and reinstall touched runtime rules while keeping the active runtime count at 40

Included wave

• wave 037: handoff request vs receiving phase boundary

v9.22 - shared execution coordination

Summary

• create a first-class shared-execution-coordination rule chain for multi-session shared boards
• add bounded companion deferrals across task, phase, execution, repository, memory, and authority owners
• add continuity-first retention, anti-overclear policy, optional memsearch support, and future-optional peer-messaging boundaries
• sync master surfaces and expand the active runtime install set from 39 to 40 rules

Included wave

• wave 036: shared execution coordination

v9.21 - next-work discovery from execution surfaces

Summary

• add bounded next-work discovery from execution surfaces to execution continuity
• make the task list the first discovery surface with bounded fallback to phase, TODO, and checked implementation state
• sync phase, patch, master docs, and installed runtime copies without changing the active runtime count of 39

Included wave

• wave 035: next-work discovery from execution surfaces