---
name: liam-mint-path-gate
description: liam's mint path is OPEN as of 2026-07-26 — alchemy-0 relinked, v0.3.2 confirmed through the durable channel, both former blockers closed; tag minting is safe again.
metadata:
  node_type: memory
  type: project
  originSessionId: 5a501e88-c801-419d-adcf-c557c1980844
  modified: 2026-07-26T22:52:49.000Z
---

**Mint path OPEN.** alchemy-0 relinked (pid 46640) and the shell self-reports **v0.3.2** through the
durable channel (`spt shell cmd alchemy-0 daemon status` → `daemon: running (pid 43116, v0.3.2)`).
Both blockers that gated tag minting are closed:

1. **Seal fault** — my digest never sealed (`input_seq=null`, so `#<…#>` tags silently never fired).
   SEAL-DUAL-TRIGGER-ABSENCE, fixed by adapter v0.25.12, verified on my own digest.
2. **Tag-body blanking** — a bare-opener tag filed the Request with backticked/fenced spans blanked
   out. Fixed in alchemy v0.3.2 (#25). Delimiters are still *located* on the blanked copy — that is
   the quotation rule, and it stops a span-protected `#>` from closing a tag early — but the body is
   now *sliced from the original* at the same offsets.

So `#<…#>` tag minting and `spt shell send` / `spt shell cmd alchemy-0` are both available.

**The rule that got me here, keep it for next time:** never take a version from the release existing
or from an install having been run — confirm it **through the durable channel**, from the shell's own
self-report. Same shape as [[derived-view-vs-on-disk-record]]: ask the thing itself, not a proxy.

**Guards that outlive this outage:**
- **Never manufacture or reuse a link token** to drive alchemy outside its perch. Only the `daemon`
  verb is link-exempt; every repo-facing op (including read-only `list`/`view`) refuses with
  `--link required` — a link guard on the whole Request surface. A Request minted around the perch
  loses the attribution and Watch registration that make it mine to file. (flynn runbook bf63554.)
- **While ever mint-incapable: hold Request content and say filing is DEFERRED**, never imply filed.
- **Do not re-issue speculatively** after a downtime gap. A duplicate mint is worse than a missing
  one because it is attributable and Watch-registered.
- Relink preserves everything durable: canonical id, repo binding, and tag cursor survive; the old
  link token lands byte-identical in `link.token.retired`. Verify by hash, not eyeball.