feat(slice 29 Checkpoint C): canonical-skills doc polish (HG-7 + HG-8)

Adjusts the 4 canonical SKILL.md files that
still contained <internal-docs> / <work-tree> / internal docs / substrate
references after Checkpoints A + B. The full canonical tree
(packages/daemon/specs/agents/shared/skills/) ended up cleaner than
the slice spec estimated — only 4 hits (not ~27) because most
canonical bodies had already been written path-agnostically.

Files touched:

core/openrig-user-settings: workspace-override example commands
rewritten from `/Users/me/code/<work-tree>/...` paths to
generic `/path/to/your/workspace/...` placeholders. Per banked
feedback_test_fixture_example_path_placeholder doctrine.

core/openrig-installer: V0.3.1 migration ceremony rewritten to be
path-agnostic. References to `~/code/substrate/<internal-docs>/rigs/kernel/`
replaced with "wherever you kept your own rigs/kernel/ directory" or
`/path/to/old/kernel-spec` placeholders. Migration steps still work
for both internal substrate-rooted operators and external users with
any non-default kernel location.

core/openrig-architect: source_evidence shortened to the operator-
relevant bootstrap line (was 3 lines including substrate-cross-ref +
import-history). Host-level doctrine paragraph rewritten path-agnostic
(matches the Checkpoint B fix to the plugin-side mirror of this skill).

core/rig-lifecycle: source_evidence one-liner rewritten to drop the
substrate-path translation breadcrumb + specific openrig SHAs.

Mirror skills propagated to skills/_canonical/ (4 files).

VERIFICATION:
- /usr/bin/find … SKILL.md … grep -c "<internal-docs>|<work-tree>|internal docs"
  → 0 hits across both canonical tree AND plugin tree. HG-6 + HG-7
  fully closed.
- Daemon focused suite: 73/73 green (openrig-core-plugin +
  skill-library-routes + plugin-files-routes + plugins-routes).
- Daemon full suite at baseline: 3600 pass + 1 skipped + 2 pre-existing
  fails (precompact-hook HG-7 OPENRIG_HOME + restore-check hook-cwd;
  verified pre-existing on pristine main pre-slice-29).
- All adjusted skills preserve frontmatter validity (HG-9 — skill
  discovery validation tests green).

HG-8 (See Also operator-reachable) now closed end-to-end:
- Plugin side (Checkpoint B): 8 files; broken refs to deleted skills
  (claude-compact-in-place / session-compaction-and-restore /
  permission-posture) replaced with peer-skill or rig-command pointers.
- Canonical side (this checkpoint): 4 files; substrate-path
  references in See Also lists replaced with path-agnostic prose.

Following: velocity-qa HG-12 VM cumulative walk pending guard
ADVISORY-CLEAN on Checkpoint C.

Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
This commit is contained in:
mvschwarzandClaude Opus 4.7 committed 2026-05-13 00:35:42 -07:00
1 parent e522d959e9
commit baacfe808d
8 files changed
+28 -40

No files matched your search

