@stdd/plugin 0.9.0 → 0.9.1

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "stdd",
-  "version": "0.9.0",
+  "version": "0.9.1",
   "description": "Native STDD workflow skills and lifecycle context",
   "author": {
     "name": "Azamat Almazbek uulu"

package/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "stdd",
-  "version": "0.9.0",
+  "version": "0.9.1",
   "description": "Native STDD workflow skills and lifecycle context for Codex",
   "author": {
     "name": "Azamat Almazbek uulu"

package/README.md

@@ -6,10 +6,13 @@ runtime; adopting repositories do not need a local `@stdd/cli` dependency.
 
 ## Install
 
-- **Codex:** install `stdd` from a Codex marketplace that points at this
-  directory.
-- **Claude Code:** install `stdd` from a Claude Code marketplace that points at
-  this directory.
+The STDD repository is its own marketplace for both plugin hosts, and its
+root catalog sources this directory.
+
+- **Codex:** `codex plugin marketplace add vsem-azamat/stdd`, then
+  `codex plugin add stdd@stdd`.
+- **Claude Code:** `/plugin marketplace add vsem-azamat/stdd`, then
+  `/plugin install stdd@stdd`.
 - **Pi:** `pi install npm:@stdd/plugin@<version>`. For a source checkout, use
   `pi install ./plugins/stdd`.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@stdd/plugin",
-  "version": "0.9.0",
+  "version": "0.9.1",
   "description": "Universal STDD workflow skills and lifecycle integration for Codex, Claude Code, and Pi",
   "type": "module",
   "license": "MIT",

package/runtime/method/reference-integration.md

@@ -88,10 +88,30 @@ The optional universal bundle at `plugins/stdd/` distributes one generated set
 of conservative-profile skills and one CLI runtime through native Codex and
 Claude Code plugin manifests or the `@stdd/plugin` Pi package. The runtime is
 generated from the same source and version as `@stdd/cli`; the adopting
-repository does not install that CLI package. The bundle never owns repository
+repository does not install that CLI package.
+
+The adoption modes are cumulative, and for Pi they overlap by name. Codex and
+Claude Code namespace a plugin's skills under the plugin, but Pi registers the
+bundle's skills into the same flat `.agents/skills` registry an initialized
+repository generates into, so every skill name exists twice. The repository's
+definition wins: it is generated for that checkout's selected hosts, while the
+bundle ships the conservative profile that assumes none of them. The bundle
+still supplies its lifecycle extension and runtime. Pi reports the overlap on
+interactive startup only, so a contract that watched a non-interactive run for
+that report would be watching a stream the host never writes to. The bundle never owns repository
 state: its lifecycle integration acts only when the checkout contains
 `.stdd/`; init, task state, policy, and optional CI stay with the repository.
 
+A host installs a plugin from a marketplace catalog, not from a bundle
+directory, so this repository root carries one catalog per host — Codex reads
+`.agents/plugins/marketplace.json` and Claude Code reads
+`.claude-plugin/marketplace.json`. Both list the single plugin `stdd`, sourced
+from the `plugins/stdd/` directory of the same checkout. Neither catalog names
+a version: `npm run build:plugin` aligns the bundle manifests and nothing above
+them, so a version restated in a catalog would be a second place to bump that
+no build touches. Each host resolves the installed version from the bundle
+manifest its entry sources.
+
 Codex and Claude Code use the bundle's fail-open SessionStart and Stop command
 hooks. If the bundled runtime cannot read an adopting checkout, SessionStart
 reports fixed update-or-reinitialize guidance and exits successfully; Stop

package/runtime/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@stdd/cli",
-	"version": "0.9.0",
+	"version": "0.9.1",
 	"description": "Spec + Test Driven Development — a markdown-first methodology kit for teams building software with AI coding agents",
 	"type": "module",
 	"exports": {

package/skills/stdd-brainstorming/SKILL.md

@@ -3,7 +3,7 @@ name: stdd-brainstorming
 description: "Shape a fuzzy idea into an agreed behavior contract before any plan or code. Use when: A non-trivial change is requested and the requirements, scope, or approach are not yet pinned down."
 ---
 
-<!-- generated by stdd plugin build v0.9.0 — do not edit -->
+<!-- generated by stdd plugin build v0.9.1 — do not edit -->
 
 
 # Brainstorming

package/skills/stdd-debugging/SKILL.md

@@ -3,7 +3,7 @@ name: stdd-debugging
 description: "Find and fix the root cause of a defect, not its symptom. Use when: A bug, crash, failing test, or unexplained behavior is reported."
 ---
 
-<!-- generated by stdd plugin build v0.9.0 — do not edit -->
+<!-- generated by stdd plugin build v0.9.1 — do not edit -->
 
 
 # Debugging

package/skills/stdd-delegate-slice/SKILL.md

@@ -3,7 +3,7 @@ name: stdd-delegate-slice
 description: "Hand a slice of work to a worker session with a declared scope, a ledger handoff, and a reviewed result. Use when: Before implementing a multi-step change whose steps are independent — hand slices to worker sessions (subagent, second CLI, teammate) instead of implementing everything inline; also whenever a worker's result comes back for review."
 ---
 
-<!-- generated by stdd plugin build v0.9.0 — do not edit -->
+<!-- generated by stdd plugin build v0.9.1 — do not edit -->
 
 
 # Delegate a Slice

package/skills/stdd-finish-change/SKILL.md

@@ -3,7 +3,7 @@ name: stdd-finish-change
 description: "Close an implemented change with independent review, PR evidence, terminal CI, and runtime verification when required. Use when: Implementation is locally verified and the change is ready for review, delivery, or handoff."
 ---
 
-<!-- generated by stdd plugin build v0.9.0 — do not edit -->
+<!-- generated by stdd plugin build v0.9.1 — do not edit -->
 
 
 # Finish change

package/skills/stdd-implement/SKILL.md

@@ -3,7 +3,7 @@ name: stdd-implement
 description: "Execute one agreed behavior slice through docs, genuine red, implementation, and fresh verification. Use when: The behavior contract is agreed and production changes are ready to begin."
 ---
 
-<!-- generated by stdd plugin build v0.9.0 — do not edit -->
+<!-- generated by stdd plugin build v0.9.1 — do not edit -->
 
 
 # Implement

package/skills/stdd-investigation/SKILL.md

@@ -3,7 +3,7 @@ name: stdd-investigation
 description: "Read-only diagnosis — evidence-backed findings, no changes. Use when: Asked to diagnose, triage, or explain behavior WITHOUT changing anything."
 ---
 
-<!-- generated by stdd plugin build v0.9.0 — do not edit -->
+<!-- generated by stdd plugin build v0.9.1 — do not edit -->
 
 
 # Investigation

package/skills/stdd-planning/SKILL.md

@@ -3,7 +3,7 @@ name: stdd-planning
 description: "Turn an agreed behavior contract into an executable, verifiable sequence of work. Use when: The behavior contract is agreed (docs edit drafted or committed) and the change is large enough to need ordered steps — before the first implementation edit, to fix the execution mode and delivery boundary."
 ---
 
-<!-- generated by stdd plugin build v0.9.0 — do not edit -->
+<!-- generated by stdd plugin build v0.9.1 — do not edit -->
 
 
 # Planning

package/skills/stdd-pr-green/SKILL.md

@@ -3,7 +3,7 @@ name: stdd-pr-green
 description: "A PR is done only when its required checks settle terminal-green on the current head. Use when: A PR/MR exists, or is about to be opened, for the current branch."
 ---
 
-<!-- generated by stdd plugin build v0.9.0 — do not edit -->
+<!-- generated by stdd plugin build v0.9.1 — do not edit -->
 
 
 # PR Green

package/skills/stdd-start-change/SKILL.md

@@ -3,7 +3,7 @@ name: stdd-start-change
 description: "Classify a request, open durable task state only for changes, and route to the smallest applicable workflow. Use when: A new implementation, fix, refactor, investigation, or repository change is beginning."
 ---
 
-<!-- generated by stdd plugin build v0.9.0 — do not edit -->
+<!-- generated by stdd plugin build v0.9.1 — do not edit -->
 
 
 # Start change

package/skills/stdd-worktrees/SKILL.md

@@ -3,7 +3,7 @@ name: stdd-worktrees
 description: "Work in an isolated workspace without fighting the platform's native isolation. Use when: Starting implementation work that should not disturb the user's current checkout."
 ---
 
-<!-- generated by stdd plugin build v0.9.0 — do not edit -->
+<!-- generated by stdd plugin build v0.9.1 — do not edit -->
 
 
 # Isolated Workspaces