@lsctech/polaris 0.3.21 → 0.3.23

package/dist/workspace/workspace/.polaris/skills/docs-ingest/steps/02-classify-batch.md

@@ -1,87 +0,0 @@
----
-name: docs-ingest-step-02-classify-batch
-description: Read each file in the batch, inspect front-matter and content signals, and assign exactly one classification from the docs-authority-model.
----
-
-# Step 02 — Classify batch
-
-## Purpose
-
-Assign each file to exactly one classification. Classification determines target directory, authority level, and whether user approval is required before placement.
-
-## Classification table
-
-| Class | Target path | Authority | Approval required |
-|---|---|---|---|
-| `runtime-summary` | `smartdocs/runtime/summaries/` | low | no |
-| `run-report` | `smartdocs/runtime/run-reports/` | low | no |
-| `spec-raw` | `smartdocs/raw/` | none | no |
-| `spec-active` | `smartdocs/specs/active/` | medium | yes |
-| `audit-finding` | `smartdocs/audits/findings/` | medium | no |
-| `doctrine-candidate` | `smartdocs/doctrine/candidate/` | low | no |
-| `architecture` | `smartdocs/architecture/` | high | yes |
-| `decision` | `smartdocs/decisions/` | high | yes |
-| `deprecated-noise` | `smartdocs/runtime/generated/` | low | no |
-
-## Classification process (per file)
-
-1. Read the document.
-2. Check for explicit Polaris front-matter (`status`, `authority`, `issue`, `classification`). If present and unambiguous: assign classification with **confidence: high**.
-3. Otherwise infer from content signals and assign a confidence level:
-   - Contains Polaris architectural assertions or "how things should work" → `doctrine-candidate`
-   - Structured spec with headings (Spec ID, Status, Purpose, etc.) → `spec-raw`
-   - Active spec governing in-flight work referencing an open issue → `spec-active` (flag for approval)
-   - Run output, telemetry summaries, session notes → `runtime-summary`
-   - Structured run output with metrics → `run-report`
-   - Contains `FINDING:` markers or audit-style analysis → `audit-finding`
-   - ADR-style decision record → `decision` (flag for approval)
-   - Architectural diagrams or structural design context → `architecture` (flag for approval)
-   - Low-signal, transient, or auto-generated content → `deprecated-noise`
-4. Assign a confidence level per file:
-   - **high**: explicit front-matter present, or content matches exactly one signal with no ambiguity
-   - **low**: multiple signals match, or content is sparse/unclear
-5. Routing by confidence:
-   - **high confidence** → auto-place to the classified target in step 04 (no pause, no user input required — except `spec-active`, `architecture`, `decision` which always require approval regardless of confidence)
-   - **low confidence** → route to `smartdocs/raw/` as holding area; record reason in telemetry
-6. When confidence cannot be determined: default to **low** and route to `smartdocs/raw/`.
-
-## Approval-required classifications
-
-For `spec-active`, `architecture`, and `decision`: do not route automatically regardless of confidence. Surface for user confirmation before step 04 proceeds for those files. Emit:
-
-```text
-**needs-input**: <n> file(s) classified as approval-required (<classes>).
-Proposed placements:
-  <file> → <target> [confidence: high|low]
-Confirm placement before step 04 proceeds for these files.
-```
-
-High-confidence, non-approval-required files proceed to step 03 immediately without pause.
-Low-confidence files are routed to `smartdocs/raw/` and noted in the step 05 summary.
-
-## Scope declarations
-
-```yaml
-allowed_files:
-  - source files in the batch (read only)
-  - smartdocs/specs/active/docs-authority-model.md (reference)
-expected_evidence:
-  - every file in batch assigned a classification and confidence level
-  - approval-required files surfaced before step 04
-  - low-confidence files routed to smartdocs/raw/ with telemetry note
-  - high-confidence non-approval files proceed automatically
-stop_rules:
-  - file cannot be read
-```
-
-## Artifact update
-
-Update `current-state.json`:
-- `current_step_id: 02-classify-batch`
-- `classifications: { "<file>": { "class": "<class>", "target": "<path>", "confidence": "high|low", "approval_required": true|false, "auto_place": true|false } }`
-
-Emit `docs-ingest-classified` telemetry event per file.
-
-## Next step
-
-03-conflict-check

