feat(track-a): promote P1 bridge from fresh main

[blakinio]

Track A P1-BRIDGE fresh-main replacement for #357

Task: OTC-20260816-track-a-p1-bridge-health-recovery
Base: main@dbd9520e2f8cc5a26f556bffaae2a83e139615f9
Execution: GitHub-hosted, runtime_access: none, physical E2E exclusively RUNTIME-owned.

Source PR #357 reached an accepted semantic implementation but its final branch is ahead 32 / behind 6 relative to current main. This replacement intentionally does not merge or rebase that stale history.

Exact replay

All implementation/test files are replayed byte-for-byte by exact blob SHA from accepted #357 head 9ddab031da32c69c55dd2f6940583c2523f00c06.

The two coordinator-serialized shared indexes were reused only after direct main -> #357 comparison proved each difference is exactly +1 / -0; the fresh replacement independently compares as exactly +1 / -0 for both CHANGELOG.md and MODULE_CATALOG.md.

Fresh branch comparison against current main is ahead 3 / behind 0 and contains only the P1 task, accepted bridge/test surface and those two one-line index additions.

Accepted semantics retained

• exact-client/profile fencing and owner-only bounded local IPC;
• Linux SO_PEERCRED + boot/PID/start/executable identity on lifecycle connections and matching PING identity envelope;
• fail-closed stale registration/process/endpoint rejection including same-path replacement;
• explicit distinction between completed zero-hit discovery and /proc scan errors;
• deterministic read-only health/reacquisition/recovery with no client launch/login/restart/signal/attach/input mutation;
• launcher.py LD_PRELOAD activation remains RUNTIME-owned;
• session-status remains DERIVED_UNTIL_LIVE_CORRELATION.

Source semantic repair runs 31947189849, 31947285170, 31947365151 were successful and source exact-head governance/CI had already passed. A later source-branch CMake retry failure was external GitHub HTTP 429 while cloning the Boost mirror, not a code regression.

This replacement still requires its own fresh exact-head Track A governance and repository CI before coordinator promotion/merge.

Current physical nonclaims remain :98 UNKNOWN, 6082 UNKNOWN, exact PID/session NOT_REGISTERED. No Synology runtime use, login, X11/VNC access, credentials, Track B mutation, owner Codex quota, OpenAI API token or owner-funded paid AI quota is used by this P1 producer.

[blakinio]

COORDINATOR ACCEPT. Fresh-main replay preserves the previously audited P1 implementation; changed-file review found no unrelated paths, source semantic findings are closed, source PR #357 is terminal superseded, and the later trusted-main advance is confined to non-overlapping canonical-runtime infrastructure/archive paths. Exact head fae521f has Track A governance 31951842202 = SUCCESS, canonical-live governance 31951842194 = SUCCESS, and repository CI 31951842289 = SUCCESS. Physical E2E is not applicable to this hosted producer; later live correlation remains RUNTIME-owned. Approved for ready-state/squash promotion.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

[blakinio]

Coordinator disposition: SUPERSEDED — close unmerged in favor of current-main replay #414.

PR #372's accepted P1 semantics are preserved exactly in #414: all tool/test/profile blobs were replayed byte-for-byte from this accepted head onto main@d3f186414256151c9d5e03f34c5a9026b1fba500. Compare proved #372 had become 30 commits behind current main and those intervening commits did not touch the P1 implementation or the two serialized shared-index paths.

PR #414 exact final checkpoint head c87ef86763ac2a92367831180ce623f7e7628ebe has zero review threads and successful Track A governance 31964526901, canonical-live governance 31964526899, and repository CI 31964527081. No unique accepted implementation change is lost by closing #372. Do not reopen or merge #372.