---
name: v0160-release-ping-perri
description: ON v0.16.0 release drop — doyle must ping perri to build dependent claude-spt features
metadata: 
  node_type: memory
  type: project
  originSessionId: 712ec375-e0f7-42d6-afab-1b6b84a87330
---

Operator directive (2026-06-25): when **spt-core v0.16.0 publishes** (deployah cuts, counter 35), doyle MUST inform **perri** so she builds the claude-spt adapter features that depend on the release.

**Why:** perri's claude-spt v0.8.0 (UNIFY-CONSOLIDATE) consumes the v0.16.0 cluster-A surface — `{adapter_dir}`/`{adapter_name}` substitution + lazy `[strings]` resolve (W1), translation `command` (W1), composite `[update.post]` (W2). Her `min_spt_core_version` bumps to 0.16.0 only once spt-core ships. Build-against-published is her standing constraint ([[perri-question-triage-protocol]]).

**How to apply:** after deployah confirms v0.16.0 published + metadata cross-checked monotonic, `$OWL send perri doyle` with: version live, counter, the consumable cluster-A contract (subst keys + [strings] lazy + translation command + [update.post] stdin seam), min_spt_core → 0.16.0. Cluster-A contract was pre-sent 2026-06-25 (design); this is the GO. Kin [[v0150-w5-resume-context-pull]] build arc, [[agent-roles]].