package/dist/workspace/workspace/.polaris/skills/docs-ingest/steps/03-conflict-check.md

@@ -1,66 +0,0 @@
----
-name: docs-ingest-step-03-conflict-check
-description: Compare each classified file against doctrine/active/ and specs/active/ to detect contradictions or overlapping scope before placement.
----
-
-# Step 03 — Conflict check
-
-## Purpose
-
-Prevent silent contradiction of active doctrine or specs. Every conflict must be surfaced. None may be suppressed.
-
-## Check sequence (per file)
-
-1. **Active doctrine check** — compare document assertions against all files in `smartdocs/doctrine/active/`.
-   - Direct contradiction (document asserts X; existing active doctrine asserts not-X) → **HALT**. Report conflict. Do not continue until user resolves.
-
-2. **Active spec overlap** — compare document scope against `smartdocs/specs/active/`.
-   - Overlapping scope (two specs govern the same surface) → flag as candidate supersede. Surface recommendation to user. Do not halt; continue with warning.
-
-3. **Stale assumption check** — scan for references to APIs, file paths, commands, or module names that no longer exist (cross-reference `.polaris/map/index.json`).
-   - Stale assumption found → record in `current-state.json` under `stale_assumptions` and emit `docs-ingest-stale-assumption` telemetry. Do not halt. Do not mutate source files.
-
-4. **No conflicts** → proceed to step 04.
-
-## Halt behavior
-
-On direct doctrine contradiction:
-
-```text
-**BLOCKED — doctrine conflict detected**
-File: <source path>
-Conflicts with: <smartdocs/doctrine/active/<file>>
-Assertion: <what conflicts>
-Required: user must resolve before ingest can proceed for this file.
-```
-
-Do not advance to step 04 for the conflicting file until resolved or reclassified. Non-conflicting files in the same batch may proceed.
-
-## Scope declarations
-
-```yaml
-allowed_files:
-  - source files from batch (read only)
-  - smartdocs/doctrine/active/ (read only)
-  - smartdocs/specs/active/ (read only)
-  - .polaris/map/index.json (read only)
-expected_evidence:
-  - all files checked against active doctrine and specs
-  - direct contradictions halted and reported
-  - stale assumptions recorded in current-state.json
-  - overlaps surfaced with candidate-supersede recommendation
-stop_rules:
-  - direct doctrine contradiction (file held; batch may continue)
-```
-
-## Artifact update
-
-Update `current-state.json`:
-- `current_step_id: 03-conflict-check`
-- `conflicts: [{ "file": "<path>", "type": "contradiction|overlap|stale", "detail": "..." }]`
-
-Emit `docs-ingest-conflict-detected` for each conflict found.
-
-## Next step
-
-04-place-and-link

package/dist/workspace/workspace/.polaris/skills/docs-ingest/steps/04-place-and-link.md

@@ -1,77 +0,0 @@
----
-name: docs-ingest-step-04-place-and-link
-description: Move classified files to their target authority directories within smartdocs/, write provenance records, and update Polaris map entries.
----
-
-# Step 04 — Place and link
-
-## Purpose
-
-Execute placements for all files that cleared steps 02–03. High-confidence, non-approval-required files are placed automatically. Approval-required files wait for explicit user confirmation. Low-confidence files land in `smartdocs/raw/`. All target paths are within `smartdocs/`. Write provenance. Update the map.
-
-## Placement rules (per file)
-
-1. **Check `auto_place` flag** — read from `current-state.json` classifications:
-   - `auto_place: true` (high confidence, non-approval-required) → proceed immediately
-   - `auto_place: false`, `approval_required: false` (low confidence) → target is `smartdocs/raw/`; proceed immediately
-   - `approval_required: true` → hold until user confirms
-
-2. **Verify target directory** — ensure the target path from step 02 exists. Create it if missing (within `smartdocs/` only).
-
-3. **Check for existing file** at the target path. If a file already exists there: halt for that file and report. Do not overwrite without explicit approval.
-
-4. **Use the Polaris CLI** — do not move files manually. The CLI handles provenance, map updates, and duplicate detection:
-   - `spec-raw` or low-confidence fallback: `npm run polaris -- docs ingest --file <path>` (CLI routes to `smartdocs/raw/`; if source is already there, no move occurs)
-   - `doctrine-candidate`: `npm run polaris -- doctrine draft <path>`
-   - All other classifications: use `npm run polaris -- docs ingest --file <path>`
-   - If source is already in `smartdocs/` (reclassification): update front-matter only, re-run ingest to refresh provenance.
-   - Do not write anything to root `docs/`.
-
-5. **Doctrine-candidate front-matter** — the CLI injects this automatically via `doctrine draft`. For reference, the added fields are:
-   ```yaml
-   status: candidate
-   candidate-since: <YYYY-MM-DD>
-   source: <original-path>
-   ```
-   Emit `doctrine-candidate-proposed` telemetry event.
-
-6. **Provenance record** — the CLI writes `<filename>.provenance.json` alongside the placed file automatically. Verify it exists after placement.
-
-7. **Update Polaris map** — the CLI calls `updateMapEntry` internally. After the batch: run `npm run polaris -- map update --changed` to synchronize the atlas.
-
-## Hard rules
-
-- All placements land within `smartdocs/`. Never root `docs/`.
-- High-authority targets (`doctrine/active/`, `specs/active/`, `architecture/`, `decisions/`) are BLOCKED without explicit user approval. Halt and report if attempted without it.
-- Low-confidence files always land in `smartdocs/raw/` regardless of inferred class.
-- The CLI handles file moves — do not use `mv` or `cp` directly on files under `smartdocs/`. Manual moves bypass `.smartdocignore` enforcement.
-- If the CLI rejects a file as ignored (e.g., `POLARIS.md`, `SUMMARY.md`, `README.md`), do NOT move it manually. Leave it in `raw/` and note it in the step 05 summary as ineligible.
-
-## Scope declarations
-
-```yaml
-allowed_files:
-  - source files (batch)
-  - smartdocs/ (target hierarchy — read and write via CLI)
-  - .polaris/map/index.json (read and write)
-  - .polaris/map/file-routes.json (read and write)
-expected_evidence:
-  - all approved files placed at correct target paths within smartdocs/
-  - provenance records written alongside each placed file
-  - map updated via npm run polaris -- map update --changed
-  - low-confidence files confirmed routed to smartdocs/raw/
-  - no placements to root docs/ or high-authority paths without approval
-stop_rules:
-  - target path collision without approval
-  - high-authority placement attempted without approval flag
-```
-
-## Artifact update
-
-Update `current-state.json`:
-- `current_step_id: 04-place-and-link`
-- `placed: [{ "file": "<original>", "target": "<placed-path>", "class": "<class>" }]`
-
-## Next step
-
-05-finalize-ingest

package/dist/workspace/workspace/.polaris/skills/docs-ingest/steps/05-finalize-ingest.md

@@ -1,49 +0,0 @@
----
-name: docs-ingest-step-05-finalize-ingest
-description: Emit completion telemetry, mark the cluster complete, update current-state, and report the placement summary.
----
-
-# Step 05 — Finalize ingest
-
-## Purpose
-
-Close out the ingest session cleanly. Emit telemetry. Write final state. Report.
-
-## Actions
-
-1. **Emit `docs-ingest-complete` telemetry** for each processed file.
-
-2. **Update cluster manifest** (`.polaris/docs-ingest/<cluster-id>.json`):
-   - `status: complete`
-   - `completedAt: <ISO timestamp>`
-
-3. **Update `current-state.json`**:
-   - `status: complete`
-   - `current_step_id: 05-finalize-ingest`
-   - `completed_at: <ISO timestamp>`
-
-4. **Report placement summary**:
-   ```text
-   **docs-ingest complete**
-   Processed:           <n> files
-   Placed:
-     <original> → <smartdocs/target>
-     ...
-   Pending user approval: <files requiring approval, if any> | none
-   Conflicts:           <none | list with resolution required>
-   Map updated:         yes | failed (<detail>)
-   Next cluster:        <cluster-id> | none pending
-   ```
-
-5. **Bootstrap packet** — if more clusters remain pending in `.polaris/docs-ingest/`, emit guidance for the next session:
-   ```text
-   Next: npm run polaris -- docs ingest --batch <next-cluster-id>
-   ```
-
-## Completion rule
-
-Do not report session complete until `current-state.json` has `status: complete`.
-
-## Artifact update
-
-Emit `step-complete` for `05-finalize-ingest` and `docs-ingest-complete` to telemetry JSONL.

