Close Milestone 2 with measured evidence
This commit is contained in:
parent
fb0df5e4a1
commit
4c5773c865
10 changed files with 771 additions and 9 deletions
|
|
@ -27,6 +27,13 @@ Run the maintained 1,000-node Milestone 1 benchmark:
|
|||
make benchmark-m1
|
||||
```
|
||||
|
||||
Run the Milestone 2 agent-workflow smoke and full gates:
|
||||
|
||||
```bash
|
||||
make benchmark-m2-smoke
|
||||
make benchmark-m2
|
||||
```
|
||||
|
||||
The benchmark creates canonical sources, derived state, changesets, rendered output, and caches
|
||||
only in a disposable temporary directory. It does not read another project, self-host DocForge, or
|
||||
mutate repository content.
|
||||
|
|
@ -42,6 +49,13 @@ harness enforces operation-specific p95 ceilings and fixed zero-work counter inv
|
|||
human-readable interpretation is in
|
||||
[`docs/MILESTONE_1_BASELINE.md`](../docs/MILESTONE_1_BASELINE.md).
|
||||
|
||||
`milestone2-2026-07-29.json` is the clean-tree agent-retrieval and client-integration baseline
|
||||
captured from commit `fb0df5e4a1c591c2a84788fd4814d98550f11863`. It gates every warmup and
|
||||
sample, reconstructs complete task-context and generation-diff collections across bounded pages,
|
||||
records whether diagnostics were dropped for response budget, checks all hidden-work counters,
|
||||
and measures isolated-process peak RSS. Its interpretation is in
|
||||
[`docs/MILESTONE_2_BASELINE.md`](../docs/MILESTONE_2_BASELINE.md).
|
||||
|
||||
The generic fixture exposes whole-source scaling. It does not replace the incremental adapter
|
||||
equivalence tests and does not claim to measure a portable graph renderer, because Milestone 0 has
|
||||
no portable graph-planning or graph-rendering contract.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue