5 Commits

Include renames

Author	SHA1	Message	Date
Claude	1ef35883e0	Ask a foreign manifest whether it can be loaded, not how it was wired ... The performance harness runs the candidate's benchmark against a baseline checkout, so the candidate's validator reads a manifest built by an older commit. #535 put a rule about the CURRENT build into that shared validator — the panel graph must not contain the card facade — and it is false of every build before #535 by construction. The candidate then refused to load any older baseline: all nine performance profiles went red at once on the same step, the stable release gate withheld `houseplan-card.js` from the published v1.75.0, and none of it was about speed. assertBundleManifest now answers only the loader's question: paths exist, nothing is duplicated, graphs reference listed assets, sizes add up. The topology of the current build moves to assertOwnBundleTopology, called from bundle-sync.mjs, which materializes our own dist, and from the unit test that reads dist/houseplan-assets.json. Neither ever looks at a foreign tree. Reproduced end to end, not only in a unit: a v1.74.0 worktree built with its own code, then `node demo/benchmark_large_house.mjs --target-root=<baseline>` from this tree. Before the change it stops with «initial panel graph must contain its own stable entry only»; after it, the profile is captured. Issue: #537 User-Visible: no	2026-09-12 09:39:05 +03:00
Claudeandclaude[bot]	063de0eef4	Let the panel reach the card by its hashed name, not by the one address without a version ... The sidebar page could serve a previous card for hours. It imported the card through the stable facade, `./houseplan-card.js` — a relative specifier, and relative resolution does not inherit a query. A dashboard reaches the same file as `houseplan-card.js?v=1.74.0`, so an upgrade changes its URL and the browser must refetch. The panel always asked for the same address, and entries are served with no Cache-Control at all — only ETag and Last-Modified — so the browser applies heuristic freshness and may answer from cache without asking. A stale 1164-byte loader names a stale chunk, chunks are immutable for a year, and the panel then ran a previous card against the current backend without a single error. The version banner was telling the truth; reloading could not help, because the address never changed. Rollup already emits the right edge: the panel's side-effect import points straight at the shared implementation. The rewrite in entryFallbackPlugin replaced it with the facade for a fallback that the hashed name gives anyway — and better: a chunk the manifest no longer serves now raises the panel's own "House Plan was updated" notice instead of silently working on old code. Two #486 assertions change meaning and are rewritten, not adjusted: the panel no longer routes through the facade, and its initial graph no longer contains it. The invariant they defended — the panel reuses the exact card graph, never a second copy — is now stated over the implementation, and a new test pins that no built entry reaches the card by an address without a version. Issue: #535 User-Visible: yes	2026-09-11 22:12:11 +00:00
Matysh	8a97d4e30d	feat: add the House Plan sidebar panel ... Issue: #486 User-Visible: yes	2026-09-08 00:31:25 +03:00
Codexandclaude[bot]	78c6020747	fix: lazy delivery survives flaky networks and stale caches (#353) ... Network failure of the editor runtime is no longer terminal: the loader re-arms to idle and the next explicit press starts a fresh cycle, while a fingerprint mismatch on either attempt stays terminal. The toast now says what actually helps — retry advice for the network, refresh advice for a foreign build — via one shared lazyLoadFailureMessage helper (new i18n key editor.retry_advice in en/ru/de). The field smoke caught a second, deeper bug on the way: Chromium records a FAILED module in the page module map permanently, so retrying the same URL (even the cache-busted one) never touched the network again. Every retry now carries a per-cycle nonce and becomes a genuinely new module request. A proxy-cached stale entry no longer kills the card silently: the entry facade is rewritten at build time from a static re-export into a top-level `try{await import(...)}catch{...}` — importers keep the happy-path guarantee (await import(entry) still resolves only after customElements.define), and the catch defines a fallback element with a localized "reload the page" panel. Content-hashed chunks are served with `public, max-age=31536000, immutable`, and verifyBundleTree now fails on orphan chunks that the manifest does not name. Proofs: loader units for re-arm/terminality/toast wording + an AST check that both loaders forward the terminality flag; smoke_entry_stale (en/ru) against a tree without the main chunk; smoke_lazy_editor_chunk extended — second press after network failure now really opens the editor; pytest for the immutable header; orphan-tree unit; five new registry mutants. TESTING.md budget line updated to the #352 ceiling alongside. Issue: #353 User-Visible: yes	2026-08-28 14:32:08 +00:00
Matyshandclaude[bot]	2c65fcec03	perf: lazy-load editor runtime ... Issue: #337 User-Visible: yes	2026-08-28 05:40:28 +00:00