Shaojin Wen 97925919ac test(managed-agent): add the FG12f MCP stream-gap gates (#14592) ... * docs(managed-agent): draft the FG12b and FG12e fault-gate designs Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com> * docs(managed-agent): correct the FG12b and FG12e designs after audit Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com> * docs(managed-agent): address the FG12b and FG12e design review * test(managed-agent): add the FG12b MCP store fault gates The eight-case ledger and a test-only faulting record store wrapper are in place and compile clean. The class is not yet green on JDK 21 + MariaDB: store-reject-settled, -releasing, -drained, -released and -reload-chain still fail. The shared fork budget re-pin (hostedForkHealthySeconds, CI fork literal, pom and workflow comments) is not done; only the roster entry is updated. * docs(managed-agent): close the remaining FG12b/e review findings * test(managed-agent): re-pin the FG12b fork budget The FG12b store-failure class is green 8/8 on JDK 21 + MariaDB (49.0 s measured). Re-pin hostedForkHealthySeconds to 4858 s, the CI fork to 5468 s, the Verify step to 102 minutes, and the job step sum to 182, with the workflow, pom and meta-test comments updated in the same diff. * test(managed-agent): harden the FG12b store fault gates Round 1 audit fixes: the settled cell asserts the dispatch_started record and zero response rows after the failed commit, reopens the stopped authority with the original operation/runtime pins, and reaches that rollback assertion under a skip-rejection mutation (red: expected dispatch_started, was settled). The released cell pins the exact owner-release path and requires two confirmed 200/released releases, with exactly one resend on the next detach. Owner/storage retention now compares the exact runtime-session/generation identity, reload-chain asserts the settled rev 2 and no duplicate chain, and the static gate is cleared in teardown. Local evidence is MariaDB 10.11, not the lane's MySQL 8.4.6. Budget: 120 s allowance for the measured 50.3 s class -> healthy 4878 s, fork 5488 s, Verify 102 minutes. * docs(managed-agent): design the FG12f stream gap gates * test(managed-agent): hold the MCP fixture call until the test releases it * style(managed-agent): format the FG12b design tables * docs(managed-agent): correct the FG12b budget provenance and release cell * test(managed-agent): drop the unused FG12c helpers from the FG12b class * style(managed-agent): realign the FG12b design tables * test(managed-agent): add the FG12f MCP stream-gap gates One MCP tool call is parked inside the stdio fixture while a client reads the Session stream, the client is cut mid-call, and the resumed client must continue the same ledger exactly once. The public route resumes with Last-Event-ID and the WebShell route with afterSequence, so a cursor that is ignored replays and reddens the union on a duplicate instead of timing out. The third case replaces the configuration while the call is held and pins that the running Session keeps its revision, its server and one contiguous stream. * docs(managed-agent): re-pin the FG12f budget to the merged base The parent branch merged main's event-stream liveness gates, which added 440 s to the shared fork's healthy sum before this class. The measurement is unchanged (104.6 s, 210 s budgeted) but the totals it lands on are now 5803 s healthy, 6403 s fork and a 117-minute Verify step. * test(managed-agent): drive the real MCP configuration route in the FG12f replacement case The third case now posts the Harness-private configuration route while the call is held, so the committed configuration generation advances to revision 2 and the released call keeps reading it; the immutable Agent-definition append it used before never reached the replace path. All three cases also pin the fixture's physical effect: one mcp.effect record and one durable proof row, so a resume that re-invokes the tool reddens even when the published completion is unchanged. * test(managed-agent): pin the FG12f replacement case to the public definition route The Harness-private configuration route requires the client id the Broker mints for the Harness session, which a Spring-created Session never exposes, so the case answered 404. The case now commits a new MCP server revision through the public definition route while the call is parked and pins that the running Session keeps revision 1, the replacement is stored once, one server start exists, and the fixture's physical append happens exactly once. * docs(managed-agent): narrow the FG12f replacement case to what it pins The case commits a new MCP server revision while the call is held; it does not replace the running Session's MCP connection. The Harness-private configuration route cannot carry that here because it requires the client id the Broker mints, which a Spring-created Session never exposes, so it answers hosted_session_not_found. The design now records runtime connection replacement as a gap instead of claiming it. * test(managed-agent): re-pin the FG12f budget to the merged-base measurement The three cases measure 121.1 s on the merged base rather than the 104.6 s they measured before it, so the class is budgeted at 2x (242 s): the healthy sum becomes 5985 s, the fork 6585 s and the Verify step stays at 120 minutes. --------- Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com> Co-authored-by: 易良 <1204183885@qq.com>		2026-10-18 18:34:21 +00:00
..
archive/managed-agent-schema	refactor(managed-agent): Consolidate server and broker sources (#14277)	2026-10-16 00:28:58 +00:00
assets	feat(managed-agent): Improve workspace selection and tool progress (#14405)	2026-10-17 10:35:25 +08:00
design	test(managed-agent): add the FG12f MCP stream-gap gates (#14592)	2026-10-18 18:34:21 +00:00
developers	fix(web-shell): delete attachments from an empty composer (#13947)	2026-10-16 18:23:26 +00:00
e2e-tests	refactor(core,cli): rename generic Gemini identifiers to Llm (#10124)	2026-08-28 03:05:49 +00:00
images
plans	refactor(managed-agent): Consolidate server and broker sources (#14277)	2026-10-16 00:28:58 +00:00
superpowers
users	feat(workflow): discover trusted ancestor workflows in local sessions (#14369)	2026-10-18 19:54:22 +08:00
verification	refactor(managed-agent): Consolidate server and broker sources (#14277)	2026-10-16 00:28:58 +00:00
_meta.ts
evaluation.md	docs(readme): simplify evaluation overview and refine trend chart (#14093)	2026-10-14 02:33:54 +00:00
evaluation.zh-CN.md	docs(readme): simplify evaluation overview and refine trend chart (#14093)	2026-10-14 02:33:54 +00:00
index.md