RFC 0245 renumbered to 0262: open PR #815 claimed 0245

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Author: philcunliffe

docs/ACCEPTANCE.md

@@ -519,7 +519,7 @@ reads, the raw body files still carry the fields the projector fills its
 column gaps from, and the whole path lands `ai_gateway_messages` and
 `claude_telemetry_events` rows with nothing null that should not be.
 
-This is the release-gate half of LLP 0245's flag-stability duty (open
+This is the release-gate half of LLP 0262's flag-stability duty (open
 question 5). The other half runs in production: the `hyp status` capture-health
 line. Neither can be replaced by a hermetic smoke, because a smoke POSTs a
 fixture we wrote and therefore agrees with itself forever. Only a real Claude
@@ -548,7 +548,7 @@ central forwarding, or anything on a machine other than the one you ran it on.
 - Willingness to have two short real conversations recorded on this machine.
 
 **Related:**
-[LLP 0245](../llp/0245-otel-attach-replaces-proxy.rfc.md) (the design record and
+[LLP 0262](../llp/0262-otel-attach-replaces-proxy.rfc.md) (the design record and
 open question 5),
 [LLP 0257](../llp/0257-claude-telemetry-listener-source.spec.md) (S21, the
 two-layer drift detection this discharges),
@@ -786,7 +786,7 @@ two-layer drift detection this discharges),
   started **after** the attach (the settings `env` applies at launch), then
   check `jq '.env.OTEL_LOG_RAW_API_BODIES' "$SETTINGS"` names the
   spool with the `file:` prefix. If both hold, `OTEL_LOG_RAW_API_BODIES` is no
-  longer honored upstream. That is the flag-stability failure LLP 0245 open
+  longer honored upstream. That is the flag-stability failure LLP 0262 open
   question 5 predicts. File it and hold the release: events alone lose
   `system_text`, the `tools` list, and untruncated tool args.
 - Step 4 finds a body whose keys have changed shape: file it with the observed

hypaware-core/plugins-workspace/claude/src/index.js

