4 Commits

Include renames

Author	SHA1	Message	Date
ClintchizandClaude Opus 5	9ed896d2b9	docs: correct the dead-output component count from 11 to 9 ... Counted from source: the 22 remaining outputs sit in 9 components, not 11. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-08-09 10:14:28 +05:30
ClintchizandClaude Opus 5	8389d9674e	docs: rank the two size items in the work order ... Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-08-09 10:03:19 +05:30
ClintchizandClaude Opus 5	5112cc1a62	docs: measure the runtime and the generated client modules ... Adds a per-subsystem measurement of reactive.js, made by minifying it repeatedly with one subsystem removed rather than counting source bytes. This corrects the earlier audit on both figures and on the conclusion drawn from them. Component controllers are 23,722 bytes minified / 6,660 gzipped -- 30.6% of transfer, not the "about 18%" previously claimed -- and splitting them out saves 6.6 kB gzipped on a typical page, not "3-4 kB". Measured against the example app, / and /login use none of the ten controllers and /layout uses one, so most pages download and parse the lot for nothing. The larger finding is that the runtime is not where the weight is. One page parses 490,212 decoded bytes across 11 generated client modules while transferring 21,026, and the largest module is 89.8% duplicated lines: the state-restore prologue appears 162 times because client-codegen.ts inlines the sync into every peer alias of every client function. Gzip hides it on the wire, but parse cost follows decoded bytes. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-08-09 10:02:36 +05:30
ClintchizandClaude Opus 5	30d1632252	docs: a remediation plan for the framework ... Collects what this session exposed into one actionable document: the five bugs fixed in 0.8.6 and the guard protecting each, the places the model is incomplete, the smaller defects, and the delivery and dev-loop problems. Every item states the issue, the evidence, the change and a test that fails before it. Where a cause is not proven -- the dev server not picking up packages/ui edits -- the item says so and makes diagnosis step one rather than asserting a fix. Two standing conventions are written down at the top because the rest is written against them: a component owns its markup, behaviour and styles in its own .wrn file, and ui.css carries global styles only; and a test that still passes with the fix removed is measuring nothing, which is how the 0.8.5 focus trap shipped with no coverage. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-08-09 09:50:45 +05:30