@sleepy_panda_srl/portulan 0.1.1 → 0.1.3

package/evals/releases/0.1.3.json

@@ -0,0 +1,134 @@
+{
+    "portulan": {
+        "releaseEval": "1"
+    },
+    "version": "0.1.3",
+    "captured": "2026-09-16",
+    "source": {
+        "commit": "fac7b6d36ce3aa53ce93381ef8cce07e503608e4",
+        "clean": true
+    },
+    "host": {
+        "node": "v26.8.1",
+        "platform": "darwin"
+    },
+    "recipes": [
+        {
+            "id": "docs",
+            "exit": 0
+        },
+        {
+            "id": "json",
+            "exit": 0
+        },
+        {
+            "id": "doctor",
+            "exit": 0
+        },
+        {
+            "id": "tests",
+            "exit": 0
+        },
+        {
+            "id": "plugin",
+            "exit": 0
+        },
+        {
+            "id": "compile",
+            "exit": 0
+        },
+        {
+            "id": "workflow-filters",
+            "exit": 0
+        },
+        {
+            "id": "index",
+            "exit": 0
+        },
+        {
+            "id": "control-chars",
+            "exit": 0
+        },
+        {
+            "id": "rule-carriers",
+            "exit": 0
+        },
+        {
+            "id": "pack-version",
+            "exit": 0
+        },
+        {
+            "id": "pack-identity",
+            "exit": 0
+        },
+        {
+            "id": "payload",
+            "exit": 0
+        },
+        {
+            "id": "eval-bundle",
+            "exit": 0
+        },
+        {
+            "id": "goldens",
+            "exit": 0
+        },
+        {
+            "id": "mutants",
+            "exit": 0
+        },
+        {
+            "id": "fuzz-shell",
+            "exit": 0
+        },
+        {
+            "id": "version-carriers",
+            "exit": 0
+        },
+        {
+            "id": "skill-goldens",
+            "exit": 0
+        },
+        {
+            "id": "review-loop",
+            "exit": 0
+        },
+        {
+            "id": "telemetry",
+            "exit": 0
+        },
+        {
+            "id": "drills",
+            "exit": 0
+        },
+        {
+            "id": "ab",
+            "exit": 0
+        },
+        {
+            "id": "ab-grade",
+            "exit": 0
+        },
+        {
+            "id": "ab-run",
+            "exit": 0
+        },
+        {
+            "id": "tools/github:actions-pinned",
+            "exit": 0
+        }
+    ],
+    "excluded": [
+        {
+            "id": "release-eval",
+            "why": "a capture cannot be accurate about the record it is inside — captured before the record is written it is red for the record's absence, and captured after it is stale the moment the register is rendered. Its verdict for this release is the rail's own run on the pull request carrying this file."
+        }
+    ],
+    "abBaseline": {
+        "snapshot": "evals/ab/baseline.json",
+        "register": "evals/ab/baseline.md",
+        "captured": "2026-08-31T09:05:32.699Z",
+        "commit": "a642d551eec6c146c67ef0acfe3f8ba535c5ce6e",
+        "clean": false
+    }
+}

package/evals/releases/0.1.3.md

@@ -0,0 +1,64 @@
+# Eval result — Portulan 0.1.3
+
+> **Generated. Do not edit.** Rendered from [`evals/releases/0.1.3.json`](0.1.3.json) by [`cli/release-eval.mjs`](../../cli/release-eval.mjs) and byte-compared by the `release-eval` verify recipe. This is the eval result milestone 8 requires a release to carry — `docs/plan.md`, Protocol → Versioning.
+
+## What this release was measured at
+
+| | |
+|---|---|
+| Version | `0.1.3` |
+| Captured | 2026-09-16 |
+| Commit | `fac7b6d36ce3aa53ce93381ef8cce07e503608e4` |
+| Tree at capture | clean |
+| Node | `v26.8.1` |
+| Platform | `darwin` |
+
+## The rails, and what each returned
+
+26 of the 27 recipes this workspace yielded at capture. The set is derived from [`cli/recipe-set.mjs`](../../cli/recipe-set.mjs) and never listed by hand.
+
+| Recipe | Verdict |
+|---|---|
+| `docs` | green |
+| `json` | green |
+| `doctor` | green |
+| `tests` | green |
+| `plugin` | green |
+| `compile` | green |
+| `workflow-filters` | green |
+| `index` | green |
+| `control-chars` | green |
+| `rule-carriers` | green |
+| `pack-version` | green |
+| `pack-identity` | green |
+| `payload` | green |
+| `eval-bundle` | green |
+| `goldens` | green |
+| `mutants` | green |
+| `fuzz-shell` | green |
+| `version-carriers` | green |
+| `skill-goldens` | green |
+| `review-loop` | green |
+| `telemetry` | green |
+| `drills` | green |
+| `ab` | green |
+| `ab-grade` | green |
+| `ab-run` | green |
+| `tools/github:actions-pinned` | green |
+
+**`release-eval` is excluded**, and the reason is printed rather than the row silently dropped: a capture cannot be accurate about the record it is inside — captured before the record is written it is red for the record's absence, and captured after it is stale the moment the register is rendered. Its verdict for this release is the rail's own run on the pull request carrying this file.
+
+## The A/B baseline this release ships against
+
+[`evals/ab/baseline.md`](../../evals/ab/baseline.md), rendered from `evals/ab/baseline.json` — captured 2026-08-31T09:05:32.699Z at `a642d551eec6c146c67ef0acfe3f8ba535c5ce6e`, over a tree that was **not clean**.
+
+**Its figures are not repeated here.** They have one carrier and this is not it.
+
+## What this record does not establish
+
+- **A green says this record agrees with its own capture — never that the release is good.** Every line below is what the recipes returned at one commit, and a recipe's own green establishes only what that recipe's documentation says it establishes.
+- **The recipes were not run at the tag.** They ran at `fac7b6d36ce3aa53ce93381ef8cce07e503608e4`, and this record is committed *in* the cut change — so the tagged tree is this commit plus whatever that change still adds after the capture, the record itself at minimum. A record cannot be captured at a commit that does not exist yet, and printing the one it was captured at is the only honest form.
+- **`release-eval` is excluded from the rows above**, because a capture cannot be accurate about the record it is inside. Its verdict for this release is the rail's own run on the pull request that carries this file.
+- **This record measures the Portulan repository's own build**, at the commit named above — never the workspace, project or package this release is installed into. Nothing here has looked at your tree.
+- **The tree was clean at capture**, so the commit named above is what was measured.
+- **The A/B baseline's figures are NOT restated here.** This record names which baseline the release ships against; the figures and everything that may not be concluded from them live in that register alone.

