Keep role-board note rendering typed
This commit is contained in:
parent
27f88bfaef
commit
555c18cd0a
5 changed files with 6 additions and 5 deletions
|
|
@ -4,7 +4,6 @@ use codex_app_server_protocol::ThreadEpiphanyCrrcAction;
|
|||
use codex_app_server_protocol::ThreadEpiphanyCrrcRecommendation;
|
||||
use codex_app_server_protocol::ThreadEpiphanyJob;
|
||||
use codex_app_server_protocol::ThreadEpiphanyReorientAction;
|
||||
use codex_app_server_protocol::ThreadEpiphanyReorientStateStatus;
|
||||
use codex_app_server_protocol::ThreadEpiphanyRoleId;
|
||||
use codex_app_server_protocol::ThreadEpiphanyRoleLane;
|
||||
use codex_app_server_protocol::ThreadEpiphanyRoleStatus;
|
||||
|
|
@ -695,7 +694,7 @@ fn map_protocol_coordinator_role_status(
|
|||
|
||||
pub fn render_epiphany_roles_note(
|
||||
roles: &[EpiphanyRoleBoardLane],
|
||||
state_status: ThreadEpiphanyReorientStateStatus,
|
||||
state_status: CoreEpiphanyReorientStateStatus,
|
||||
recommendation: CoreEpiphanyCrrcAction,
|
||||
) -> String {
|
||||
render_role_board_note(
|
||||
|
|
|
|||
|
|
@ -334,7 +334,7 @@ pub async fn map_epiphany_view_response(
|
|||
.as_ref()
|
||||
.map(|role_board| role_board.roles.as_slice())
|
||||
.unwrap_or(&[]),
|
||||
reorient_state_status,
|
||||
core_reorient_state_status,
|
||||
recommendation
|
||||
.as_ref()
|
||||
.map(|recommendation| recommendation.action)
|
||||
|
|
|
|||
|
|
@ -65,7 +65,7 @@ remembers doctrine; the branch remembers the blade.
|
|||
- Role launch, role accept, and role-result runtime lookup now use core `EpiphanyRoleResultRoleId` inside the bridge. App-server maps `ThreadEpiphanyRoleId` at the JSON-RPC boundary and keeps it only for legacy request/response shape.
|
||||
- Reorient launch service results now use typed `EpiphanySurfaceSource`; app-server projects it into `ThreadEpiphanyReorientSource` only for the legacy launch response.
|
||||
- Generic job launch now converts protocol `ThreadEpiphanyWorkerLaunchDocument` cargo at the app-server edge before building the core `EpiphanyJobLaunchRequest`; the bridge launch builder takes a typed `EpiphanyWorkerLaunchDocument`.
|
||||
- Coordinator note rendering now consumes core CRRC/coordinator actions, pressure, and role/reorient result statuses. `ThreadEpiphany*` status/action DTOs are no longer the native shape for that prompt/text policy helper.
|
||||
- Coordinator note rendering now consumes core CRRC/coordinator actions, pressure, role/reorient result statuses, and reorient state status. `ThreadEpiphany*` status/action DTOs are no longer the native shape for that prompt/text policy helper.
|
||||
- Context and graph-query response builders now take core `EpiphanyContextParams` / `EpiphanyGraphQuery` documents. App-server read routes convert `ThreadEpiphanyContextParams` / `ThreadEpiphanyGraphQuery` at the JSON-RPC wall before invoking bridge derivation.
|
||||
- Role-result response assembly now takes core `EpiphanyRoleResultRoleId`; `ThreadEpiphanyRoleId` is reconstructed only for the legacy response payload and finding projection.
|
||||
- Distill response assembly now consumes core `EpiphanyDistillInput`; `ThreadEpiphanyDistillParams` is converted before bridge policy invocation.
|
||||
|
|
|
|||
Binary file not shown.
|
|
@ -352,7 +352,9 @@ current_status:
|
|||
Coordinator note rendering now consumes core CRRC/coordinator actions,
|
||||
pressure, and role/reorient result statuses instead of protocol
|
||||
`ThreadEpiphany*` action/status DTOs, so prompt/text policy no longer
|
||||
treats JSON-RPC enums as its native fact shape. Context and graph-query
|
||||
treats JSON-RPC enums as its native fact shape. Role-board note rendering
|
||||
now consumes the core reorient state status too; `ThreadEpiphanyReorientStateStatus`
|
||||
is response projection only, not prompt/text policy input. Context and graph-query
|
||||
response builders now receive core `EpiphanyContextParams` /
|
||||
`EpiphanyGraphQuery`; app-server read routes convert JSON-RPC request cargo
|
||||
before invoking the bridge. Role-result response assembly now takes core
|
||||
|
|
|
|||
Reference in a new issue