4 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
Matysh	8a97d4e30d	feat: add the House Plan sidebar panel ... Issue: #486 User-Visible: yes	2026-09-08 00:31:25 +03:00
Matyshandclaude[bot]	2c65fcec03	perf: lazy-load editor runtime ... Issue: #337 User-Visible: yes	2026-08-28 05:40:28 +00:00
Matysh	6d0fa3b819	build: stop committing the stand copy of the bundle ... Issue: #255 User-Visible: no	2026-08-23 10:15:45 +03:00