pi-namespace-patch 1.0.2-namespace.1 → 1.0.2-namespace.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +21 -3
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -60,7 +60,7 @@ As a **user** there is nothing to learn — install, and packages that declare a
60
60
 
61
61
  ```bash
62
62
  npm install -g pi-namespace-patch
63
- pi --version # 1.0.2-namespace.1
63
+ pi --version # 1.0.2-namespace.2
64
64
  ```
65
65
 
66
66
  As a **package author**, add the `pi.namespace` field (two lines above), publish, and your resources are invocable in-session:
@@ -70,7 +70,25 @@ As a **package author**, add the `pi.namespace` field (two lines above), publish
70
70
  /skill:acme:review # the unambiguous skill form
71
71
  ```
72
72
 
73
- A real consumer: the [solidforge](https://github.com/maskshell/solidforge-pi) toolchain exposes its agent skills as `solidforge:*` through this mechanism.
73
+ A real consumer — [solidforge-pi](https://github.com/maskshell/solidforge-pi) — declares the field and ships both kinds of resources:
74
+
75
+ ```json
76
+ {
77
+ "name": "solidforge-pi",
78
+ "pi": {
79
+ "namespace": "solidforge",
80
+ "skills": ["./skills"],
81
+ "prompts": ["./prompts"]
82
+ }
83
+ }
84
+ ```
85
+
86
+ Its `skills/blueprint-crafting/SKILL.md` keeps the bare `name: blueprint-crafting` frontmatter and its `prompts/arm-tools.md` keeps a plain filename; in-session they surface as:
87
+
88
+ ```
89
+ /skill:solidforge:blueprint-crafting
90
+ /solidforge:arm-tools
91
+ ```
74
92
 
75
93
  ## How it works
76
94
 
@@ -89,7 +107,7 @@ The mechanics, in order of depth:
89
107
 
90
108
  - The version scheme `X.Y.Z-namespace.N` mirrors the upstream release it tracks (`X.Y.Z`) plus the fork patch revision (`N`). **Pin exact versions** — never ranges.
91
109
  - Each upstream release flows through an automated pipeline: release detection, mechanical re-base, agent repair on conflict, full check chain plus touched suites, then OIDC trusted publishing with signed provenance.
92
- - `pi --version` on this alias reports `1.0.2-namespace.1` (registry-stamped); the [GitHub tarball](https://github.com/maskshell/pi/releases/download/v1.0.2-namespace.1/earendil-works-pi-coding-agent-1.0.2-namespace.1.tgz) reports the workspace form `1.0.2+namespace.1` — same build, never rebuilt.
110
+ - `pi --version` on this alias reports `1.0.2-namespace.2` (registry-stamped); the [GitHub tarball](https://github.com/maskshell/pi/releases/download/v1.0.2-namespace.1/earendil-works-pi-coding-agent-1.0.2-namespace.1.tgz) reports the workspace form `1.0.2+namespace.2` — same build, never rebuilt.
93
111
 
94
112
  ## Provenance and trust
95
113
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "pi-namespace-patch",
3
- "version": "1.0.2-namespace.1",
3
+ "version": "1.0.2-namespace.2",
4
4
  "description": "Coding agent CLI with read, bash, edit, write tools and session management — maskshell fork build with the pi.namespace patch (earendil-works/pi#8834)",
5
5
  "type": "module",
6
6
  "piConfig": {