Repository navigation
⚡ #543 remeasure weights and performance, then deliver #587
Description
Parent quest: #543
Purpose
Integrate the completed PC, CT, and IE migrations, prove the frozen matrix, measure the result under the current runtime topology, and deliver #543.
Matrix audit
- Account for every PC, CT, IE, and DT row exactly once.
- Confirm all DT rows remain focused TypeScript command tests pending Add in-process
xmdcommand execution to Markdown tests #581. - Confirm no row in these four suites is labeled a permanent OS-process claim.
- Confirm launchers contain no row assertions and TestResult is unchanged.
Focused feedback
Run the three launchers, the four retained suites, and testing-execution-host.test.ts under Deno; run the three launchers under Node and Bun. Create the feedback commit as soon as this frozen evidence and all required mutation probes pass.
Performance evidence
- Repeat three alternating local
/usr/bin/time -p deno task testsamples on clean before/after worktrees and compare medians. - From exact-commit hosted runs, record every Deno shard Test window, their sum, and the slowest shard before/after.
- Slowest-shard change is an observation, not a gate.
Weights and partition
- Dispatch the hosted weight-measurement workflow against the implementation ref.
- Commit the generated
test-weights.jsonartifact byte-for-byte with full provenance. - Recompute Deno, Node, and Bun partitions; record file counts, serial totals, affected file weights, fallback set, and every predicted shard total.
- Prove pairwise disjointness and exact applicable-corpus union with the existing discovery/weight/shard/workflow regressions.
- Apply the specification's five-run fixed-head calibration rule if any installed runtime count no longer qualifies.
Acceptance
- Frozen matrix, focused evidence, mutation records, local timing, hosted Deno spend/slowest shard, generated weights, and partition evidence are durable in the PR or linked issues.
- Required CI is green under the authoritative workflow.
- 🗺️ Quest: Prove document behavior through <Execution>, and spawn xmd only for process claims #543 can close without waiting for Add in-process
xmdcommand execution to Markdown tests #581.
Activity
taras commentedon Aug 25, 2026
Delivered: PR #606 merged at e425ee4 (feedback commit 73b73ed). Fresh test-weights.json (run 32873071843 at 170a021, byte-for-byte), shard counts calibrated to 9/5/2 by the five-consecutive-run rule (7/3 and 8/4 missed at the committed weights; run 32892093466 attempts 1–5 all pass), final hosted after-measurement recorded against the #582 baseline (slowest Deno shard 330s → 270s), final partitions disjoint with exact union and an empty fallback set. Matrix audit, focused three-runtime evidence, and alternating local medians are in the PR body and issue-587-implementor-handoff.md.
taras commentedon Aug 25, 2026
Planner closure — PASS
#587 is complete on
mainat merge commite425ee42ebc024ff7a092d0fcbbe769436a346ee(PR #606; reviewed head73b73edef0b3090928410b6ea0ea9af7512f0622).xmdcommand execution to Markdown tests #581, and no row is classified as a permanent OS-process claim.TestResultare unchanged.test-weights.jsonis byte-identical to hosted measurement artifact run 32873071843, with an empty fallback set.#587 frozen acceptance and delivery evidence are satisfied.