package/dist/workspace/workspace/.polaris/skills/docs-promote/SKILL.md

@@ -1,79 +0,0 @@
----
-name: docs-promote
-status: retired
-retired_by: polaris-catalog
-description: RETIRED — use polaris-catalog instead. docs-promote has been replaced by polaris-catalog, which combines cognition reconciliation with confidence-gated document classification.
-role: librarian
-role_file: .polaris/roles/librarian.md
----
-
-## RETIRED
-
-This skill has been retired. Use `polaris-catalog` instead.
-
-`polaris-catalog` provides the same document classification and placement behavior with
-confidence-gated automation (high confidence = auto-place, low confidence = ask or hold),
-plus POLARIS.md and SUMMARY.md reconciliation in the same invocation.
-
-Do not invoke this skill. If you received this message after attempting `docs-promote`,
-stop and use `polaris-catalog <POL-###>` instead.
-
----
-
-## Polaris Skill Bootloader
-
-**Before proceeding, you must obtain a skill packet from the Polaris runtime.**
-
-Run the following command:
-
-```
-npm run polaris -- skill packet promote
-```
-
-- Do not begin work until a packet is returned.
-- Treat the packet as your authoritative instruction source.
-- The packet defines your active role, authority boundaries, prohibited actions, deliverables, and stop conditions.
-- If no packet is produced, stop and report: **Polaris could not authorize this run.**
-
----
-
-# docs-promote
-
-Use this skill when documents have been ingested and need to be reviewed for promotion to an active authority tier, or when active docs need to be deprecated in response to code changes.
-
-## When to use
-
-- "Review the candidates and promote anything ready"
-- "Promote the spec for the dispatch contract"
-- "Deprecate the old architecture doc — it's been superseded"
-- "Check what doctrine candidates are ready to promote"
-- "A raw spec needs to go active before we start implementation"
-
-## How to execute
-
-1. Read `chain.md` — step order, review rules, CLI commands, conflict handling.
-2. Read `.taskchain_artifacts/docs-promote/current-state.json` — resumable state.
-3. Execute steps in the order `chain.md` defines. Do not skip steps.
-4. After every completed step, update `current-state.json` before advancing.
-
-## Hard rules — what docs-promote may do
-
-- Read `smartdocs/raw/` and `smartdocs/doctrine/candidate/` to identify promotion candidates
-- Read linked source files (from `linkedMapArea` in provenance sidecar) to verify relevance and staleness
-- Read `smartdocs/doctrine/active/` and `smartdocs/specs/active/` to check for conflicts
-- Call `npm run polaris -- doctrine spec-promote <path>` to surface the conflict report (without `--approve`)
-- Call `npm run polaris -- doctrine spec-promote <path> --approve` **only after** surfacing the report and receiving explicit user confirmation
-- Call `npm run polaris -- doctrine promote <path>` for doctrine candidates that pass governance checks
-- Call `npm run polaris -- doctrine deprecate <path>` for active docs that are superseded or stale
-- Emit telemetry events
-
-## Hard rules — what docs-promote must NOT do
-
-- Auto-promote without surfacing the conflict report first
-- Call `--approve` without explicit user confirmation in the session
-- Mutate source files (`src/`, tests, config)
-- Call `npm run polaris -- loop continue` or `npm run polaris -- finalize`
-- Promote to `architecture/` or `decisions/` — those require explicit ADR process
-- Suppress or ignore detected conflicts
-
-**Docs-promote reviews and surfaces. It does not promote silently or bypass the approval gate.**

package/dist/workspace/workspace/.polaris/skills/docs-promote/chain.json

@@ -1,25 +0,0 @@
-{
-  "name": "docs-promote-chain",
-  "steps": [
-    "01-orient-promote",
-    "02-review-candidates",
-    "03-read-linked-code",
-    "04-conflict-surface",
-    "05-await-approval",
-    "06-execute-promote-deprecate",
-    "07-finalize-promote"
-  ],
-  "terminal_steps": ["07-finalize-promote"],
-  "scope": "docs-promote-only",
-  "forbidden_actions": [
-    "src file mutations",
-    "polaris loop continue",
-    "polaris finalize",
-    "git push",
-    "pr creation",
-    "spec-promote --approve without user confirmation in session",
-    "doctrine promote without governance field check",
-    "architecture/ writes",
-    "decisions/ writes"
-  ]
-}

