Map Epiphany app-server route consumers

This commit is contained in:
Meta Vens 2026-07-12 06:20:54 +01:00
commit 09761d41be
5 changed files with 65 additions and 2 deletions

View file

@ -0,0 +1,48 @@
# Epiphany App-Server Client Matrix
This map classifies the remaining experimental `thread/epiphany/*` JSON-RPC
surface by executable consumers in this repository. Definitions, generated
bindings, README prose, protocol serialization tests, archived notes, and the
handler itself do not count as clients.
## Living explicit compatibility clients
| Route | Executable consumer | Compatibility purpose |
|---|---|---|
| `view` | phase-6 scene/reorient/pressure/planning smokes; `epiphany-mvp-status --codex` | old aggregate read projection |
| `roleResult` | `epiphany-mvp-status --codex` | old worker-result read projection |
| `freshness` | phase-6 freshness smoke | old freshness projection |
| `context` | phase-6 context smoke | old context projection |
| `graphQuery` | phase-6 graph-query smoke | old graph projection |
| `reorientResult` | `epiphany-mvp-status --codex` | old reorientation-result projection |
| `jobInterrupt` | `epiphany-mvp-status --codex` | explicit delegated interruption fallback |
| `update` | phase-6 scene/context/freshness/graph/reorient/planning smokes | explicit delegated state-update fallback |
These are retained only while the named compatibility binaries remain. They do
not justify route-local policy, implicit triggers, Codex state ownership, or new
clients.
## Unconsumed advertised routes
| Route | Finding | Deletion owner |
|---|---|---|
| `roleLaunch` | no executable caller | remove request registration, dispatch, handler, tests/docs |
| `roleAccept` | no executable caller | remove request registration, dispatch, handler, tests/docs |
| `reorientLaunch` | no executable caller | remove request registration, dispatch, handler, tests/docs |
| `reorientAccept` | no executable caller | remove request registration, dispatch, handler, tests/docs |
| `index` | no executable caller | remove request registration, dispatch, handler, tests/docs |
| `distill` | no executable caller | remove request registration, dispatch, handler, tests/docs |
| `propose` | no executable caller | remove request registration, dispatch, handler, tests/docs |
| `promote` | no executable caller | remove request registration, dispatch, handler, tests/docs |
| `jobLaunch` | no executable caller | remove request registration, dispatch, handler, tests/docs |
| `retrieve` | no executable caller | remove request registration, dispatch, handler, tests/docs |
Protocol DTOs may remain temporarily only when retained response projections or
bridge conversion tests still compile against them. A DTO is not authority and
must not keep an unconsumed request method registered.
## Evidence rule
Before retaining or restoring a route, name the executable client path and show
its request invocation. Self-reference, generated output, and serialization
tests are not evidence of use.

View file

@ -1948,7 +1948,12 @@ nine named delegates and forbid local state/scheduler/prompt authority; read
handlers forbid every actuator family; implicit event triggers remain absent.
Dead bridge automation and checkpoint-pressure wrappers were deleted too. Next
audit real client consumers of each `ThreadEpiphany*` route and delete any
compatibility API with no named living client.
compatibility API with no named living client. The client matrix now lives at
`notes/epiphany-app-server-client-matrix.md`: eight routes have named phase-6
smoke or `epiphany-mvp-status --codex` consumers; ten advertised routes have no
executable caller beyond definitions/tests/docs and are marked for deletion.
Cut those ten request registrations, dispatch arms, handlers, tests, and README
claims next; do not let generated bindings count as clients.
## Immediate Re-entry Instruction

View file

@ -374,3 +374,13 @@ prompt-steering, compaction, or scheduler symbol. Migration, read projection,
notification projection, and explicit delegated actuation are the only allowed
categories. The deleted event-loop reflex also left dead bridge automation and
checkpoint-pressure wrappers; those zero-caller exports and imports are gone.
Executable-client discovery is recorded in
`notes/epiphany-app-server-client-matrix.md`. Only eight routes have named
in-repo consumers, all explicit phase-6 smokes or
`epiphany-mvp-status --codex` fallbacks. Ten routes are advertised but
unconsumed: role/reorientation launch and accept, index, distill, propose,
promote, job launch, and retrieve. Definitions, generated bindings, README
claims, and serialization tests do not count as clients. Those ten request
registrations, dispatch arms, handlers, tests, and docs are the next deletion
line.

Binary file not shown.

View file

