This draft documents the progressive U2/U3 workflow and its quality revisions. The new r0.6 design separates HTTP body completion from SSE tool-call completion on the current MiniMax route. It keeps the missing-[DONE] tool gate closed and proposes bounded, content-free evidence before any route-specific compatibility decision. The validation record retains the authorized r0.5 probe outcome: HTTP 200, tool_calls, clean EOF, returned Usage 513, zero tools.
The user approved writing this design direction. Written stage-4 review is pending; this PR does not authorize implementation, another paid request, A01, merge, or deployment.
Evidence
Before: The one-shot r0.5 probe ended incomplete_terminal; the client did not observe [DONE]. Independent assessment: /home/weichen/.local/share/agent-system-evidence/fast-slow-u3-r05-terminal-20261014/probe-result-independent-assessment.md (SHA-256 f35d1c17).
After: The r0.6 document and index resolve all local links; Documents 54d39ef is pinned by Dev 89125b8. make test-pins and make test passed locally on that combination (SELF receipts in the Dev task record). Exact-head Dev CI run 3158 passed all test, test-pg, and svc-realcombo jobs and steps (GATE).
Merge Danger
Door: Two-way. Blast Radius: Documentation. The Dev gitlink moves with this draft; the eight U3 PRs remain drafts while real A01 quality is NOT_RUN. This document changes no runtime or UI behavior.
## Summary
This draft documents the progressive U2/U3 workflow and its quality revisions. The new [r0.6 design](https://git-home.u1680832.nyat.app:30319/weichen/Agent-System-Documents/src/branch/feature/fast-slow-u2-u3-plan/docs/proposals/2026-10-14-fast-slow-u3-r06-transport-completeness-design.md) separates HTTP body completion from SSE tool-call completion on the current MiniMax route. It keeps the missing-`[DONE]` tool gate closed and proposes bounded, content-free evidence before any route-specific compatibility decision. The [validation record](https://git-home.u1680832.nyat.app:30319/weichen/Agent-System-Documents/src/branch/feature/fast-slow-u2-u3-plan/docs/reports/2026-10-13-fast-slow-u2-u3-validation.md) retains the authorized r0.5 probe outcome: HTTP 200, `tool_calls`, clean EOF, returned Usage 513, zero tools.
The user approved writing this design direction. Written stage-4 review is pending; this PR does not authorize implementation, another paid request, A01, merge, or deployment.
## Evidence
- **Before:** The one-shot r0.5 probe ended `incomplete_terminal`; the client did not observe `[DONE]`. Independent assessment: `/home/weichen/.local/share/agent-system-evidence/fast-slow-u3-r05-terminal-20261014/probe-result-independent-assessment.md` (SHA-256 `f35d1c17`).
- **After:** The r0.6 document and index resolve all local links; Documents `54d39ef` is pinned by Dev `89125b8`. `make test-pins` and `make test` passed locally on that combination (SELF receipts in the Dev task record). Exact-head Dev [CI run 3158](https://git-home.u1680832.nyat.app:30319/weichen/Agent-System-Dev/actions/runs/3158) passed all `test`, `test-pg`, and `svc-realcombo` jobs and steps (GATE).
## Merge Danger
**Door:** Two-way. **Blast Radius:** Documentation. The Dev gitlink moves with this draft; the eight U3 PRs remain drafts while real A01 quality is `NOT_RUN`. This document changes no runtime or UI behavior.
Why: make persistent activity and grounded findings reviewable before business changes.
Evidence: fixed source audit and scoped plan self-review; business and live checks remain NOT_RUN.
Impact: proposed contracts, implementation sequence, compatibility and bounded verification only.
Refs: fast-slow design r1.1, Dev feature/fast-slow-u2-u3-plan
Why: Planning-only status no longer matches the candidate, while failed model samples must remain explicit.
Evidence: Native SELF receipts and independent REPLAY reports distinguish code checks, six model cases and the failed quality/fidelity boundaries; relative links verified.
Impact: Update only this approved U2/U3 planning record and validation report; CI, merge, deployment and an extra sample remain pending.
Refs: User confirmation 2026-10-13; Dev feature-fast-slow-u2-u3-plan
Why: Make the current corrected candidate reviewable while preserving the failed model acceptance boundary.
Evidence: Native SELF receipt for exact source composition 7fd5288 is green; independent reviewer verifies Backend 6a2d85c and all fixed regressions.
Impact: Documentation only; the six failed or limited model samples remain unchanged and no merge or deployment is claimed.
Refs: Approved U2/U3 plan; pending explicit extra A01 test authorization
Why: Preserve other approved planning records and index updates.
Evidence: Exact current main fetched; no overlapping source behavior.
Impact: Retain both planning histories.
Refs: Agent-System-Dev U2/U3 delivery
Why: The model produced no admissible findings, so release and further paid work remain gated.
Evidence: Original provider calls, 42203 tokens, independent SQLite replay and strict source rejection are linked from the validation report.
Impact: Correct planning status and recommend a bounded lower-complexity test design for separate approval.
Refs: Approved U2/U3 plan r0.1; extra A01 user approval 2026-10-13
Why: Keep the latest merged candidate reviewable without turning failed model findings into a release claim.
Evidence: Exact d06792c composition, two current browser cases and independent model review are linked and source-labeled.
Impact: Documentation only; model quality gate and merge remain closed.
Refs: Approved U2/U3 task card
Why: The project and proposal indexes still said no U2/U3 implementation or experiment existed.
Evidence: Current combination, full PG backend, two HTTP browser cases and independent code review are linked with their actual statuses.
Impact: Documentation only; real-model acceptance is explicitly failed and no release is claimed.
Refs: Approved U2/U3 task card and validation report
Why: The approved extra sample ended with no valid saved findings and exhausted its per-run token threshold.
Evidence: Provider responses, strict-source rejections, Usage and independent analysis are retained; v7 has only local checks.
Impact: Define a separately approvable two-run 30000-token-per-run experiment without altering original acceptance rules or claiming model success.
Refs: Approved U2/U3 plan r0.1; independent extra A01 assessment
Why: The approved v7 sample saved two checkpoints but still missed semantic and final-result acceptance.
Evidence: Independent DB replay, provider usage reconciliation, source checks and the original failed evaluation receipt.
Impact: Preserve the exhausted one-shot boundary and keep all draft PRs unmerged.
Refs: Agent-System-Documents#95; Agent-System-Dev#512
Why: The controlled trial made one more paid provider request after rejecting a nonliteral quote.
Evidence: Independent transcript audit found a 14231-token continuation within the same child run; original receipts and failed quality verdict remain intact.
Impact: Make the authorization deviation explicit and reference a zero-paid prevention guard; no additional model run is authorized.
Refs: Agent-System-Documents#95; Agent-System-Backend#193; Agent-System-Dev#512
Why: The approved model samples showed unsupported approval claims, repeated source input and no final answer before the run budget stopped.
Evidence: The design cites the preserved A01 provider usage, persisted findings and independent sample audit without claiming new model validation.
Impact: Define a reviewable source, claim and final-reserve revision while keeping code, paid trials and merge gated.
Refs: Agent-System-Documents#95; Agent-System-Dev#512
Why: The approved written design needs testable work items before changing model behavior or spending another sample.
Evidence: The plan maps all three design duties to existing code seams, RED-to-GREEN checks, a fixed combination gate and a separately authorized real-model exit.
Impact: Record stage-five review material without modifying product code, using paid models, or opening merge gates.
Refs: Agent-System-Documents#95; Agent-System-Dev#512
Why: Hiding a tool declaration alone does not prevent a model from calling a tool already in the runtime registry.
Evidence: The agent-native loop continues after tool errors; the plan now requires a local stop latch before any later provider call.
Impact: Clarify the zero-paid test and implementation boundary without changing the approved design or authorizing model usage.
Refs: Agent-System-Documents#95; Agent-System-Dev#512
Why: A provider may report prompt and completion tokens while leaving totalTokens zero; the reserve must not treat that usage as free.
Evidence: Existing budgetedStream falls back to prompt plus completion, while subRun usage accounting currently does not; the plan adds a focused regression.
Impact: Clarify the reviewed implementation scope without changing product code or authorizing a model sample.
Refs: Agent-System-Documents#95; Agent-System-Dev#512
Why: The existing browser fixture parses the trailing source index that the approved source-once layout removes.
Evidence: A zero-paid parser probe matched the old format and rejected the planned inline format; the plan now owns a failing fixture test and adaptation.
Impact: Preserve real HTTP browser coverage without changing product contracts or model acceptance.
Refs: Agent-System-Documents#95; Agent-System-Dev#512
Why: The design and implementation plan were approved while the previous report still described them as pending.
Evidence: git diff --check; Backend, UI and affected Frontend tests recorded as SELF with their component SHAs.
Impact: The report distinguishes the new mechanism candidate from the failed paid v7 sample and keeps model QA NOT_RUN.
Refs: U3 quality revision r0.2
Why: The resolved cross-component candidate now has actual HTTP/browser evidence and one diagnosed fixture failure.
Evidence: Task-card SELF sync and browser receipts, including manifest verification and two passing Playwright cases.
Impact: The report keeps model quality NOT_RUN for r0.2 and the older paid failure unchanged.
Refs: U3 quality revision r0.2
Why: The merged candidate now has complete local combination and task-owned PostgreSQL results.
Evidence: Imported SELF receipts for make test && make build and Backend runmgr/cardsvc/store on isolated PostgreSQL.
Impact: The report keeps final exact-head and model acceptance gates pending for the next candidate SHA.
Refs: U3 quality revision r0.2
Why: The final zero-paid candidate incorporates three review findings and fresh browser/PostgreSQL evidence.
Evidence: Backend RED-to-GREEN regressions; task-card SELF receipts for HTTP/browser and isolated PostgreSQL reruns.
Impact: Real-model quality remains NOT_RUN and still blocks merge.
Refs: U3 quality revision r0.2
weichen
changed title from [WIP] Record the U2/U3 implementation and failed model acceptance to [WIP] Record U2/U3 delivery and the U3 quality revision2026-10-13 11:03:11 +00:00
Why: The one authorized trial produced useful stages and a final answer but also an unsupported phase-membership claim.
Evidence: Fixed SQLite, provider and result hashes; tool-imported SELF receipts; independent read-only source-by-source replay.
Impact: Keep U3 quality FAIL, six PRs draft and the new diagnostic fix separate from the paid sample.
Refs: U3 quality implementation plan r0.2, Task 6
Why: The failed model sample must remain reviewable beyond the task-owned temporary directory.
Evidence: Eighteen copied files rehashed and checked at restrictive modes; protected route key was not copied.
Impact: The report points to a durable, access-restricted archive without upgrading the failed quality verdict.
Refs: U3 r0.2 A01 independent replay
Why: The approved r0.2 A01 produced an unsupported set-membership claim despite an explicit prompt warning.
Evidence: Independent read-only replay of the fixed A01 result, source text, persisted checkpoints and final card; spec self-review and link checks.
Impact: Defines a conservative no-extra-model-call proposal for review, without authorizing semantic implementation or another paid sample.
Refs: U3 r0.2 A01 quality FAIL, user-approved r0.3 design direction
Why: The approved r0.3 design needs a reviewable implementation and validation path.
Evidence: Design approval recorded in the task conversation; plan self-reviewed against the spec and current Core/Backend interfaces; git diff --cached --check passed.
Impact: Documentation only; semantic code and paid model trials remain unapproved.
Refs: Dev task feature/fast-slow-u2-u3-plan; Documents PR #95
Why: The user approved zero-paid execution of the written plan.
Evidence: Approval response on 2026-10-13; git diff --cached --check passed.
Impact: Document status only; new paid A01 remains separately gated.
Refs: Documents PR #95; Dev task feature/fast-slow-u2-u3-plan
Why: The new evidence-bound checkpoint candidate needs a reviewable account of what the local and browser gates prove.
Evidence: Tool-imported Dev combination, isolated PostgreSQL and real HTTP fake-stream browser receipts; previous knip failure retained.
Impact: Documentation only; r0.2 model quality remains FAIL and r0.3 paid A01 remains NOT_RUN.
Refs: Dev task feature/fast-slow-u2-u3-plan; Documents PR #95
Why: The first r0.3 code review found three unsafe inference paths despite green mechanism tests.
Evidence: Reviewer's read-only replay, Backend RED→GREEN counterexamples, isolated PostgreSQL and task-owned HTTP browser receipts are identified separately.
Impact: Keep the old review failure and new fix candidate traceable; real-model quality stays NOT_RUN.
Refs: Dev task feature/fast-slow-u2-u3-plan; Documents PR #95
Why: Repeated independent semantic review required a conservative final source and analysis boundary.
Evidence: Backend 5f53f80 independent replay found no remaining Critical/Important; task-owned PostgreSQL and HTTP browser receipts identify separate fixed SHAs.
Impact: Code mechanism review is PASS, while real-model quality, exact Dev combination and platform gates remain pending.
Refs: Dev task feature/fast-slow-u2-u3-plan; Documents PR #95
Why: Reviewers need the exact successful combination and a clear distinction between prepared evaluation code and paid authorization.
Evidence: Dev 6f91ca9 make test/build SELF receipt; Backend 5f83454 label regression RED→GREEN.
Impact: Documentation only; real-model quality remains NOT_RUN and six PRs stay drafts.
Refs: Dev task feature/fast-slow-u2-u3-plan; Documents PR #95
weichen
changed title from [WIP] Record U2/U3 delivery and the U3 quality revision to [WIP] Record U3 evidence design, implementation, and validation2026-10-13 18:20:36 +00:00
Why: the approved r0.3 A01 sample failed before any useful background checkpoint.
Evidence: preserved A01 receipt, SQLite and provider records; offline SSE and retrieval replay; local links and diff checks pass.
Impact: design and validation record only; no behavior, budget, or model route changes.
Refs: docs/proposals/2026-10-14-fast-slow-u3-r04-reliable-first-checkpoint-design.md; docs/reports/2026-10-13-fast-slow-u2-u3-validation.md
weichen
changed title from [WIP] Record U3 evidence design, implementation, and validation to [WIP] Document U3 staged findings and r0.4 recovery design2026-10-14 01:42:04 +00:00
Why: turn the approved recovery design into reviewable cross-component implementation and validation steps.
Evidence: six tasks and thirty steps mapped to the spec; review-focus tests, local links and diff checks pass.
Impact: plan and validation status only; code and paid model execution remain NOT_RUN.
Refs: docs/proposals/2026-10-14-fast-slow-u3-r04-reliable-first-checkpoint-implementation-plan.md; docs/reports/2026-10-13-fast-slow-u2-u3-validation.md
weichen
changed title from [WIP] Document U3 staged findings and r0.4 recovery design to [WIP] Document U3 r0.4 recovery design and plan2026-10-14 01:57:15 +00:00
Why: Preserve approved proposal status updates while retaining the U3 r0.4 design and implementation plan.
Evidence: The two lines of work touch disjoint document paths; merge status is clean and the parent Dev composition will be revalidated.
Impact: Documentation only; no model or runtime behavior change.
Refs: Dev U3 r0.4 Task 6 synchronization
Why: The single authorized real-model trial produced no persisted checkpoint or final result and exposed an unsupported fast-channel inference.
Evidence: Independent read-only assessment SHA 2ac373ed66d47aaa9cdb699d3bf77eb8a515d46956ee0321b70cc0230d79b667; restricted 20-file source-verified archive manifest SHA 881991dcab17ad2539f8b24332f962e3505ab2f248662f58283fe08daa179077.
Impact: Preserve the FAIL decision, returned-versus-persisted Usage discrepancy, resource stop, and next design gate without rewriting the sample.
Refs: U3 r0.4 plan; Dev task feature-fast-slow-u2-u3-plan
Why: The authorized r0.4 A01 exposed an unobserved stream terminator and an unsupported numeric relationship in the immediate reply.
Evidence: Independent A01 assessment and fixed-head Backend/Dev CI are linked from the design and task record; relative Markdown links and git diff --check pass.
Impact: Propose content-free terminal diagnostics and a source-safe host acknowledgement while retaining strict tool rejection and the original A01 quality gate. This document grants no implementation or model budget.
Refs: U3 r0.4 validation; Dev task feature-fast-slow-u2-u3-plan
weichen
changed title from [WIP] Document U3 r0.4 recovery design and plan to [WIP] Document U3 r0.5 safe terminal and fast feedback2026-10-14 06:37:17 +00:00
Why: The approved r0.5 design needs an auditable zero-paid execution sequence after the failed r0.4 model sample.
Evidence: The approved design object is Documents 0d473fe; current source seams, file ownership, relative links, and whitespace were checked before drafting this plan.
Impact: Add five test-first work units and explicit stage, budget, privacy, and stop gates. This commit contains no product implementation or model call.
Refs: U3 r0.5 design; Dev task feature-fast-slow-u2-u3-plan
weichen
changed title from [WIP] Document U3 r0.5 safe terminal and fast feedback to [WIP] Plan U3 r0.5 safe terminal and fast feedback2026-10-14 07:26:40 +00:00
Why: The task needs an auditable distinction between the new mechanism checks and the failed r0.4 model sample.
Evidence: Dev task receipts for component tests, browser replay, isolated PostgreSQL, and composed build.
Impact: Documents the candidate and leaves r0.5 model quality as NOT_RUN.
Refs: U3 r0.5 implementation plan Task 5
Why: The merged index predates the approved r0.5 implementation and standalone CI applicability check.
Evidence: Dev task card and isolated component/combination receipts; Documents origin/main merged at 9062445.
Impact: Corrects review status and marks absent Frontend/Documents workflows N/A.
Refs: U3 r0.5 implementation plan Task 5
Why: The review found a provider-label leak and incomplete browser evidence for the candidate.
Evidence: Sentinel RED/GREEN, twelve exact-pin browser cases, and isolated PG/Redis receipts.
Impact: Distinguishes the reviewed old object from the fixed zero-paid candidate; model quality stays NOT_RUN.
Refs: U3 r0.5 independent review
Why: Preserve the authorized one-shot diagnostic and its limits in the durable validation record.
Evidence: Dev run 3136; SELF terminal receipt 6b013965; independent result assessment f35d1c17.
Impact: Documentation only; tool execution gate and A01 quality status stay unchanged.
Refs: Agent-System-Dev task feature/fast-slow-u2-u3-plan
Why: The authorized small tool stream again lacked an observed DONE marker, leaving transport and provider causes unresolved.
Evidence: U3 r0.5 terminal receipt 6b013965 and independent assessment f35d1c17; local links and diff checks passed.
Impact: Design only; the missing-DONE tool gate, runtime behavior, and paid resource boundary remain unchanged.
Refs: Agent-System-Dev feature/fast-slow-u2-u3-plan; Documents PR #95
weichen
changed title from [WIP] Plan U3 r0.5 safe terminal and fast feedback to [WIP] Document U3 r0.6 route-scoped terminal evidence2026-10-14 13:15:58 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
This draft documents the progressive U2/U3 workflow and its quality revisions. The new r0.6 design separates HTTP body completion from SSE tool-call completion on the current MiniMax route. It keeps the missing-
[DONE]tool gate closed and proposes bounded, content-free evidence before any route-specific compatibility decision. The validation record retains the authorized r0.5 probe outcome: HTTP 200,tool_calls, clean EOF, returned Usage 513, zero tools.The user approved writing this design direction. Written stage-4 review is pending; this PR does not authorize implementation, another paid request, A01, merge, or deployment.
Evidence
incomplete_terminal; the client did not observe[DONE]. Independent assessment:/home/weichen/.local/share/agent-system-evidence/fast-slow-u3-r05-terminal-20261014/probe-result-independent-assessment.md(SHA-256f35d1c17).54d39efis pinned by Dev89125b8.make test-pinsandmake testpassed locally on that combination (SELF receipts in the Dev task record). Exact-head Dev CI run 3158 passed alltest,test-pg, andsvc-realcombojobs and steps (GATE).Merge Danger
Door: Two-way. Blast Radius: Documentation. The Dev gitlink moves with this draft; the eight U3 PRs remain drafts while real A01 quality is
NOT_RUN. This document changes no runtime or UI behavior.[WIP] Record the U2/U3 implementation and failed model acceptanceto [WIP] Record U2/U3 delivery and the U3 quality revision[WIP] Record U2/U3 delivery and the U3 quality revisionto [WIP] Record U3 evidence design, implementation, and validation[WIP] Record U3 evidence design, implementation, and validationto [WIP] Document U3 staged findings and r0.4 recovery design[WIP] Document U3 staged findings and r0.4 recovery designto [WIP] Document U3 r0.4 recovery design and plan[WIP] Document U3 r0.4 recovery design and planto [WIP] Document U3 r0.5 safe terminal and fast feedback[WIP] Document U3 r0.5 safe terminal and fast feedbackto [WIP] Plan U3 r0.5 safe terminal and fast feedback[WIP] Plan U3 r0.5 safe terminal and fast feedbackto [WIP] Document U3 r0.6 route-scoped terminal evidence