package/dist/workspace/workspace/.polaris/skills/docs-promote/chain.md

@@ -1,80 +0,0 @@
----
-name: docs-promote-chain
-description: Route map for docs-promote — step order, CLI reference, canonical paths, run ID format, telemetry, and artifact authority. Step detail lives in steps/.
----
-
-# docs-promote chain
-
-## Authority
-
-**Polaris runtime state is authoritative. Chat reasoning is not authoritative.**
-
-Query runtime state before acting. Do not infer promotion readiness from conversation context.
-
-## Step traversal order
-
-```text
-01-orient-promote
-02-review-candidates
-03-read-linked-code
-04-conflict-surface
-05-await-approval
-06-execute-promote-deprecate
-07-finalize-promote
-```
-
-Read the current step's file in `steps/` before acting. Do not read ahead.
-
-## CLI
-
-Always use the repo-local Polaris CLI:
-
-```
-npm run polaris -- doctrine draft <path>
-npm run polaris -- doctrine promote <path>
-npm run polaris -- doctrine deprecate <path>
-npm run polaris -- doctrine spec-promote <path>
-npm run polaris -- doctrine spec-promote <path> --approve
-```
-
-Never assume a globally linked `polaris` command exists.
-
-## Canonical paths
-
-| State | Path |
-|---|---|
-| Drop zone | `smartdocs/raw/` |
-| Doctrine staging | `smartdocs/doctrine/candidate/` |
-| Active doctrine | `smartdocs/doctrine/active/` |
-| Deprecated doctrine | `smartdocs/doctrine/deprecated/` |
-| Active specs | `smartdocs/specs/active/` |
-| Implemented specs | `smartdocs/specs/implemented/` |
-| Superseded specs | `smartdocs/specs/superseded/` |
-
-## Run ID format
-
-`docs-promote-<slug>-<YYYY-MM-DD>-<seq>` — e.g. `docs-promote-dispatch-contract-2026-05-29-001`
-
-## Telemetry
-
-File: `.taskchain_artifacts/docs-promote/runs/<run-id>/telemetry.jsonl` (append-only).
-
-| Event | Trigger |
-|---|---|
-| `run-start` | Begin processing |
-| `step-complete` | End of every step |
-| `docs-promote-conflict-report` | Conflict check result per candidate |
-| `docs-promote-approved` | User approved a promotion |
-| `docs-promote-rejected` | User rejected a promotion |
-| `docs-promoted` | Successful promote/deprecate command |
-| `docs-promote-complete` | All candidates processed |
-
-Required fields: `event`, `run_id`, `timestamp`. Add `file` where applicable.
-
-## Artifact authority
-
-`.taskchain_artifacts/docs-promote/current-state.json` is the sole authoritative live state surface.
-
-- Update after every completed step — before advancing.
-- A step is NOT complete until the state update succeeds.
-- If the update fails: stop and report the persistence failure.

package/dist/workspace/workspace/.polaris/skills/docs-promote/steps/01-orient-promote.md

@@ -1,53 +0,0 @@
----
-name: docs-promote-step-01-orient-promote
-description: Generate run_id, emit run-start telemetry, load candidate list, confirm canonical target.
----
-
-# Step 01 — Orient promote
-
-## Purpose
-
-Establish bounded promotion context before touching any files. Confirm what to review, confirm the canonical target exists.
-
-## Actions
-
-1. **Generate `run_id`**: `docs-promote-<slug>-<YYYY-MM-DD>-<seq>`
-   - Resumed runs: generate new `run_id` first, emit telemetry immediately, then read `current-state.json` for prior `run_id`.
-
-2. **Emit `run-start` telemetry** — first I/O action:
-   ```bash
-   mkdir -p .taskchain_artifacts/docs-promote/runs/<run-id>
-   echo '{"event":"run-start","run_id":"<run-id>","prior_run_id":null,"timestamp":"<ISO>"}' \
-     >> .taskchain_artifacts/docs-promote/runs/<run-id>/telemetry.jsonl
-   ```
-   If this write fails: halt. Do not continue.
-
-3. **Confirm canonical target** — verify `smartdocs/` exists. If not: halt and report.
-
-4. **Restate working context** in under 6 bullets:
-   - `run_id` and fresh/resumed
-   - Candidates to review (raw/ + doctrine/candidate/)
-   - Canonical target confirmed
-
-## Scope
-
-```yaml
-allowed_files:
-  - .polaris/skills/docs-promote/chain.md
-  - .taskchain_artifacts/docs-promote/current-state.json
-  - .polaris/map/index.json
-stop_rules:
-  - run-start telemetry write fails
-  - smartdocs/ not found
-```
-
-## Artifact update
-
-Update `.taskchain_artifacts/docs-promote/current-state.json`:
-- `run_id`, `status: orienting`, `current_step_id: 01-orient-promote`, `updated_at`
-
-Emit `step-complete` for `01-orient-promote`.
-
-## Next step
-
-02-review-candidates