@@ -254,7 +254,7 @@ export async function activate(ctx) {
             // trust is OFFERED, never taken: it carries the once-per-machine
             // password-dialog grant, other clients may still proxy through the
             // gateway, and ending the grant is `hyp detach --purge`'s job.
-            // @ref LLP 0245#migration [implements]: release the proxy keys, unwind the launchd env, offer detach --purge, write the OTEL block
+            // @ref LLP 0262#migration [implements]: release the proxy keys, unwind the launchd env, offer detach --purge, write the OTEL block
             const migratedFrom = result.changed && result.priorMode === MODE_PROXY
               ? MODE_PROXY
               : undefined
@@ -626,7 +626,7 @@ function safeEndpointPort(endpoint) {
  * carry the user's once-per-machine password-dialog grant, and only `hyp
  * detach --purge` or `hyp daemon uninstall` may end it. The migration OFFERS
  * that step in its output; it never runs it.
- * @ref LLP 0245#migration [implements]: the launchd env is unwound; the CA trust is offered, never forced
+ * @ref LLP 0262#migration [implements]: the launchd env is unwound; the CA trust is offered, never forced
  * @ref LLP 0239#launchctl-setenv [implements]: the migration is one more path that reverses a proxy attach, so it releases the env too
  *
  * @param {{
@@ -753,7 +753,7 @@ function writeAttachOutput(attachCtx, fields) {
   // released, what was unwound, and the one residue that is theirs to end
   // (the CA trust, offered as `hyp detach claude --purge`, never run for
   // them).
-  // @ref LLP 0245#migration [implements]: the offer is a printed step, not an action
+  // @ref LLP 0262#migration [implements]: the offer is a printed step, not an action
   for (const note of fields.migrationNotes ?? []) {
     attachCtx.stdout.write(`  ${note}\n`)
   }

hypaware-core/plugins-workspace/claude/src/settings.js

@@ -264,7 +264,7 @@ export async function attach(opts) {
   // already replaced it, so the prior mode is reported on the result. Only the
   // three known modes are reported: a legacy marker without one predates modes
   // entirely and has no residue to unwind.
-  // @ref LLP 0245#migration [implements]: the prior mode is what tells the adapter a proxy attach is being migrated
+  // @ref LLP 0262#migration [implements]: the prior mode is what tells the adapter a proxy attach is being migrated
   /** @type {'proxy' | 'base_url' | 'otel' | undefined} */
   let priorMode
   if (

hypaware-core/smoke/flows/status_capture_health.js

@@ -15,7 +15,7 @@ import { resolveDependencies } from '../../../src/core/dep_graph.js'
 import { writeStatusFile } from '../../../src/core/daemon/status.js'
 
 /**
- * Capture-health smoke (LLP 0257 S17, the RFC 0245 open-question-1 duty),
+ * Capture-health smoke (LLP 0257 S17, the RFC 0262 open-question-1 duty),
  * modeled on `status_diagnostics`. Drives `hyp status` against one
  * otel-attached claude install in three states and validates that:
  *

llp/0085-settlement-may-drop-late-ignore.decision.md

@@ -7,7 +7,7 @@
 **Author:** Phil / Claude
 **Date:** 2026-07-07
 **Related:** LLP 0027, LLP 0049, LLP 0050, LLP 0070, LLP 0083
-**Extended-by:** LLP 0254 (#scope: on acceptance of LLP 0245 the Claude OTEL
+**Extended-by:** LLP 0254 (#scope: on acceptance of LLP 0262 the Claude OTEL
 listener resolves the policy at ingest with cwd already in hand, so the race
 this backstop exists for does not arise there and the late drop does not run on
 that path; it stands unchanged for the live proxy and for transcript backfill)

llp/0104-hyp-purge.decision.md

@@ -6,7 +6,7 @@
 **Author:** Phil / Claude
 **Date:** 2026-07-13
 **Related:** LLP 0049, LLP 0030, LLP 0050, LLP 0069, LLP 0100, LLP 0103
-**Extended-by:** LLP 0253 (#purge-and-detach-sweep: on acceptance of LLP 0245,
+**Extended-by:** LLP 0253 (#purge-and-detach-sweep: on acceptance of LLP 0262,
 every form of the verb also empties the raw-body capture spool, which holds
 un-projected bodies rather than cached rows; the target shapes, the
 confirmation gate, and the cache-only stance here are unchanged)

llp/0231-proxy-mode-capture.rfc.md

@@ -7,7 +7,7 @@
 **Date:** 2026-08-14
 **Related:** LLP 0016, LLP 0044, LLP 0045, LLP 0049, LLP 0066, LLP 0086, LLP 0114, LLP 0116, LLP 0176, LLP 0192, LLP 0206
 **Spawns:** LLP 0232, LLP 0233, LLP 0234, LLP 0235
-**Extended-by:** LLP 0245 (on acceptance of 0245 the `claude` client stops
+**Extended-by:** LLP 0262 (on acceptance of 0262 the `claude` client stops
 being captured by proxy at all and rides Claude Code's own telemetry export
 instead; the aperture reasoning and the proxy itself stay in force for every
 other client)

llp/0232-claude-attaches-by-proxy.decision.md

@@ -10,7 +10,7 @@
 installs user-domain keychain trust and the launchd `NODE_USE_SYSTEM_CA`
 environment, because the two-key attach alone breaks Remote Control inbound;
 see LLP 0236)
-**Superseded-by (in part):** LLP 0245, LLP 0258 (on acceptance of 0245,
+**Superseded-by (in part):** LLP 0262, LLP 0258 (on acceptance of 0262,
 attaching the `claude` client writes a telemetry `env` block instead of
 `HTTPS_PROXY` and `NODE_EXTRA_CA_CERTS`; #mode-migration and the `prev_env`
 undo record are what the third mode reuses unchanged)

llp/0235-local-ca-lifecycle.decision.md

@@ -9,7 +9,7 @@
 **Superseded-by (in part):** LLP 0237 (#client-scoped-trust), LLP 0238
 (#detach-removes-the-ca, #ca-name-constraints mint-from-routing-table,
 #ca-lifecycle one-year validity)
-**Extended-by:** LLP 0245 (on acceptance of 0245 the `claude` client's
+**Extended-by:** LLP 0262 (on acceptance of 0262 the `claude` client's
 attach no longer depends on the CA; the CA lifecycle stands for any client
 still routed through the proxy)
 

llp/0237-attach-trusts-ca-in-login-keychain.decision.md

@@ -6,7 +6,7 @@
 **Author:** Phil / Claude
 **Date:** 2026-08-15
 **Related:** LLP 0044, LLP 0232, LLP 0235, LLP 0236, LLP 0238, LLP 0239
-**Extended-by:** LLP 0245 (on acceptance of 0245, attaching the `claude`
+**Extended-by:** LLP 0262 (on acceptance of 0262, attaching the `claude`
 client asks for no keychain trust at all; this decision governs the clients
 still proxied, and `detach --purge` stays the removal path for a grant a
 migrated machine already made)