Centralize view enum projection
This commit is contained in:
parent
d32136531a
commit
06145e33aa
5 changed files with 44 additions and 36 deletions
Binary file not shown.
|
|
@ -443,6 +443,10 @@ current_status:
|
|||
indexing, state lookup, and typed retrieval responses; `retrieve_protocol.rs`
|
||||
owns Codex JSON-RPC retrieve/index response projection and absolute-path DTO
|
||||
validation.
|
||||
View response assembly no longer owns private lens/source/reorient-status
|
||||
projection helpers; those small enum conversions route through
|
||||
`protocol_edge`, so `view.rs` does not grow a second protocol dialect while
|
||||
the larger typed-view wall remains under judgment.
|
||||
The bridge still depends on vendored Codex for app-server protocol DTOs and
|
||||
absolute path validation, so the purification is not done.
|
||||
next_action: Continue Codex starvation and CultNet liberation by cutting bridge-internal response/projection authority. Prioritize the next coordinator/view seam that still composes policy-shaped facts instead of merely loading host facts and projecting core surfaces; keep MCP/OpenAI JSON only at their true protocol/text edges. Do not add compatibility adapters unless they protect a named ownership invariant.
|
||||
|
|
|
|||
Reference in a new issue