@@ -7,8 +7,6 @@ metadata:
last_verified: "2026-05-04"
distribution_scope: product-bound
source_evidence: |
Imported 2026-05-02 from openrig/packages/daemon/specs/agents/shared/skills/rig-architect/SKILL.md (349 lines).
Product built-in is the only source — substrate/shared-docs/skills/rig-architect/ does not exist.
Bootstrap skill — NPM install lands this in personal homes (~/.claude/skills/, ~/.agents/skills/) for users authoring their own rigs.
sibling_skills:
- openrig-user
@@ -56,12 +54,7 @@ Load these before starting any design work. The quality of your output depends o
**Read if present on this host:**
4. **Host-level doctrine** at `~/code/substrate/shared-docs/HOST-TOPOLOGY.md` (or wherever substrate lives on this host). If this file exists, it supersedes the baseline process below for complex or high-stakes rigs. Specifically:
- §3 defines the canonical rig classes (kernel, project, ephemeral, infra-build, managed-app). Classify before designing.
- §4 defines context-sharing patterns (pods as context domains, pair pattern, HA via mental-model-ha skill + substrate session logs, terminal nodes as common-room, chatroom/substrate/transcripts/Corpus).
- **§7 is the canonical 12-step rig-spec authoring SOP for high-stakes rigs — use it instead of the baseline "Design Process" below when the rig is ≥4 members, uses HA, is a managed-app, or will be shared/copied.** The baseline below still applies to small/focused rigs.
- §10 contains the host's bootstrap sequence so you know where your new rig fits.
- §12 has the naming canon and vocabulary mapping to shipped terms.
4. **Host-level doctrine file** (if your team maintains one — e.g., a HOST-TOPOLOGY doc that defines canonical rig classes, context-sharing patterns, and authoring SOPs for high-stakes rigs). If present, it supersedes the baseline process below for complex or high-stakes rigs (≥4 members, HA, managed-app, or shared/copied). Solo operators and small/focused rigs use the baseline below directly.
5. **`building-agent-software` skill** if available in your skill catalog. Design principles for agent-facing tools and surfaces. Relevant when your rig ships a new CLI, service, or managed app.
**Load as needed:**
@@ -51,9 +51,9 @@ Or click the CMUX button on the topology graph in the UI at
## V0.3.1 upgrade ceremony (one-time migration)
Operators with an existing substrate-rooted kernel at
`~/code/substrate/shared-docs/rigs/kernel/` (the pre-V0.3.1 layout)
must migrate to the daemon-managed location
Operators with a kernel spec stored outside the daemon-managed
location (any pre-V0.3.1 layout, typically wherever you kept your
own `rigs/kernel/` directory) must migrate to
`~/.openrig/specs/rigs/kernel/` as a one-time step during the V0.3.1
upgrade. The V0.3.1 upgrade IS the migration moment; it's not a
separate ceremony.
@@ -74,12 +74,12 @@ separate ceremony.
rig down kernel --snapshot
```
3. **Copy the substrate kernel spec** into the daemon-managed
3. **Copy your existing kernel spec** into the daemon-managed
location:
```bash
mkdir -p ~/.openrig/specs/rigs/kernel
cp -r ~/code/substrate/shared-docs/rigs/kernel/* ~/.openrig/specs/rigs/kernel/
cp -r /path/to/old/kernel-spec/* ~/.openrig/specs/rigs/kernel/
```
4. **Upgrade the CLI + daemon**:
@@ -101,11 +101,11 @@ separate ceremony.
rig ps --nodes --rig kernel --json
```
6. **Decommission the substrate copy** (only after verifying the
6. **Decommission the old copy** (only after verifying the
daemon-managed copy works):
```bash
rm -rf ~/code/substrate/shared-docs/rigs/kernel
rm -rf /path/to/old/kernel-spec
```
### If migration fails
@@ -86,10 +86,10 @@ Resolution order for workspace per-subdir keys: per-subdir override >
> set the per-subdir workspace overrides explicitly:
>
> ```bash
> rig config set workspace.slices_root /Users/me/code/substrate/.../missions
> rig config set workspace.steering_path /Users/me/code/substrate/openrig-work/STEERING.md
> rig config set workspace.progress_scan_roots 'work:/Users/me/code/substrate/openrig-work,missions:/Users/me/code/substrate/openrig-work/missions'
> rig config set workspace.field_notes_root /Users/me/code/substrate/openrig-work/field-notes
> rig config set workspace.slices_root /path/to/your/workspace/missions
> rig config set workspace.steering_path /path/to/your/workspace/STEERING.md
> rig config set workspace.progress_scan_roots 'work:/path/to/your/workspace,missions:/path/to/your/workspace/missions'
> rig config set workspace.field_notes_root /path/to/your/workspace/field-notes
> ```
>
> No restart needed for the CLI; for the daemon's reads to pick up
@@ -7,7 +7,8 @@ metadata:
last_verified: "2026-05-04"
distribution_scope: product-bound
source_evidence: |
Translated from openrig-work/primitives/runtime-control/rig-lifecycle.md (102 lines, matrix-proof-complete-tier-1-with-tier-2-human-gated). Lifecycle Reboot/Recovery Scenario Matrix slice closed at openrig ab01331 (2026-04-30); Codex auth-refusal → attention_required closed at 53e9409 same day.
Lifecycle Reboot/Recovery Scenario Matrix (Tier 1 complete; Tier 2
human-gated). Codex auth-refusal surfaces as attention_required.
sibling_skills:
- topology-mutation-and-seat-management
- seat-scaling-and-specialization
@@ -7,8 +7,6 @@ metadata:
last_verified: "2026-05-04"
distribution_scope: product-bound
source_evidence: |
Imported 2026-05-02 from openrig/packages/daemon/specs/agents/shared/skills/rig-architect/SKILL.md (349 lines).
Product built-in is the only source — substrate/shared-docs/skills/rig-architect/ does not exist.
Bootstrap skill — NPM install lands this in personal homes (~/.claude/skills/, ~/.agents/skills/) for users authoring their own rigs.
sibling_skills:
- openrig-user
@@ -56,12 +54,7 @@ Load these before starting any design work. The quality of your output depends o
**Read if present on this host:**
4. **Host-level doctrine** at `~/code/substrate/shared-docs/HOST-TOPOLOGY.md` (or wherever substrate lives on this host). If this file exists, it supersedes the baseline process below for complex or high-stakes rigs. Specifically:
- §3 defines the canonical rig classes (kernel, project, ephemeral, infra-build, managed-app). Classify before designing.
- §4 defines context-sharing patterns (pods as context domains, pair pattern, HA via mental-model-ha skill + substrate session logs, terminal nodes as common-room, chatroom/substrate/transcripts/Corpus).
- **§7 is the canonical 12-step rig-spec authoring SOP for high-stakes rigs — use it instead of the baseline "Design Process" below when the rig is ≥4 members, uses HA, is a managed-app, or will be shared/copied.** The baseline below still applies to small/focused rigs.
- §10 contains the host's bootstrap sequence so you know where your new rig fits.
- §12 has the naming canon and vocabulary mapping to shipped terms.
4. **Host-level doctrine file** (if your team maintains one — e.g., a HOST-TOPOLOGY doc that defines canonical rig classes, context-sharing patterns, and authoring SOPs for high-stakes rigs). If present, it supersedes the baseline process below for complex or high-stakes rigs (≥4 members, HA, managed-app, or shared/copied). Solo operators and small/focused rigs use the baseline below directly.
5. **`building-agent-software` skill** if available in your skill catalog. Design principles for agent-facing tools and surfaces. Relevant when your rig ships a new CLI, service, or managed app.
**Load as needed:**
@@ -51,9 +51,9 @@ Or click the CMUX button on the topology graph in the UI at
## V0.3.1 upgrade ceremony (one-time migration)
Operators with an existing substrate-rooted kernel at
`~/code/substrate/shared-docs/rigs/kernel/` (the pre-V0.3.1 layout)
must migrate to the daemon-managed location
Operators with a kernel spec stored outside the daemon-managed
location (any pre-V0.3.1 layout, typically wherever you kept your
own `rigs/kernel/` directory) must migrate to
`~/.openrig/specs/rigs/kernel/` as a one-time step during the V0.3.1
upgrade. The V0.3.1 upgrade IS the migration moment; it's not a
separate ceremony.
@@ -74,12 +74,12 @@ separate ceremony.
rig down kernel --snapshot
```
3. **Copy the substrate kernel spec** into the daemon-managed
3. **Copy your existing kernel spec** into the daemon-managed
location:
```bash
mkdir -p ~/.openrig/specs/rigs/kernel
cp -r ~/code/substrate/shared-docs/rigs/kernel/* ~/.openrig/specs/rigs/kernel/
cp -r /path/to/old/kernel-spec/* ~/.openrig/specs/rigs/kernel/
```
4. **Upgrade the CLI + daemon**:
@@ -101,11 +101,11 @@ separate ceremony.
rig ps --nodes --rig kernel --json
```
6. **Decommission the substrate copy** (only after verifying the
6. **Decommission the old copy** (only after verifying the
daemon-managed copy works):
```bash
rm -rf ~/code/substrate/shared-docs/rigs/kernel
rm -rf /path/to/old/kernel-spec
```
### If migration fails
@@ -86,10 +86,10 @@ Resolution order for workspace per-subdir keys: per-subdir override >
> set the per-subdir workspace overrides explicitly:
>
> ```bash
> rig config set workspace.slices_root /Users/me/code/substrate/.../missions
> rig config set workspace.steering_path /Users/me/code/substrate/openrig-work/STEERING.md
> rig config set workspace.progress_scan_roots 'work:/Users/me/code/substrate/openrig-work,missions:/Users/me/code/substrate/openrig-work/missions'
> rig config set workspace.field_notes_root /Users/me/code/substrate/openrig-work/field-notes
> rig config set workspace.slices_root /path/to/your/workspace/missions
> rig config set workspace.steering_path /path/to/your/workspace/STEERING.md
> rig config set workspace.progress_scan_roots 'work:/path/to/your/workspace,missions:/path/to/your/workspace/missions'
> rig config set workspace.field_notes_root /path/to/your/workspace/field-notes
> ```
>
> No restart needed for the CLI; for the daemon's reads to pick up
@@ -7,7 +7,8 @@ metadata:
last_verified: "2026-05-04"
distribution_scope: product-bound
source_evidence: |
Translated from openrig-work/primitives/runtime-control/rig-lifecycle.md (102 lines, matrix-proof-complete-tier-1-with-tier-2-human-gated). Lifecycle Reboot/Recovery Scenario Matrix slice closed at openrig ab01331 (2026-04-30); Codex auth-refusal → attention_required closed at 53e9409 same day.
Lifecycle Reboot/Recovery Scenario Matrix (Tier 1 complete; Tier 2
human-gated). Codex auth-refusal surfaces as attention_required.
sibling_skills:
- topology-mutation-and-seat-management
- seat-scaling-and-specialization