@techgoblin/gobstack 0.4.4-beta.6 → 0.4.4-beta.8

package/skills/goblin-bootstrap/SKILL.md

@@ -9,11 +9,16 @@ Use when adopting goblin-stack in a repo, or starting one.
 
 1. **Classify the project A-F.** The class selects which parts are required, optional or off;
    it is not a stringency level. F is a desktop shell: it adds the electron bans and a host gate.
-2. **`goblin-install --target <dir> --class <x>`**
-3. **`goblin-verify`** — a class-A install verifies green: `43 passed, 0 failed, 11
-   advisory, 28 skipped`, exit 0, once `HANDOFF.md` names a commit that exists; before that edit the
-   scaffold's `0000000` placeholder is `HP-05`'s one expected day-one red (`42 passed, 1 failed`).
-   Twenty-eight rows skip with a reason, and the reason matters: `HS-02`
+2. **`goblin-install --target <dir> --class <x>`** — the default install is a NEUTRAL harness:
+   no agent skills. Opt in per platform afterwards with `gob emit --platform <p>` (or vendor the
+   Hermes project tier with `--skills yes`).
+3. **`goblin-verify`** — a default class-A install (no agent skills) verifies green:
+   `38 passed, 0 failed, 11 advisory, 33 skipped`, exit 0, once `HANDOFF.md` names a commit that
+   exists; before that edit the
+   scaffold's `0000000` placeholder is `HP-05`'s one expected day-one red (`37 passed, 1 failed`).
+   Thirty-three rows skip with a reason, and the reason matters: the five skill rows
+   (`SK-01`..`SK-04`, `AU-04`) skip on the `playbooks` opt-out a skills-free install records,
+   then `HS-02`
    (no pinned pre-change commit yet, so the REPLAY is not provable), `AU-02`/`AU-03` (no report
    has been filed in this repo), `SC-06`/`SC-07`/`SC-08` (no dependency manifest, no lockfile, no
    audit record), `PF-01` (no perf baseline measured yet), `BN-01`/`BN-02`/`BN-05` (the ban table is

package/templates/AGENTS.md.tmpl

@@ -1,23 +1,32 @@
 # AGENTS.md
 
-This repository uses **goblin-stack** (class `{{CLASS}}`, installed {{DATE}}). It is a pointer,
+This repository uses **gobstack** (class `{{CLASS}}`, installed {{DATE}}). It is a pointer,
 not a rule dump — the rules live in one executable place, and facts beat requirements.
 
+- **Harness entry point:** `.goblin/bin/goblin-verify` — exit 0 pass, 1 a check failed,
+  2 could not run, 3 the manifest is broken. Run it before you commit; the gate is the
+  same run.
 - **Rules and their checks:** `.goblin/manifest/enforcement.tsv` (one row per rule; every row
   carries a runnable check or the literal `advisory`).
 - **Forbidden code (the ban list):** `.goblin/bin/goblin-bans` runs the bans named by `bans:` in
   `.goblin/goblin.yaml`; each ban's mechanism lives in `.goblin/manifest/bans.tsv`. Run it before
   you write the line, not after — a ban is a gate, and `goblin-verify` only reports it once the
   code exists.
-- **Verify:** `.goblin/bin/goblin-verify` — exit 0 pass, 1 a check failed, 2 could not run,
-  3 the manifest is broken.
-- **Procedures:** the skills installed at `.hermes/skills/` (Hermes project tier — highest
-  precedence, repo-owned). Start with `goblin-mode`, which routes a request to a playbook.
 - **Session state:** `HANDOFF.md` at the repo root. Read it before touching anything.
 - **Project config:** `.goblin/goblin.yaml` (class, branch, gates, ratchet, runtime data,
   replay, opt-outs). Edit it in place; the installer never overwrites it.
 - **The referenced standard**, if configured, is named by `practice:` in `.goblin/goblin.yaml`.
   Read it before starting work; this repo carries no copy of it.
 
+**Agent skills are opt-in, per platform.** A default install ships none — this is a neutral
+harness on purpose, so nothing here assumes which coding agent you use. To install the
+procedure skills for your tool:
+
+    gob emit --platform <p>
+
+(`--scope project` writes them inside this repo; `--scope global` writes them for your user.)
+Run `gob emit` with no platform to see the list. If skills were installed here, they live
+under the platform's own directory, and `gob verify` hashes them.
+
 Two things this repo does not do: it does not choose models (a role resolves through the
 mapping file named by `models_file:`), and it does not write outside its own tree.