feat(tasks): add declarative task slices and rollout validation - #500
Open
yuecideng wants to merge 2 commits into
Open
feat(tasks): add declarative task slices and rollout validation#500yuecideng wants to merge 2 commits into
yuecideng wants to merge 2 commits into
Conversation
4 tasks
4 tasks
yuecideng
marked this pull request as ready for review
August 11, 2026 16:46
Greptile SummaryAdds fixed-seed Expert Program rollout measurement and deterministic static rollout reporting.
Confidence Score: 5/5The PR appears safe to merge with no concrete blocking or independently actionable non-blocking issues identified. The new benchmark validates artifact inputs, preserves executor failures, discards episode data, closes simulation resources, and distinguishes static framework coverage from physical acceptance.
|
| Filename | Overview |
|---|---|
| scripts/benchmark/expert_program/demo_success.py | Adds validated trial models, no-retry collection, failure-preserving aggregation, artifact generation, and live/offline CLI paths. |
| scripts/tools/expert_program_rollout_report.py | Generates the static capability and migration-size report and supports checked-in drift validation. |
| tests/benchmark/expert_program/test_demo_success.py | Covers model validation, execution lifecycle, aggregation, serialization, CLI validation, and cleanup behavior. |
| tests/benchmark/expert_program/test_demo_success_open_drawer_sim.py | Adds a slow supported-simulation gate validating successful Open Drawer artifacts through the public CLI. |
| docs/design/expert_program_rollout_report.md | Records framework coverage, checked-in integrations, migration-size metrics, and benchmark limitations. |
Flowchart
%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[CLI invocation] --> B{Run simulation?}
B -- Yes --> C[Build Gym environment]
C --> D[Reset once per fixed seed]
D --> E[Execute demo episode]
E --> F[Normalize rows and preserve failures]
F --> G[Discard episode buffer]
G --> H[Write raw trial JSON]
B -- No --> I[Load existing raw JSON]
I --> J[Validate and aggregate trials]
H --> J
J --> K[Write three-table Markdown report]
L[Static rollout-report tool] --> M[Count declared task sources]
M --> N[Render capability and migration snapshot]
N --> O{Check mode?}
O -- Yes --> P[Reject report drift]
O -- No --> Q[Write design report]
Reviews (1): Last reviewed commit: "feat(benchmark): add expert program roll..." | Re-trigger Greptile
yuecideng
changed the base branch from
feat/declarative-task-vertical-slices
to
feat/mllm-expert-program-frontend
August 11, 2026 17:47
4 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Stack
feat/mllm-expert-program-frontendConsolidation
Consolidates #499 into this layer. Scope: declarative task vertical slices and deterministic rollout validation.
Add deterministic Expert Program rollout measurement: fixed-seed execution, raw trial JSON, failure-preserving aggregation, Markdown reports, static migration-size checks, and supported-simulation gates.
Benchmark reporting distinguishes framework coverage, checked-in integrations, and physical acceptance instead of treating compilation success as task success.
Refs #471
Refs #474
Type of change
Screenshots
Not applicable.
Validation
tests/benchmark/expert_program/test_demo_success.pyandtests/scripts/tools/test_expert_program_rollout_report.pyChecklist