docs(harness): mark Phase 1 complete + estimate-vs-actual retrospective - #3658
Merged
PattaraS merged 1 commit intoJul 31, 2026
Merged
Conversation
…ospective
Phase 1 of the modular native-harness registry refactor landed (10 PRs,
2026-07-28 → 07-31). Bring the design doc in line with what actually shipped:
- Status header, Phase 1 subtotal, effort summary, and bottom line updated from
forward-looking ('1.1–1.3 in review') to Phase 1 complete / Phase 2 next.
- Ledger: 1.8 (omnigent-ai#3648) landed; 1.4 marked descoped (with rationale); the 1.7
opencode-e2e follow-up (omnigent-ai#3656) recorded; per-PR merge dates added.
- Calibration rewritten as a Phase 1 retrospective: estimate (~20–29 eng-days)
vs. actual (10 PRs / 4 calendar days), the real cost centers (test-shape churn
+ review-caught behavior bugs, enumerated per PR), the correct runner re-scope,
the two intentional behavior deltas (qwen label, antigravity relay), and the
recurring uv.lock / full-suite-only-flake operational friction.
Doc-only; no code change.
Co-authored-by: Isaac
Signed-off-by: Pat Sukprasert <pattara.sk127@gmail.com>
Contributor
|
🏷️ Doc impact: The change only updates an internal design proposal doc ( Auto-classified on merge. Set the label manually before merging to override. · run |
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.
Related issue
N/A — housekeeping for the modular native-harness registry workstream (
designs/harness-modular-registry-proposal.md).Summary
Phase 1 of the refactor is complete (10 PRs, 2026-07-28 → 07-31). The design doc had accumulated drift over the stack — still reading "Phase 0 landed, 1.1–1.3 in review" and projecting ~2.5–3.5 calendar months. This brings it in line with what actually shipped:
uv.lock-rewrite / full-suite-only-flake operational friction.The plan tables (scope/dependencies) are left as the stable target; only the status, ledger, and estimate-vs-actual narrative changed.
Test Plan
Doc-only.
pre-commit(whitespace/newline/merge-conflict/line-ending checks) passes.Demo
N/A — documentation.
Type of change
Test coverage
Coverage notes
Documentation-only change to a design doc; no code paths affected, so no test coverage applies.