package/evals/releases/README.md

@@ -0,0 +1,32 @@
+# `evals/releases/`
+
+The eval result each release carries, one pair per version — milestone 8's ninth clause. The argument,
+the limits and the two designs a fresh context reversed are in [`../README.md`](../README.md); the
+mechanism is [`../../cli/release-eval.mjs`](../../cli/release-eval.mjs). This file does not restate
+either, because a rule with two carriers is obeyed at the narrower one.
+
+- `<version>.json` — the **capture**: the verdict every recipe the workspace yielded returned, at a named
+  commit, plus the identity of the A/B baseline that release ships against. Written by
+  `node cli/release-eval.mjs --capture`, which runs them. **A hand-edited capture is NOT caught by the
+  byte comparison** — that holds the register to the capture, so `--write` re-renders the edit and the
+  pair agrees perfectly. What guards a capture is the rail's reading of its *contents*: an exclusion
+  list that is anything but the self-exclusion, a recorded non-zero exit, a version not matching the
+  release it is filed under, a record for a version never cut or for one the clause does not govern.
+  This sentence used to claim the opposite, and a sentence claiming a guard that does not exist is what
+  makes the gap it describes look unreachable.
+- `<version>.md` — the **register**, rendered from the capture. Generated; do not edit. `--write`
+  re-renders it and the `release-eval` recipe refuses any difference.
+
+**Which releases have records is not written here.** `ls` this directory, or run
+`node cli/release-eval.mjs --verify`, which prints the governed set and is the carrier — a sentence
+counting the files beside it would be a hand-maintained figure of a subject that grows once per release,
+which is the defect this repository deletes on sight.
+
+**What is fixed, and is the only thing this file states about coverage:** the clause binds *from
+milestone 8* — [`../../docs/plan.md`](../../docs/plan.md), Protocol → Versioning — so `v0.1.0`, `v0.1.1`
+and `v0.1.2` carry none and are never asked to. That is history and cannot change.
+
+_(This paragraph read **"This directory is empty of records"** as a standing claim. It would have gone
+false in the very commit that wrote the first record — and, since this directory ships inside the npm
+payload, it would then have been **frozen false beside the record it denied**, in a tarball only another
+release could correct. Caught by a second opinion before the first cut rather than by a reader of it.)_

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sleepy_panda_srl/portulan",
-  "version": "0.1.1",
+  "version": "0.1.3",
   "description": "Portulan — an agentic-engineering framework whose product is its files. The CLI wraps the file-based mechanics for hosts beyond Claude Code.",
   "license": "Apache-2.0",
   "type": "module",
@@ -15,13 +15,18 @@
     "core/",
     "spec/",
     "packs/",
+    "evals/releases/",
     "README.md",
     "LICENSE",
     "NOTICE",
     "!cli/*.test.mjs",
     "!cli/fixtures",
     "!cli/eval-bundle.mjs",