package/dist/workspace/workspace/.polaris/skills/docs-promote/steps/02-review-candidates.md

@@ -1,51 +0,0 @@
----
-name: docs-promote-step-02-review-candidates
-description: List promotion candidates from raw/ and doctrine/candidate/, read provenance sidecars, extract linkedMapArea.
----
-
-# Step 02 — Review candidates
-
-## Purpose
-
-Build the candidate list. Read every co-located provenance sidecar to know what linked code area each doc is associated with.
-
-## Actions
-
-1. **List candidates**:
-   - `smartdocs/raw/*.md`
-   - `smartdocs/doctrine/candidate/*.md`
-
-2. **For each candidate**, read `<filename>.provenance.json` if present. Extract:
-   - `linkedMapArea` — code area this doc covers
-   - `classifiedAs` — ingest classification
-   - `ingestedAt` — when it was ingested
-
-3. **Categorize** each candidate:
-   - `spec-raw` → route: `spec-promote` gate
-   - `doctrine-candidate` → route: doctrine governance check
-   - No provenance → route: spec-promote gate (default)
-
-4. If no candidates found: emit `step-complete`, update state with `candidates: []`, skip to step 07.
-
-## Scope
-
-```yaml
-allowed_files:
-  - smartdocs/raw/ (read only)
-  - smartdocs/doctrine/candidate/ (read only)
-  - .taskchain_artifacts/docs-promote/current-state.json
-stop_rules:
-  - directory read fails
-```
-
-## Artifact update
-
-Update `current-state.json`:
-- `current_step_id: 02-review-candidates`
-- `candidates: [{ file, classifiedAs, linkedMapArea, route }]`
-
-Emit `step-complete` for `02-review-candidates`.
-
-## Next step
-
-03-read-linked-code

package/dist/workspace/workspace/.polaris/skills/docs-promote/steps/03-read-linked-code.md

@@ -1,50 +0,0 @@
----
-name: docs-promote-step-03-read-linked-code
-description: Read the linked source area for each candidate and assess whether the doc is current, stale, or superseded.
----
-
-# Step 03 — Read linked code
-
-## Purpose
-
-Ground each candidate in the actual codebase. A doc that no longer matches its linked code area should not be promoted — it should be updated or discarded.
-
-## Actions
-
-For each candidate with a `linkedMapArea`:
-
-1. **Read the linked area**:
-   - Read `<linkedMapArea>/POLARIS.md` if present
-   - Read up to 3 key source files in the area (prefer files named in the doc)
-
-2. **Assess relevance**:
-   - `current` — doc accurately describes what the code does
-   - `stale` — code has evolved; doc's assumptions are partially outdated
-   - `superseded` — the area no longer exists or has been fully replaced
-
-3. **Record findings** — one verdict per candidate with a brief rationale (≤2 sentences).
-
-For candidates with **no `linkedMapArea`**: mark as `unlinked` — cannot assess code relevance. Proceed; surface to user in step 05.
-
-## Scope
-
-```yaml
-allowed_files:
-  - <linkedMapArea>/ (read only — POLARIS.md and up to 3 source files)
-  - .polaris/map/index.json (read only)
-  - .taskchain_artifacts/docs-promote/current-state.json
-stop_rules:
-  - linked area not found in map (record as unlinked; do not halt)
-```
-
-## Artifact update
-
-Update `current-state.json`:
-- `current_step_id: 03-read-linked-code`
-- Per candidate: `relevance: current|stale|superseded|unlinked`, `relevance_rationale: "..."`
-
-Emit `step-complete` for `03-read-linked-code`.
-
-## Next step
-
-04-conflict-surface