archik 0.7.4 → 0.7.5
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.
- package/.claude/commands/archik/spawn.md +18 -0
- package/.claude/skills/archik/SKILL.md +2 -0
- package/dist/cli/archik.mjs +179 -179
- package/package.json +1 -1
|
@@ -131,12 +131,30 @@ archik suggest set` stages it.
|
|
|
131
131
|
nodes: [ ... ]
|
|
132
132
|
edges: [ ... ]
|
|
133
133
|
YAML
|
|
134
|
+
# mechanical: puts sub-file on disk so the main draft's
|
|
135
|
+
# archikFile: pointer validates. NOT the user's review gate
|
|
136
|
+
# on the main draft — that one is always left as a sidecar.
|
|
134
137
|
npx archik suggest accept .archik/<id>.archik.yaml
|
|
135
138
|
```
|
|
136
139
|
Repeat for every sub-file. The `accept` step is what makes
|
|
137
140
|
the file real on disk — without it the orphan sidecar lingers
|
|
138
141
|
and the canvas shows it as "(pending)" rather than rendering it.
|
|
139
142
|
|
|
143
|
+
**Narrate each auto-accept with its rationale**, not just
|
|
144
|
+
"accept each". The user must be able to tell from your status
|
|
145
|
+
line that you are NOT bypassing their `/archik:accept` review
|
|
146
|
+
on the main draft. Example narration:
|
|
147
|
+
|
|
148
|
+
> Auto-accepting `agent` sub-file so the main draft can
|
|
149
|
+
> reference it via `archikFile:` — the next `suggest set`
|
|
150
|
+
> would fail validation otherwise. The main draft will still
|
|
151
|
+
> be left as a sidecar for you to review.
|
|
152
|
+
|
|
153
|
+
The main draft (step 8b) is always left as a sidecar.
|
|
154
|
+
`/archik:accept` is the user's gate; `npx archik suggest
|
|
155
|
+
accept <sub-file>` here is mechanical plumbing for the
|
|
156
|
+
cross-file reference, not a substitute for that gate.
|
|
157
|
+
|
|
140
158
|
b. **Main draft**: once all sub-files exist (i.e. their
|
|
141
159
|
`accept`s succeeded), stage the main one. No `--allow-orphan`
|
|
142
160
|
needed because the main file already exists from `archik init`:
|
|
@@ -39,6 +39,8 @@ If `npx archik` is unreachable (offline, sandboxed, missing), STOP and tell the
|
|
|
39
39
|
| `/archik:reject` | Discard the pending suggestion |
|
|
40
40
|
| `/archik:dev` | Open the live canvas |
|
|
41
41
|
|
|
42
|
+
Slash commands are typed **by the user**, not by you. You always run `npx archik` directly. When a workflow internally needs `suggest accept` (e.g. spawn's sub-file step — the parent draft references sub-files via `archikFile:` and `suggest set` validates target-on-disk), narrate the rationale so the user can tell you are not bypassing their `/archik:accept` review on the main draft. The main draft is always left as a sidecar.
|
|
43
|
+
|
|
42
44
|
When a user types `/archik:suggest`, `/archik:spawn`, or `/archik:evolve`, treat it as direct authorisation to run the sidecar workflow now — skip "want me to update the YAML?". Each command's body file under `.claude/commands/archik/` has the full protocol; follow it.
|
|
43
45
|
|
|
44
46
|
Distinction:
|