Add the package-local browser tracer over the Phase 4b protocol boundary as a
new Live console mode in the standalone devtool.
Surfaces derive only from canonical PRP events and the shared reducer: live
transcript and composer, same-turn steering with stale-turn recovery, three
distinct interrupt races, inline runtime request cards, capability-gated goal
controls, parent/child lineage, reconnect, refresh, replay, and a redacted
protocol inspector.
Add a deterministic scripted driver and eleven demo chats behind the same demo
server routes the real Codex driver uses, so every protocol state is reachable
without a provider account and PAPERCLIP_PHASE4B_DRIVER=codex swaps in the real
session.
Adapt shadcn/ui and Vercel AI Elements source with zero new runtime
dependencies, and extend the boundary check to keep it that way.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
UX gate PAP-16832: live-console interaction map for all spec 29.1
surfaces, shadcn/AI Elements adapt/reject decision record with a
zero-new-runtime-dependency rule, keyboard/accessibility acceptance
criteria, token additions, annotated 1440x900 and 390x844 mockups,
and OKF journal/index updates.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Bind Codex reconciliation to the persisted active turn and retain semantic-result and terminal fingerprints across transport recovery. Align Phase 4 docs with content-idempotent retry behavior.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Enforce loopback/same-origin transport and bounded browser resources, frame harness output before allocation, and reconcile terminal state from runner-owned facts.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Add the production-direction Cargo workspace, make the Rust tracer the default Phase 0 path, and enforce shared-fixture parity with the TypeScript reference. Extend standalone boundary checks and record the correction in the implementation plan and OKF journal.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
UX review PAP-16714 findings applied:
- Resume line now normatively precedes the response control (UX doc 2.3),
matching OPX-4/OPX-F3 DOM-order gates and the doc's own acceptance
criterion 4; the PAP-16712 mockup footer placement is noted as
non-normative.
- 18.12.13 screenshot matrix gains the accepted happy path
(completion_contract_satisfied -> Done, four layers in agreement).
Co-Authored-By: Paperclip <noreply@paperclip.ing>
Phase 4 of the 18.3 status authority track (PAP-16713). Adds spec section
18.12, the binding contract between the arbitration/attention contracts
(18.3-18.11) and the approved operator UX reference.
- Ten presentation invariants (OPX-1..OPX-10) stated as testable criteria.
- Persistence prerequisites: attention_requests, attention_request_attempts,
and attention_budgets, which 18.3.1 described but 18.7 never defined, plus
the index the board summary needs.
- Read models: NativeOutcomeLayers carries all four authority layers as one
embedded object, plus StatusDecisionView, RunFinalizationView,
AttentionRequestView, and the compact list/board summaries.
- livePathIntegrity makes "every waiting state names an owner" a server
assertion rather than a UI convention.
- Adds the missing attention read routes; specifies envelope asOf,
authorization, and a whitelist redaction table.
- Client derivation rules, component data contracts, a requirement ->
field -> component -> gate coverage matrix, degraded/legacy/error
renderings, and gates OPX-F1..OPX-F11.
pnpm check:runner-phase4-spec enforces reason-code copy totality, read-model
coverage, gate reachability, invariant enforcement, route agreement,
backing persistence, and the claim copy law across both documents.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Extract the board-approved PAP-16712 UX design into
spec/paperclip-runner-status-attention-ux.md: layered outcome vocabulary
(turn/run/claim/status), OutcomeChipRow / StatusDecisionCard /
AttentionRequestCard / FinalizationErrorCard, five desktop board flows,
the v1 reason-code copy table, and token-system notes.
Core spec changes are pointers only: 18.3 names the reference doc as the
normative Phase 4 presentation, and the 18.11 UI-surfaces row now requires
the Phase 4 read models to carry every field that design renders.
Co-Authored-By: Paperclip <noreply@paperclip.ing>
