docs(v0.44): correct candidate interactiveProgramBytes to 3943 in performance qualification doc - #1268
Merged
Merged
Conversation
…formance qualification doc The B1.6 admission review (#1225 follow-up) flagged that docs/current/v0.44.0-PERFORMANCE.md stated 'candidate interactive JS bytes: 2626 versus 4096 baseline' while benchmarks/v044/evidence.json records candidate.interactiveProgramBytes = 3943 for the same fixture. 2626 traces to a stale embedded-program byte count from an earlier repair note, not the recorded evidence. State the precise metric name (interactiveProgramBytes, Part Program JSON bytes excluding diagnostic source maps) and the recorded value. Prose-only fix; evidence JSON unchanged. Refs #1225, #1150, #1155
Deploying openelement with
|
| Latest commit: |
cd3a961
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://844fe6b5.lessjs.pages.dev |
| Branch Preview URL: | https://kimi-v044-b1-6-perf-doc-trut.lessjs.pages.dev |
Contributor
|
APIError: Insufficient Balance |
15 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
1 participant
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.
Problem
The B1.6 admission review (PR #1267,
docs/evidence/2026-09-03-v044-alpha10-performance-admission-review.md) flagged a pre-existing inconsistency:docs/current/v0.44.0-PERFORMANCE.md:42stated "candidate interactive JS bytes: 2626 versus 4096 baseline" whilebenchmarks/v044/evidence.jsonrecordscandidate.interactiveProgramBytes: 3943versusbaseline.interactiveProgramBytes: 4096for the same fixture. Refs #1225; follow-up to #1150 / #1155.Owner
Implementer role under dispatch packet B1.6-followup (performance doc byte-count truth fix, defect found by #1225 review).
Before
docs/current/v0.44.0-PERFORMANCE.mdline 42 claimed candidate interactive JS bytes of 2626 versus 4096 baseline. The 2626 figure traces to a stale embedded-program byte count in an earlier agent-loop repair note (docs/evidence/v0.44.0-agent-loops/a0-001/repair-2-result.md), not to the recorded benchmark evidence.After
The line now states the precise metric name and the recorded evidence value: candidate interactive Part Program bytes (
interactiveProgramBytes, the Part Program JSON byte count excluding diagnostic source maps, pertools/benchmark-v044.ts) of 3943 versus 4096 baseline — matchingbenchmarks/v044/evidence.jsonexactly. All other numbers in the surrounding bullet list (static runtime bytes 0, transferred bytes 219, browser matrix, claim identity, live value) were re-verified againstevidence.jsonand are already correct. Evidence JSON untouched.Why-not-second-owner
This change introduces no duplicate-looking implementation; it is a prose-only correction to a documentation line so it matches the recorded evidence.
Evidence
Ran against branch
kimi/v044-b1.6-perf-doc-truth-fix, commitcd3a9611, base SHA710df689:deno task fmt:check— exit 0 (1545 files)deno task lint— exit 0 (880 files)deno task docs:truth— exit 0 (strategic+public+current+www+text+evidence+claims, release truth, version anchors, recipe parity all passed)deno task docs:check-role-neutral— exit 0deno task docs:check-public— exit 0deno task docs:check-strategy— exit 0deno task docs:check-current— exit 0deno task docs:check-claims— exit 0deno task docs:check-recipe-parity— exit 0deno task docs:check-version-anchors— exit 0deno task text-integrity:check— exit 0Scope
Packet-owned paths only:
docs/current/v0.44.0-PERFORMANCE.md(one bullet, 2 insertions / 1 deletion). No product code, no benchmark harness, no evidence JSONs edited. Nothing outside the packet was touched.Risk
None. Doc-only truth fix; no semantic, API, or evidence changes. The 3943 figure is the recorded candidate
interactiveProgramBytesinbenchmarks/v044/evidence.jsonand is what the acceptance gate (tools/check-v044-performance.ts) compares against the 4096 baseline.