Render the plot forecast receipt and persona binding control in Bevy. master
The selected plot row's WHAT HAPPENS NEXT area now states the 2026-08-02 disclosure: the expanded cost read (ActionCost::player_label) replaces the compact "cost {label}" line, the one shared PlotForecast::money_sentence renders with each earned account as an activatable link that focuses its exact ACCOUNTS object (unearned accounts stay plain text), each PredictedDelta prints its axis and exact numeric range beside a read-only DIM bar on a GUNMETAL track scaled against the fixed 50-point practical axis range, the derived unlock fact prints in bone, and the signature slot is omitted entirely with no dangling separator. Missing-persona legality renders as the FRONTING IDENTITY control instead of a blocked sentence: recognized-first identity choices with exactly one current row and DIM alternatives, unrecognized identities marked as introductions naming the exposure, clicks rebinding the row's StartPlot persona parameter as pure frontend state the executor still revalidates, an empty-but-required state under the AMBER_DIM requirement outline naming what is missing, and the exact PERSONAS-owned ADD NEW {TYPE} PERSONA creation rows dispatched in place, after which the recomputed row keeps the decision selected with the new identity as its default binding. A persona-less StartPlot can never dispatch from Bevy, and the unified blocked string remains untouched for terminal and agent surfaces. Core changes are read-only projection data only: MoneyMove carries the earned account id behind each label and plot_account_id opens to pub(crate). Eight structure tests pin the exact Marcus debt-settled numbers, the linked money sentence, bar widths, the omitted signature slot, the control's selection and emphasis states, account-link focus, persona rebinding through the unchanged confirm law, and creation-row dispatch. current-build.md's line count refreshes because this change pushed the tracked drift past the corpus gate's 15% tolerance. Defense: operations-workspace.md's "The persona binding control" section and detail-order item 6 (reopened 2026-08-02) require the receipt to disclose typed predicted deltas as numbers with small labeled bars, name each account focusable to its exact ACCOUNTS object where earned, and present a satisfiable select-or-create control dispatching the same bound PERSONAS commands instead of a blocked: dead end; the liturgical constitution's control canon binds the rendering itself - bars reinforce while the number carries the meaning, a named world object inside a receipt is an activatable link to its owning view, requirement emphasis draws on the amber tiers while crimson stays danger-only, and every control renders renderer-neutral projection data that stays fully legible as terminal text and agent commands.