-    "!cli/eval-license.template.md"
+    "!cli/eval-license.template.md",
+    "!cli/ab.mjs",
+    "!cli/ab-run.mjs",
+    "!cli/ab-grade.mjs",
+    "!cli/payload.mjs"
   ],
   "repository": {
     "type": "git",

package/packs/README.md

@@ -15,18 +15,14 @@ array, in the canonical `category/name` form.
 
 ## Why there is a `.claude-plugin/plugin.json` in *this* directory
 
-Because **this directory is itself a plugin payload**, and it had been shipping as one while declaring
-nothing. The private feed's `portulan-checkpoints` entry is a `git-subdir` source rooted here, so what a
-host installs is the contents of `packs/` — and until 2026-08-09 that payload carried no plugin manifest
-at all. The host had nothing to read, registered nothing, and said so only as a count nobody was
-watching: **`claude plugin details portulan-checkpoints@portulan-internal` → `Skills (0)`**, for the
-whole of milestone 6 and after.
-
-That is [#134](https://github.com/sleepy-panda-srl/portulan/issues/134)'s `Skills (0)` bullet, and the
-issue's own diagnosis of it was wrong: it attributed the zero to a declared path pointing one level too
-high, which is a real trap and a different one. Measured on Claude Code 2.1.226 by installing this
-directory both ways — **`Skills (0)` without the manifest, `Skills (3)` with it**, the same three
-`SKILL.md` files either way.
+Because **this directory is itself a plugin payload**. The private feed's
+`portulan-checkpoints` entry is a `git-subdir` source rooted here, so what a host installs is the
+contents of `packs/` — and a payload with no plugin manifest registers nothing, silently, reporting
+it only as a count nobody is watching: `claude plugin details` → `Skills (0)`.
+
+**Registration is a property of the plugin manifest and of nothing else.** Measured on Claude Code
+2.1.226 by installing this directory both ways — **`Skills (0)` without the manifest, `Skills (3)`
+with it**, the same three `SKILL.md` files either way.
 
 The manifest declares `./rituals/checkpoints/skills/` — the directory that actually holds them — because
 **a host expands a declared skills path exactly one level and no further**. Declaring `./rituals/`
@@ -50,12 +46,6 @@ exists and the feed's pin moves to it. Until then the green is demonstrated on t
 for the feed — a distinction this repository would rather write down than round off.
 
 > **Two packs exist.** [`rituals/checkpoints`](rituals/checkpoints/README.md), the supervised-build
-> ritual, as of milestone 6; and [`tools/github`](tools/github/README.md), one verify recipe, authored
-> at milestone 7 session 5 because a demonstration needed a real subject. `stacks/` is still empty and
-> says why. _(This said "One pack exists … `stacks/` and `tools/` are still empty" from milestone 6
-> until 2026-08-13, and the second half went false the day `tools/github` landed beside it.)_
->
-> This file read "Nothing here yet" for four milestones, and the pack it predicted — a cross-artifact
-> consistency check — is not the one that arrived. Recorded rather than quietly replaced: the first
-> pack was chosen by which ritual this project could show working evidence for, not by which was named
-> first.
+> ritual; and [`tools/github`](tools/github/README.md), one verify recipe. `stacks/` is still empty and
+> says why.
+

package/packs/rituals/checkpoints/README.md

@@ -38,7 +38,7 @@ Four verdicts, and which are available depends on the checkpoint.
 | Verdict | Means | Available at |
 |---|---|---|
 | **APPROVE** | Proceed as it stands. | session-open · pre-commit |
-| **APPROVE-WITH-ADJUSTMENTS** | Proceed once the numbered adjustments are folded in. Not a soft failure — it is what a working checkpoint usually returns. | session-open · pre-commit |
+| **APPROVE-WITH-ADJUSTMENTS** | Proceed once the numbered adjustments are folded in. Not a soft failure — it is what a working checkpoint usually returns. **At pre-commit the fold itself is then graded** — see that skill. | session-open · pre-commit |
 | **REQUEST-CHANGES** | Does not meet the standard. Name what, and what would meet it. Needs a second pass at the same checkpoint. | all three |
 | **CLOSE** | Every clause of the criterion is demonstrated; the milestone may be marked done. | milestone-close only |
 
@@ -49,6 +49,13 @@ concerns is not a verdict.
 proceed on a promise to fold something in, and a close is the one decision with nothing downstream of
 it to catch what was folded in wrongly.
 
+**That argument reaches one moment earlier, which is why pre-commit's A-W-A grades its own fold**
+(proposal `0035`, 2026-08-29). Session-open's fold *does* have something downstream — the plan it folds
+into becomes a diff, and pre-commit grades that. **Pre-commit's fold has only the commit.** So the
+verdict that lets work proceed on a promise is, at that moment, a promise nothing checks; measured on a
+change where two of three later review findings were created by the fold and were absent from the graded
+diff.
+
 ## The fidelity note
 
 What a close leaves in the record once the session that wrote it is gone. Four parts, in one clause:

package/packs/rituals/checkpoints/pack.json

@@ -1,7 +1,7 @@
 {
   "portulan": {
     "pack": "1.0",
-    "version": "0.2.1"
+    "version": "0.3.0"
   },
 
   "name": "checkpoints",

package/packs/rituals/checkpoints/skills/pre-commit/SKILL.md

@@ -65,8 +65,38 @@ whether a status column changed.
 ## The verdicts this checkpoint may return
 
 - **APPROVE** — commit as it stands.
-- **APPROVE-WITH-ADJUSTMENTS** — commit once the numbered adjustments are folded in.
-- **REQUEST-CHANGES** — the diff does not meet the criterion; it needs work and a second pre-commit pass.
+- **APPROVE-WITH-ADJUSTMENTS** — fold the numbered adjustments, then **grade the fold**: a pass over
+  **the fold delta alone**, in a context that did not perform the fold, before the commit.
+- **REQUEST-CHANGES** — the diff does not meet the criterion; it needs work and a second pre-commit pass
+  **over the whole diff**.
+
+**Grade a fully staged diff.** The whole procedure below is index-shaped, so anything left unstaged was
+not graded and will not appear in the fold delta either — it would pass through both nets. Stage first,
+then grade; this is what practice here already did, and it is stated because the mechanism now depends
+on it rather than merely benefiting from it.
+
+**A checkpoint records the tree it graded** — the index it read, as a tree object (`git write-tree`). The
+fold delta is then **`git diff --cached <graded-tree>`**: the recorded tree against the index, which is
+what is about to be committed. Derived, not reconstructed from memory by the person who folded.
+
+_Why the fold is graded at all, and why the A-W-A pass is scoped to the delta._ **The tree that ships is
+not the tree that was graded**, and the difference is where a remediation can inject what the checkpoint
+just caught elsewhere. Measured: on one change, folding an adjustment split a table row and left a
+summary count stale three sections above, and folding another **re-measured a question the checkpoint had
+answered correctly** — with a line-based tool against a normalising scanner — and wrote the wrong answer
+over the right one. Neither defect was in the graded diff. A full re-grade after every A-W-A would double
+the cost of the cheapest verdict, which is the ceremony a definition of done should refuse; **the delta is
+the only region a fold-injected defect can be in.**
+
+_The delta is **whatever was staged after the grade** — it *should* be the adjustments and nothing else,
+and the mechanism does not guarantee that. **Where it is wider, that is not noise; it is the finding.**
+Post-grade edits nobody proposed are exactly what escapes a checkpoint today, so a pass that sees them is
+worth more than one over a delta that had been trimmed to what the verdict asked for._
+
+_What this does not buy, said plainly: whether a fresh context actually read the delta is not checkable —
+a session can claim a pass it did not run. What changes is that the pass now has a **defined subject**,
+derived from the tree rather than recalled by the one who folded._ Provenance: proposal `0035`,
+accepted 2026-08-29.
 
 ## Why it earns its tokens
 

package/packs/tools/README.md

@@ -3,10 +3,7 @@
 Tool packs — integrations for the tools and MCP servers an agent drives (issue trackers, cloud
 CLIs, design tools, databases), with the how-to and the gate classification for each.
 
-> **One tool pack exists** — [`github/`](github/README.md), since milestone 7 session 5. _(This read
-> "No tool pack exists yet" until 2026-08-13, beside the directory that refutes it.)_ What changed at
-> milestone 6 was the machinery rather
-> than this directory. Milestone 4 built the thing that would read one — a gate policy in a
+> **One tool pack exists** — [`github/`](github/README.md). The machinery that reads one is a gate policy in a
 > host-neutral vocabulary, dispatched on by [`../../cli/compile.mjs`](../../cli/compile.mjs) — and the
 > cascade's missing middle (`core < pack < workspace`) is now bridged: a pack's `contributes.gates`
 > fragments are resolved and merged into the policy, **tighten-only**, by the same compiler.

package/spec/README.md

@@ -6,8 +6,7 @@ what makes both machine-readable instead of a folder convention.
 
 - [`workspace.schema.json`](workspace.schema.json) — the **Workspace Definition**: the manifest at a
   workspace root. Normative.
-- [`pack.schema.json`](pack.schema.json) — the **Pack Definition**: the manifest at a pack root, added at
-  milestone 6, declaring what the pack contributes to the cascade. Normative, and on **its own version
+- [`pack.schema.json`](pack.schema.json) — the **Pack Definition**: the manifest at a pack root, declaring what the pack contributes to the cascade. Normative, and on **its own version
   train** — see [Versioning](#versioning-and-migrations).
 - [`slots.md`](slots.md) — every workspace slot: what it holds, why it exists, where it was derived from,
   and what `doctor` checks about it. The rationale lives there; this file is the orientation.
@@ -64,7 +63,7 @@ read.
 The fourth, **`pointer`**, added at 2.7, governs nothing. It names the workspace that governs this
 repository and carries no slots of its own — a repository whose policy layer resides elsewhere says so in
 one thin manifest instead of keeping a second copy nothing holds in agreement. That is the maintainer's
-residence ruling of 2026-07-30 in the schema
+residence ruling in the schema
 ([proposal 0017](../.portulan/proposals/0017-one-repository-one-governing-workspace.md)):
 
 > A repository is governed by exactly one workspace. It carries its own full workspace, or a pointer to
@@ -76,11 +75,11 @@ makes that a property rather than a promise is that every feature keys to a work
 to a residence. Nothing in `doctor`, `compile` or `index` asks where the manifest lives. The proposal
 carries the one place where that was not yet true, and it was a discovery gap rather than a feature gap:
 the boot skill searched the project directory only, so a repository governed from a feed booted to a
-pointer's honest report rather than to a resolved workspace. **Closed at milestone 7** by
+pointer's honest report rather than to a resolved workspace. **Closed** by
 [`../cli/discover.mjs`](../cli/discover.mjs), which reads the host's installed-plugin record and
 dereferences a pointer's `governed_by` — from disk, never over the network. The other half of the same amendment — the **pack** root
 ([#123](https://github.com/sleepy-panda-srl/portulan/issues/123)) — landed beside it: `--pack-root
-auto` resolves one from that same record. It ran **only when asked** until 2026-08-13, which was narrower
+auto` resolves one from that same record. It ran **only when asked**, which was narrower
 than the row's *"optional where discovery finds a root"* and was recorded as a narrowing rather than read
 as compliance. **The narrowing is now lifted and the row's word is met**: discovery runs on the unasked
 path, and `auto` selects the strict degrade rather than unlocking anything. The narrowing's stated reason
@@ -159,10 +158,8 @@ real cost, stated here rather than discovered. The subset earns its narrowness b
 completely and honestly; the price is this list, and the list is the thing to watch if it keeps growing.
 **Four MINORs at +2 each** was the growth rate to hold the next bump against, and **2.3's, 2.5's and
 2.6's** pairs are the *same* pair three times over — a series needs a store and its index must sit outside
-it — which was an argument for generalising it rather than adding it again. _(2.4's pair is `librarian`'s
-and is a different one: a pass needs a store to age, and a proposal threshold needs a proposal series.
-An earlier draft of this sentence read "2.4's, 2.5's and 2.6's", which would have made the repeating pair
-four bumps old instead of three and misattributed `memory`'s contribution to `librarian`.)_
+it — which was an argument for generalising it rather than adding it again. _(2.4's pair is `librarian`'s and is a
+different one: a pass needs a store to age, and a proposal threshold needs a proposal series.)_
 
 **2.7 is the first MINOR since 2.2 that adds nothing to this list**, and that is the reason its pointer
 requirement went into the schema's `oneOf` instead. The generalisation the paragraph above kept asking for
@@ -198,7 +195,7 @@ number governing both would make a bump in either mean a change in the other:
 | Schema | Manifest key | Current | What it governs |
 |---|---|---|---|
 | [`workspace.schema.json`](workspace.schema.json) | `portulan.spec` | **2.8** | the Workspace Definition — the manifest at a workspace root |
-| [`pack.schema.json`](pack.schema.json) | `portulan.pack` | **1.0** | the Pack Definition — the manifest at a pack root, added at milestone 6 |
+| [`pack.schema.json`](pack.schema.json) | `portulan.pack` | **1.0** | the Pack Definition — the manifest at a pack root. |
 
 The rules below apply to each train independently. `portulan.spec` is `MAJOR.MINOR`, and the current
 Workspace Definition version is **2.8**. It did **not** move when the Pack Definition arrived, because
@@ -300,7 +297,7 @@ better, and not a fix.)_
 
 This migration is a paragraph and a version bump, and a directory holding a document that says "add one
 line" would be scaffolding pretending to be machinery. This paragraph therefore ended **"There is still
-no `migrations/` directory: one arrives when a migration needs code"** — and at milestone 7 session 9
+no `migrations/` directory: one arrives when a migration needs code"** — and
 one did, on that stated condition rather than because a tool wanted a home.
 
 **[`migrations/`](migrations/) is now the contract**, and its README is where a step is defined. What
@@ -328,24 +325,24 @@ workspace with no constitution slot and a green report.
 |---|---|---|
 | Every `.json` file parses | [`../.portulan/verify/json.sh`](../.portulan/verify/json.sh) | **Built.** Well-formedness only — it does not read the schema. |
 | Manifest conforms to the schema | [`../cli/doctor.mjs`](../cli/doctor.mjs) | **Built.** Names the violated constraint and its location. |
-| A declared pack **resolves** | `doctor` | **Built** (milestone 6). Roots are derived from `tree`, and named roots may be given with `--pack-root`, which **replace** the derived one rather than preceding it, so a from-a-feed demonstration cannot be satisfied by a copy in the local tree at all. A workspace with no `tree` and no named root has its packs reported *unverifiable* rather than failed. Resolution **from a feed is demonstrated** as of milestone 6, session 1: the checkpoint ritual pack installed from the private `portulan-internal` marketplace and resolved from the install root, which is the same code path the derived one takes. **Discovery landed at milestone 7** ([#123](https://github.com/sleepy-panda-srl/portulan/issues/123)): `--pack-root auto` reads the host's installed-plugin record — in **both** shapes a plugin lands in, packs under `packs/` for a repository-shaped one and categories at the install root for a flat one, which is what this project's own feed ships. **Amended 2026-08-12:** asked-for discovery is **unioned** with the tree-derived root, discovered first, so a workspace composing a cache-installed pack *and* one of its own resolves both — which no invocation could do before without naming a cache path by hand. The **named**-root property above is untouched: a named root still replaces the derived one, so a from-a-feed demonstration given one cannot be satisfied by a local copy. What the union trades is the weaker guarantee that `auto` *alone* implied provenance; it no longer does, and each pack's resolution states which root answered instead. Asking for a named root **and** `auto` together is refused (exit 2) rather than silently resolved to one of them. **Amended 2026-08-13 — the disposal:** discovery runs on the **unasked** path too, because the row's clause is that `--pack-root` is *optional where discovery finds a root* and it was not. `auto` now selects the strict degrade (asked-and-could-not-look is exit 2) rather than unlocking discovery. Two things bound it, and neither makes a bare run host-independent — `doctor` is a per-host capability report and a bare verdict does move with the machine. First, every **required** check **names** its root, which replaces every other source, so it cannot consult the host at all. Second, `doctor`'s note-vs-fail keying is on a root's **origin**, so discovery can turn a note into a **resolution** and never a **miss** into a failure — a miss under a root the workspace or the caller claimed stays a FAIL whatever is installed. It softens nothing: a discovered copy that resolves and is *invalid* still fails, with its origin named. |
-| A pack manifest conforms to the Pack Definition | `doctor` | **Built** (milestone 6). Same validator, same subset, a different schema and version train. |
-| A pack's skills and personas are opened and validated | `doctor` | **Built** (milestone 7 session 2), on the maintainer's ruling of 2026-08-03 that row 7's validation reads broad. A skill's frontmatter (`name` kebab-case, `description` non-empty — the two a host reads before loading a body); a persona against the five-part contract, **including the memory scope** `core/operating/memory.md` promised would be validated at this milestone; and the tier no role may claim. Containment is checked **after resolution**, because opening these paths is what made an escaping value stop being inert. Three honest limits, each measured rather than assumed. The skills walk stops **three levels down**, matching `cli/plugin-lint.mjs`'s bound so two walkers over the same key cannot disagree, and it **reports the directories it did not descend into** rather than counting a root it never opened as empty. The Prohibited check is a prose heuristic defeated by any negation **in the same block** — a bullet list counts as one block — and the structural fix is a declared reach *field*, a contract change that is not built. And the five-part check is **presence**, not content: a persona whose sections are all empty passes, so a declared memory scope is read and not honoured. |
-| Pack gate fragments merge **tighten-only** | [`../cli/compile.mjs`](../cli/compile.mjs) | **Built** (milestone 6). Two layers and two axes: `auto` is absent from the Pack Definition's tier enum, so a demotion to unattended is unexpressible; the comparison against the composed base is the compiler's, and both a weakened **tier** and a changed **action** throw rather than being dropped. The action half is the one a tier-only check misses — raising the tier while swapping the matcher removes the gate and still reads as a tightening. |
-| A pack declaring a version ahead of `doctor` | `doctor` | **Built** (milestone 6). Refused rather than graded, symmetric with the workspace train, and on the Pack Definition's own `$id`. |
+| A declared pack **resolves** | `doctor` | **Built**. Roots are derived from `tree`, and named roots may be given with `--pack-root`, which **replace** the derived one rather than preceding it, so a from-a-feed demonstration cannot be satisfied by a copy in the local tree at all. A workspace with no `tree` and no named root has its packs reported *unverifiable* rather than failed. Resolution **from a feed is demonstrated**: the checkpoint ritual pack installed from the private `portulan-internal` marketplace and resolved from the install root, which is the same code path the derived one takes. **Discovery is built** ([#123](https://github.com/sleepy-panda-srl/portulan/issues/123)): `--pack-root auto` reads the host's installed-plugin record — in **both** shapes a plugin lands in, packs under `packs/` for a repository-shaped one and categories at the install root for a flat one, which is what this project's own feed ships. Asked-for discovery is **unioned** with the tree-derived root, discovered first, so a workspace composing a cache-installed pack *and* one of its own resolves both. The **named**-root property above is untouched: a named root still replaces the derived one, so a from-a-feed demonstration given one cannot be satisfied by a local copy. What the union trades is the weaker guarantee that `auto` *alone* implied provenance; it no longer does, and each pack's resolution states which root answered instead. Asking for a named root **and** `auto` together is refused (exit 2) rather than silently resolved to one of them. Discovery runs on the **unasked** path too, because `--pack-root` is *optional where discovery finds a root*. `auto` now selects the strict degrade (asked-and-could-not-look is exit 2) rather than unlocking discovery. Two things bound it, and neither makes a bare run host-independent — `doctor` is a per-host capability report and a bare verdict does move with the machine. First, every **required** check **names** its root, which replaces every other source, so it cannot consult the host at all. Second, `doctor`'s note-vs-fail keying is on a root's **origin**, so discovery can turn a note into a **resolution** and never a **miss** into a failure — a miss under a root the workspace or the caller claimed stays a FAIL whatever is installed. It softens nothing: a discovered copy that resolves and is *invalid* still fails, with its origin named. |
+| A pack manifest conforms to the Pack Definition | `doctor` | **Built**. Same validator, same subset, a different schema and version train. |
+| A pack's skills and personas are opened and validated | `doctor` | **Built**, on the maintainer's ruling that row 7's validation reads broad. A skill's frontmatter (`name` kebab-case, `description` non-empty — the two a host reads before loading a body); a persona against the five-part contract, **including the memory scope** `core/operating/memory.md` promised would be validated at this milestone; and the tier no role may claim. Containment is checked **after resolution**, because opening these paths is what made an escaping value stop being inert. Three honest limits, each measured rather than assumed. The skills walk stops **three levels down**, matching `cli/plugin-lint.mjs`'s bound so two walkers over the same key cannot disagree, and it **reports the directories it did not descend into** rather than counting a root it never opened as empty. The Prohibited check is a prose heuristic defeated by any negation **in the same block** — a bullet list counts as one block — and the structural fix is a declared reach *field*, a contract change that is not built. And the five-part check is **presence**, not content: a persona whose sections are all empty passes, so a declared memory scope is read and not honoured. |
+| Pack gate fragments merge **tighten-only** | [`../cli/compile.mjs`](../cli/compile.mjs) | **Built**. Two layers and two axes: `auto` is absent from the Pack Definition's tier enum, so a demotion to unattended is unexpressible; the comparison against the composed base is the compiler's, and both a weakened **tier** and a changed **action** throw rather than being dropped. The action half is the one a tier-only check misses — raising the tier while swapping the matcher removes the gate and still reads as a tightening. |
+| A pack declaring a version ahead of `doctor` | `doctor` | **Built**. Refused rather than graded, symmetric with the workspace train, and on the Pack Definition's own `$id`. |
 | Path slots resolve to real files | `doctor` | **Built.** File-versus-directory too; a slot resolving outside the workspace is reported, never failed. |
 | Workspace claims match the tree | `doctor` | **Built, where a tree is declared** — repo-card build/test/run lines and layout, and the gate map's required-check claim. A workspace with no `tree` has those claims *reported unverifiable*. |
 | A rule's provenance is well-formed | `doctor` | **Built.** On `type: rule` records in the `memory` slot; the form only, never the truth. |
 | Sealed proportion reported | `doctor` | **Built.** Over rules, which is the denominator the mandate uses. |
-| The recipes a workspace declares actually run | Stop-gate runner | **Built** (milestone 4), for the **default** recipe only, and outside `doctor` — which still reads recipes and executes none. A non-default recipe declaring a tool it does not have still passes. |
-| The gate policy compiles to host enforcement | `compile` | **Built** (milestone 4). Two backends — the Claude Code host and the GitHub repository ruleset that is the platform floor. Every rule ends as compiled or refused-with-a-reason, **per backend**, and each emitted artifact is held to the policy by a verify recipe. That the *host* honours it is not checkable here — CI installs nothing. |
-| What each backend cannot enforce | `doctor` · `compile --matrix` | **Built** (milestone 4). Per-backend coverage, the gates no backend compiles, and the floor's declared status checks against the tree's workflow jobs — the last of those a failure, the rest reports. Exported-versus-live drift is **not** checked: `doctor` does not fetch settings, and no recipe here makes a network call. |
+| The recipes a workspace declares actually run | Stop-gate runner | **Built**, for the **default** recipe only, and outside `doctor` — which still reads recipes and executes none. A non-default recipe declaring a tool it does not have still passes. |
+| The gate policy compiles to host enforcement | `compile` | **Built**. Two backends — the Claude Code host and the GitHub repository ruleset that is the platform floor. Every rule ends as compiled or refused-with-a-reason, **per backend**, and each emitted artifact is held to the policy by a verify recipe. That the *host* honours it is not checkable here — CI installs nothing. |
+| What each backend cannot enforce | `doctor` · `compile --matrix` | **Built**. Per-backend coverage, the gates no backend compiles, and the floor's declared status checks against the tree's workflow jobs — the last of those a failure, the rest reports. Exported-versus-live drift is **not** checked: `doctor` does not fetch settings, and no recipe here makes a network call. |
 | One repository, one governing workspace | `doctor` | **Built** (2.7). Two refusals need only the manifest in hand: a `pointer` carrying governing slots, and a governing kind carrying a `governed_by`. Both print the ruling's own sentence, which is why they are `doctor`'s and not the schema's — a schema failure returns at *the manifest must conform first* and the sentence would never reach a reader. |
-| A repository named by one workspace and governed by another | `doctor --repo-root` | **Built** (2.7), **where visible**. Roots are named, never discovered — **and since milestone 7 this is the narrower limit of the two**: `--pack-root` gained `auto` and `--repo-root` did not, because what it would have to find is a *repository checkout*, which no host plugin record lists. The amendment that ordered discovery names the plugin cache in its own title, so this is outside its scope rather than owed by it. Without a root the check **reports that it did not run** rather than passing quietly. Visibility is one-way: the refusal runs from the naming workspace outward, so a repository carrying a full workspace cannot see a portfolio that claims it. A workspace that names its **own** repository finds itself and is not two managers; that identity is compared on the real path. |
-| A pointer resolves to the workspace it names | `discover` · `doctor` | **Built** (milestone 7). `governed_by` is dereferenced against the host's installed-plugin record — `<config>/plugins/installed_plugins.json`, `CLAUDE_CONFIG_DIR` overriding the config directory — and the match is on the **governing manifest's `name`**, never on a plugin's, with `governed_by.feed` constraining the marketplace where it is declared. Four answers, because three of them are not *no*: `resolved` (exactly one), `not-installed`, `ambiguous` (two or more — **refused and both named**, never ranked), `could-not-look` (a record that would not parse, which must never spend as absence). **Nothing is fetched**: the record is read from disk and no path here touches the network, so *discovery of anything not installed* stays out of scope as row 7 states. `doctor` **reports** the answer on a pointer and never grades it — a pointer whose governor is uninstalled is a correct pointer, and no discovery outcome moves this tool's exit code. The candidate locations inside a plugin payload are a **named pair** — `<installPath>/workspace.json` and `<installPath>/.portulan/workspace.json` — rather than a walk, which is what keeps this bundle's demo and drifted fixtures out of reach by construction — neither sits at one; the bundle's own `.portulan/` does, which is the correct answer to a pointer naming `portulan` rather than a hole. `init` **asks** the residence question and writes a pointer as of milestone 7 session 1; `vendor` **performs the switch in both directions** as of session 3, and both write pointers rather than resolving them. |
+| A repository named by one workspace and governed by another | `doctor --repo-root` | **Built** (2.7), **where visible**. Roots are named, never discovered — **and this is the narrower limit of the two**: `--pack-root` gained `auto` and `--repo-root` did not, because what it would have to find is a *repository checkout*, which no host plugin record lists. The amendment that ordered discovery names the plugin cache in its own title, so this is outside its scope rather than owed by it. Without a root the check **reports that it did not run** rather than passing quietly. Visibility is one-way: the refusal runs from the naming workspace outward, so a repository carrying a full workspace cannot see a portfolio that claims it. A workspace that names its **own** repository finds itself and is not two managers; that identity is compared on the real path. |
+| A pointer resolves to the workspace it names | `discover` · `doctor` | **Built**. `governed_by` is dereferenced against the host's installed-plugin record — `<config>/plugins/installed_plugins.json`, `CLAUDE_CONFIG_DIR` overriding the config directory — and the match is on the **governing manifest's `name`**, never on a plugin's, with `governed_by.feed` constraining the marketplace where it is declared. Four answers, because three of them are not *no*: `resolved` (exactly one), `not-installed`, `ambiguous` (two or more — **refused and both named**, never ranked), `could-not-look` (a record that would not parse, which must never spend as absence). **Nothing is fetched**: the record is read from disk and no path here touches the network, so *discovery of anything not installed* stays out of scope as row 7 states. `doctor` **reports** the answer on a pointer and never grades it — a pointer whose governor is uninstalled is a correct pointer, and no discovery outcome moves this tool's exit code. The candidate locations inside a plugin payload are a **named pair** — `<installPath>/workspace.json` and `<installPath>/.portulan/workspace.json` — rather than a walk, which is what keeps this bundle's demo and drifted fixtures out of reach by construction — neither sits at one; the bundle's own `.portulan/` does, which is the correct answer to a pointer naming `portulan` rather than a hole. `init` **asks** the residence question and writes a pointer; `vendor` **performs the switch in both directions** as of session 3, and both write pointers rather than resolving them. |
 | A feed-side repo card's claims against a repo-side tree | — | **Not built** — the cross-repo claims-lint gap, priced in [proposal 0017](../.portulan/proposals/0017-one-repository-one-governing-workspace.md). A portfolio workspace declares no `tree`, so its cards' build/test/run and layout claims are *reported unverifiable*; repo-side the tree is present and the cards are not. No single CI run sees both halves. In-session validation does work, and `--repo-root` narrows the governance question specifically — neither closes this. **Tracked as [#138](https://github.com/sleepy-panda-srl/portulan/issues/138)**, filed 2026-07-30 at the maintainer's instruction. This row states no *arrives-at*, unlike its neighbour below which says outright that it is not planned as a gate; which milestone owns it — milestone 9 has been proposed, since its criterion is the first that needs both halves green together — is **the maintainer's to decide**, and this row will name it once [`../docs/plan.md`](../docs/plan.md) does. Until then the honest state is *not built, tracked, undispositioned* rather than a milestone claimed here first. |
 | A rule's link resolves | — | Not built, and not planned as a gate: dereferencing needs the network, and a gate that fails for reasons unrelated to the change under test is worse than no gate. |
-| Agent-legibility scored | `doctor` | **Built** (milestone 7 session 7). **Seven** dimensions, each optional in this definition so it can genuinely be absent and none of them a restatement of a check that already fails — *executable verification* was an eighth for one checkpoint until that rule was applied to it, since form 0 of the `oneOf` above requires `verify` of every workspace the score can reach: recipes declaring `requires` · a machine-readable gate policy · a `dod` slot · a memory store with a generated index · a handoff series with a generated index · affordances reachable for every product (its own or the workspace-level default) · each of those documents naming what an agent must **not** assume. The `affordances` slot is the **named input, not the only one** — a score confined to it could not tell two workspaces apart. **It moves no exit code**: a measurement is not a verdict, and one that could fail a workspace would make conformance a function of prose volume. The last dimension is a **form** check over a named heading table, so a limits section with an empty body passes. |
+| Agent-legibility scored | `doctor` | **Built**. **Seven** dimensions, each optional in this definition so it can genuinely be absent and none of them a restatement of a check that already fails — *executable verification* was an eighth for one checkpoint until that rule was applied to it, since form 0 of the `oneOf` above requires `verify` of every workspace the score can reach: recipes declaring `requires` · a machine-readable gate policy · a `dod` slot · a memory store with a generated index · a handoff series with a generated index · affordances reachable for every product (its own or the workspace-level default) · each of those documents naming what an agent must **not** assume. The `affordances` slot is the **named input, not the only one** — a score confined to it could not tell two workspaces apart. **It moves no exit code**: a measurement is not a verdict, and one that could fail a workspace would make conformance a function of prose volume. The last dimension is a **form** check over a named heading table, so a limits section with an empty body passes. |
 
 As of milestone 2 the schema is a rail rather than only a specification — but read the right-hand column
 rather than the middle one. `doctor` checks that a workspace's claims are **well-formed and resolvable**;

package/spec/migrations/README.md

@@ -1,9 +1,8 @@
 # `spec/migrations/` — what a migration is
 
 > Part of the **Workspace Definition**. [`../README.md`](../README.md)'s *Versioning and migrations*
-> section is the contract this directory implements; it said *"There is still no `migrations/`
-> directory … **One arrives when a migration needs code**"* until milestone 7 session 9, and this
-> directory arrives on that stated condition rather than because a tool wanted a home. The runner is
+> section is the contract this directory implements, and this directory exists on that section's own
+> stated condition: a migration needed code. The runner is
 > [`../../cli/upgrade.mjs`](../../cli/upgrade.mjs).
 
 ## A step, and the two kinds

package/spec/slots.md

@@ -345,9 +345,7 @@ has a product-layer slot, which is what the criterion requires; *instances* may
 **What `doctor` checks:** each `product` path resolves; each `affordances` path **that is present**
 resolves; each `repos` entry names a card in the `repos` slot. Per-product `affordances` is optional
 because a product may inherit the workspace-level default — so the check is conditional, and `doctor`
-*reports* a product that has neither its own nor an inherited one rather than failing it. (An earlier
-draft of this line said `doctor` checks `affordances` unconditionally, which would have made the spec
-demand something the schema declares optional; caught in review of the change that introduced it.) The
+*reports* a product that has neither its own nor an inherited one rather than failing it. The
 claim it cannot check is whether the mission written there is still true.
 
 ## `affordances` — what the product offers an agent
@@ -465,12 +463,9 @@ workspace that cannot say which packs it composes leaves an agent to infer the m
 resolution order. The portfolio workspace at milestone 6 ships as a private-feed plugin composing a pack
 delivered by that feed — a manifest that cannot express that forces a MAJOR bump one milestone after v1.
 
-_(This sentence said **premium** packs until milestone 6, session 1, and no shipped pack is premium: the
-one the portfolio workspace composes is the universal checkpoint ritual, delivered by the private feed and
-authored in the public engine. The prediction was reasonable and turned out not to be what milestone 6
-built, so it is corrected to what the tree shows rather than left as a promise about a pack nobody wrote.
-Whether a premium pack should exist at all is a commercial question for the maintainer, not a gap this
-file may quietly keep open.)_
+_(No shipped pack is premium: the one the portfolio workspace composes is the universal checkpoint
+ritual, delivered by the private feed and authored in the public engine. Whether a premium pack should
+exist at all is a commercial question for the maintainer, not a gap this file may quietly keep open.)_
 
 An array of names in cascade order, empty by default. Each name is the canonical `category/name` form
 the Pack Definition owns ([`pack.schema.json`](pack.schema.json)) — but the items stay **free strings**
@@ -776,8 +771,32 @@ Each of these was a candidate; none is an oversight.
 - **A per-host capability matrix.** The vision's `doctor` includes a per-host capability report, but that
   is generated from the host and the compiled gates, not declared by the team. It belongs with the
   enforcement backends in milestone 4.
-- **`evals`.** Milestone 8 owns the eval harness; a slot pointing at golden tasks before any exist would
-  be the emptiest kind of scaffolding.
+- **`evals`.** Milestone 8 owns the eval harness. **The original reason for deferring is spent, and the
+  deferral is re-argued rather than left standing on it.** It read *"a slot pointing at golden tasks
+  before any exist would be the emptiest kind of scaffolding"* — and golden tasks exist: the gate corpus
+  landed at clause (a) and the core-skill corpus at the row's original first subject. The premise
+  expired the day it stopped being true and nothing noticed, which is the shape this file elsewhere
+  calls a claim outliving its measurement.
+
+  **What the deferral now rests on.** A slot is the Workspace Definition's promise that every conforming
+  workspace can be asked one question and answer it. `evals/` today holds **two corpora with two
+  different oracles** — gates answered by the compiler's own `matchesRule`, skills answered by
+  mandate-to-artifact bindings — plus a metering register, and a slot naming that directory would
+  promise adopters a shape this repository has not settled for itself. **Revisit when milestone 8
+  closes**, by which point the row's nine clauses will have decided what an eval artifact is here.
+  Filling it is a schema change, a spec version bump and a migration, so it is not a thing to do in
+  passing.
+
+  **Milestone 8 closed 2026-09-09, so this deferral is now DUE and is not discharged here.** The
+  close names it rather than filling it, which is what the sentence above asks for: the drafting is
+  commissioned by proposal
+  [`../.portulan/proposals/0034-one-spec-bump-carries-both-evals-and-telemetry.md`](../.portulan/proposals/0034-one-spec-bump-carries-both-evals-and-telemetry.md)
+  — accepted 2026-08-28 — which carries `evals` **and** `telemetry` in **one** MINOR and settles none of
+  the shape: the key names, either slot's structure, and whether a migration is owed are the drafted
+  work. Doing that drafting inside the close would be the *"splitting on speculation"* this entry warns
+  against, in the change that closed the row it was waiting for. **What the close settled is the
+  precondition, not the slot:** `evals/` now holds two corpora, a metering register, an A/B capture and
+  a per-release record layer, which is the shape a slot would have to name.
 
 ## What v2.0 is not