fix(skills): address develop workflow review

2026-09-04 10:47:04 -04:00
parent 1bab01799c
commit 1e213db45a
4 changed files with 26 additions and 41 deletions
@@ -8,7 +8,9 @@ Publish packages to the `jb` owner endpoint of the Gitea npm registry. Repositor

 `extensions/shared` is the publishable `@jbcode/pi-shared` library. Extensions that import it declare a normal runtime dependency so Pi's production package installation receives the required code.

-`extensions/_workflows` is reference code, not a package or publishable extension. The package-boundary decision remains valid, but [ADR 0006](./0006-skill-led-development-workflow-04SEP2026.md) supersedes the proposed runtime merge: `@jbcode/pi-workflow` now remains private, unpublished, and unexposed as historical pilot evidence.
+`extensions/_workflows` is reference code, not a package or publishable extension. `@jbcode/pi-workflow` remains a private workspace until the required reference runtime is merged under `extensions/workflow`; this prevents publishing two workflow packages or publishing an incomplete package.
+
+> **Later decision:** [ADR 0006](./0006-skill-led-development-workflow-04SEP2026.md) supersedes the workflow-specific merge and release direction above. Keep the legacy workspace private, unpublished, and unexposed during the skill pilot.

 The existing `config/pi-links.json` policy remains the authority for live-development exposure. Package boundaries and publication do not automatically enable extensions globally.

@@ -18,4 +20,4 @@ The existing `config/pi-links.json` policy remains the authority for live-develo
 - Catalog and workspace protocols require `bun publish` or `bun pm pack` before npm publication so concrete versions are written into package metadata.
 - Shared libraries must be published before extensions that depend on the same new version.
 - Pi packages continue shipping TypeScript source because Pi loads extension entrypoints directly.
- ADR 0006 removes a `workflow` extension release from the active plan; archival or removal follows the skill pilot.
+- The `workflow` merge is an explicit blocker for its first release.
@@ -22,4 +22,6 @@ Rename the private `pi-workflow` extension identity to `workflow`. Its workspace
 - Published packages use the scoped Gitea registry instead of Pi-managed Git sources.
 - Upstream movement is detected but never merged automatically; imported changes require reconciliation with monorepo-specific manifests and APIs.
 - Only `main` is tracked. Source tags, branches, and historical commits are not copied.
- The renamed `workflow` extension remains a private historical snapshot. [ADR 0006](./0006-skill-led-development-workflow-04SEP2026.md) supersedes its merge/release prerequisite with the skill pilot and a later retirement decision.
+- The renamed `workflow` extension remains private until its `_workflows` dependencies are merged and isolated packaging succeeds.
+
+> **Later decision:** [ADR 0006](./0006-skill-led-development-workflow-04SEP2026.md) supersedes this workflow-specific merge and release direction with the skill pilot and a later retirement decision.