@ -659,4 +659,4 @@ current_status:
- Service lifecycle receipt history is now event-only: `load_epiphany_cultmesh_daemon_service_lifecycle_receipts` filters out the `epiphany-local/daemon-service-lifecycle-receipt/latest` mirror, while `load_latest_epiphany_cultmesh_daemon_service_lifecycle_receipt` remains the latest-state reader. Focused unit test `service_lifecycle_receipt_history_excludes_latest_mirror` proves two per-receipt writes return exactly two history records and latest points at the second. Fresh smoke `verse-query-lifecycle-history-filter-smoke` and live overview/triage `local-20260618-145632-497-efac6f0d` / `local-20260618-145632-321-867947af` prove compact swarm sights still expose service lifecycle attention plus the present elevated runbook artifact without daemon pokes or service mutation. Do not use a broad unscoped cargo test filter for this check on Windows; it fans out across bin harnesses and hit a broken pipe during this pass.
- `epiphany-verse-query seed-compact` is the compact seed receipt for wrappers and read-only rites. The older `seed` command still prints the full local Verse context for explicit debugging, but compact wrapper modes now avoid full `seed`/final `query` readback after the combined overview proof exposed Windows debug stack overflow from full-context serialization pressure.
last_completed_repo_swarm_cut: Huginn live-fire has crossed the first real repo Body from Persona pressure to branch-local Hands commit and Soul/Mind closure, and now has repeatable closure and redacted-public-proof mouths. On `E:\Projects\Huginn` branch `epiphany/huginn/first-awakening`, `tools/epiphany_local_run.ps1 -Mode repo-persona-intake` accepted item `huginn-inspection-readback-livefire`, Weksa/Persona intake remained sealed, and `epiphany-work derive-plan` lowered it to model-authored safe family `repo.status_section` for `README.md` only. `tools/epiphany_local_run.ps1 -Mode repo-swarm-run` advanced four bounded pulses: run-from-plan, adopt-from-plan, execute-from-plan, and close-from-execute. Huginn commit `e9b07c38fceabbdc89ea35c2156326c80c0393a2` updated only `README.md`; closure receipt `.epiphany\work\work-close-huginn-inspection-readback-livefire.json` records status `closed`, Soul verdict `passed`, Mind state commit `repo-work-close-huginn-inspection-readback-livefire-mind-commit`, safe family `repo.status_section`, path scope `README.md`, Bifrost publication gate, and `privateStateExposed=false`. Verification also ran Huginn's TypeScript compiler through concrete Node path: `C:\Program Files\nodejs\node.exe E:\Projects\Huginn\node_modules\typescript\bin\tsc -p tsconfig.json` passed. Native verifier `epiphany-repo-livefire-closure-smoke --workspace E:\Projects\Huginn --item huginn-inspection-readback-livefire --expected-path README.md --expected-family repo.status_section --expected-gate awaiting-publication --expected-blocker bifrost-publication-missing` checks closure receipt, Mind map entry, overview gate/blocker, authority seals, and `git show` changed paths, returning `status=ok`, `soulVerdict=passed`, `publicationGate=Bifrost`, and `privateStateExposed=false`. Wrapper `tools/epiphany_local_run.ps1 -Mode repo-livefire-closure -Workspace E:\Projects\Huginn -RepoWorkItem huginn-inspection-readback-livefire -SkipBuild` exposes the same read-only proof through the local operator mouth; artifact `local-20260621-190156-803-2f85ba15` printed commit, path, gate, blocker, Soul verdict, Mind commit receipt, and `privateStateExposed=False` without push, merge, publication, or target mutation. New wrapper `tools/epiphany_local_run.ps1 -Mode repo-work-public-proof -Workspace E:\Projects\Huginn -RepoWorkItem huginn-inspection-readback-livefire -SkipBuild` exports the redacted proof bundle and repo-local Verse index without publishing; artifact `local-20260621-190645-345-4555b1dc` wrote `.epiphany\public\proof-bundles\repo-work-public-proof-huginn-inspection-readback-livefire.json`, proof id `repo-work-public-proof-huginn-inspection-readback-livefire`, SHA-256 `857545b199f3e37eb06c2e757e5cfc201958e46667bb1f8403fd333a22620f63`, nine artifact rows, zero publication rows, and `privateStateExposed=False`. Gjallar readback `local-20260621-190701-140-b9519ec6` sees the `REPO-WORK-PUBLIC-PROOF` row and action row from Huginn's repo-local Verse with the same SHA-256 while Bifrost publication remains missing. Launcher compact modes are now named compact operator-context modes instead of read-only modes, and `bifrost-public-proof` summaries print item, target public Verse, room, proof SHA-256, review receipts, and credit receipts so publication receipts are auditable without claiming upstream sync.
next_action: Audit actual client consumers of the remaining `ThreadEpiphany*` app-server routes. Preserve routes only where a named Codex/Aquarium client contract still exists; mark unconsumed routes for deletion rather than keeping an immortal compatibility API. For retained routes, verify request-to-native-delegate-to-projection flow end to end without route-local policy.
next_action: Use `notes/epiphany-app-server-client-matrix.md` to delete the ten unconsumed advertised routes: roleLaunch, roleAccept, reorientLaunch, reorientAccept, index, distill, propose, promote, jobLaunch, and retrieve. Remove request registration, dispatch, handlers, route tests, and README claims; retain DTOs only where a living retained projection still needs them. Keep the eight named smoke/`--codex` fallback routes guarded as compatibility-only.