1.6 KiB
Sweep 015 Direct Mock Partial Closure Report
Date: 2026-04-20 Plan:
2026-04-20-sweep-015-direct-mock-partial-closure-plan.md
Scope
This closure only handled the single remaining full direct mock partial:
sweep-015-scene / 任务报表
It did not modify generated skill packages, generator/analyzer code, official board state, browser runtime, network access, or production systems.
Root Cause
sweep-015-scene generated script applies this business filter:
row.status == 5
The full direct mock runner's generic fake row did not include status = 5, so mock data was filtered out and the artifact became partial with zero rows.
This was a mock fixture contract gap, not a generated skill or generator defect.
Change
Updated the direct mock runner fake row to include:
status: 5
Result
Full direct mock execution now reports:
| Status | Count |
|---|---|
direct-mock-pass |
102 |
direct-mock-partial |
0 |
direct-mock-fail |
0 |
By archetype:
| Archetype | Pass |
|---|---|
paginated_enrichment |
51 |
host_bridge_workflow |
26 |
local_doc_pipeline |
6 |
multi_mode_request |
10 |
single_request_enrichment |
5 |
page_state_eval |
2 |
multi_endpoint_inventory |
2 |
Verification
Command:
node tests/generated_scene_full_direct_mock_runner.js
Output asset:
tests/fixtures/generated_scene/scene_skill_102_full_direct_mock_execution_2026-04-20.json
Stop Statement
This plan stops here. The next bounded stage can be pseudo-production batch selection, but that is not started under this closure.