1315 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
claude[bot]andSergey Matyunin	e6e80934e0	docs: review document for #293 ... Issue: #293 User-Visible: no	2026-08-24 17:35:11 +03:00
Sergey Matyunin	8eb351baa3	docs: specify resize pointer recovery ... Issue: #293 User-Visible: no	2026-08-24 17:35:11 +03:00
claude[bot]	a4ef0e2088	docs: review document for #291 ... Issue: #291 User-Visible: no	2026-08-24 14:34:43 +00:00
Sergey Matyunin	3c754729f2	docs: accept screenshots after lattice rebase ... Issue: #291 User-Visible: no	2026-08-24 17:16:23 +03:00
Sergey Matyunin	3f6338889e	test: prove lattice barrier across editor controllers ... Issue: #291 User-Visible: no	2026-08-24 17:13:28 +03:00
claude[bot]andSergey Matyunin	35ab1dc0c3	docs: review document for #291 ... Issue: #291 User-Visible: no	2026-08-24 17:13:28 +03:00
Sergey Matyunin	4ccf4a3ccc	fix: enforce exact lattice coordinates ... Issue: #291 User-Visible: yes	2026-08-24 17:13:21 +03:00
Sergey Matyunin	c8a3878568	docs: define lattice shift precision ... Issue: #291 User-Visible: no	2026-08-24 17:11:27 +03:00
claude[bot]andSergey Matyunin	0146d5787e	docs: review document for #291 ... Issue: #291 User-Visible: no	2026-08-24 17:11:27 +03:00
Sergey Matyunin	feff436942	docs: define lattice report translations ... Issue: #291 User-Visible: no	2026-08-24 17:11:27 +03:00
claude[bot]andSergey Matyunin	374081b490	docs: review document for #291 ... Issue: #291 User-Visible: no	2026-08-24 17:11:27 +03:00
Sergey Matyunin	e9bf11a8e3	docs: record optimize report decision ... Issue: #291 User-Visible: no	2026-08-24 17:11:27 +03:00
Sergey Matyunin	66193c5862	docs: add product context and rollback ... Issue: #291 User-Visible: no	2026-08-24 17:11:27 +03:00
claude[bot]andSergey Matyunin	894a4e5803	docs: review document for #291 ... Issue: #291 User-Visible: no	2026-08-24 17:11:26 +03:00
Sergey Matyunin	1d220628ff	docs: specify lattice coordinate write barrier ... Issue: #291 User-Visible: no	2026-08-24 17:11:26 +03:00
claude[bot]	52c74301f9	docs: review document for #290 ... Issue: #290 User-Visible: no	2026-08-24 14:11:02 +00:00
Sergey Matyunin	01512081db	test: enforce shared near-axis threshold source ... Issue: #290 User-Visible: no	2026-08-24 17:02:48 +03:00
claude[bot]	1245beaaf6	docs: review document for #290 ... Issue: #290 User-Visible: no	2026-08-24 14:01:23 +00:00
Sergey Matyunin	d33ae88da4	docs: accept screenshots after near-axis rebase ... Issue: #290 User-Visible: no	2026-08-24 16:33:20 +03:00
claude[bot]andSergey Matyunin	f6cb957bba	docs: review document for #290 ... Issue: #290 User-Visible: no	2026-08-24 16:30:43 +03:00
Sergey Matyunin	f44df5d05d	test: reconcile near-axis resize proof ... Issue: #290 User-Visible: no	2026-08-24 16:30:25 +03:00
claude[bot]andSergey Matyunin	6983f2b088	docs: review document for #290 ... Issue: #290 User-Visible: no	2026-08-24 16:30:25 +03:00
Sergey Matyunin	f6cf2c93ae	fix: scope near-axis resize validation ... Keep unrelated pre-existing near-axis edges from disabling exact Resize handles, make tracked single-space fixtures visible to the invariants CLI, and add the three missing mutation gates plus real-plan coverage. Issue: #290 User-Visible: no	2026-08-24 16:30:25 +03:00
Sergey Matyunin	edf8b068ed	fix: straighten near-axis wall geometry ... Issue: #290 User-Visible: yes	2026-08-24 16:30:11 +03:00
claude[bot]andSergey Matyunin	6551c5d53d	docs: review document for #290 ... Issue: #290 User-Visible: no	2026-08-24 16:29:51 +03:00
Sergey Matyunin	e102f34156	docs: add real-plan proof and rollback ... Issue: #290 User-Visible: no	2026-08-24 16:29:51 +03:00
claude[bot]andSergey Matyunin	7fd9ca0f6a	docs: review document for #290 ... Issue: #290 User-Visible: no	2026-08-24 16:29:50 +03:00
Sergey Matyunin	6e1007a363	docs: specify near-axis authoring and repair ... Issue: #290 User-Visible: no	2026-08-24 16:29:50 +03:00
claude[bot]	10fa0dc7fb	docs: review document for #288 ... Issue: #288 User-Visible: no	2026-08-24 13:14:55 +00:00
Sergey Matyunin	f2c0721a9d	docs: recapture screenshots after corridor integration ... Issue: #288 User-Visible: no	2026-08-24 16:02:03 +03:00
claude[bot]andSergey Matyunin	e8a4db7972	docs: review document for #288 ... Issue: #288 User-Visible: no	2026-08-24 15:57:49 +03:00
Sergey Matyunin	406e46ecb1	docs: recapture screenshots after fixture repair ... Issue: #288 User-Visible: no	2026-08-24 15:57:49 +03:00
claude[bot]andSergey Matyunin	4201644d33	docs: review document for #288 ... Issue: #288 User-Visible: no	2026-08-24 15:57:25 +03:00
Sergey Matyunin	17086d3cf2	fix: preserve walls beyond short junction rays ... Issue: #288 User-Visible: yes	2026-08-24 15:57:25 +03:00
claude[bot]andSergey Matyunin	74fdf2182c	docs: review document for #288 ... Issue: #288 User-Visible: no	2026-08-24 15:56:48 +03:00
Sergey Matyunin	2d8ade3b2b	docs: add risks and rollback to junction spec ... Issue: #288 User-Visible: no	2026-08-24 15:56:48 +03:00
claude[bot]andSergey Matyunin	6f67d53665	docs: review document for #288 ... Issue: #288 User-Visible: no	2026-08-24 15:56:48 +03:00
Sergey Matyunin	e333f0b2f1	docs: specify bounded multiwall corridor ... Issue: #288 User-Visible: no	2026-08-24 15:56:48 +03:00
claude[bot]	f472af88a3	docs: review document for #289 ... Issue: #289 User-Visible: no	2026-08-24 12:50:45 +00:00
Sergey Matyunin	a7618151cc	test: accept safe resize baselines ... Accepted the complete Linux artifact after visual review. Only the dark and light safe-resize handle views change intentionally; all other passing scenarios keep their prior bytes. Issue: #289 User-Visible: no Release: v1.67.0-beta.10 Baseline-Reviewed: https://github.com/Matysh/houseplan-card/actions/runs/32726613816	2026-08-24 15:31:26 +03:00
Sergey Matyunin	10ca913fad	test: keep resize smokes self-contained ... Issue: #289 User-Visible: no	2026-08-24 15:30:23 +03:00
claude[bot]andSergey Matyunin	849b3e5f76	docs: review document for #289 ... Issue: #289 User-Visible: no	2026-08-24 15:19:47 +03:00
Sergey Matyunin	bca3bfd52c	fix: prevent mixed-role walls during resize ... Issue: #289 User-Visible: yes	2026-08-24 15:19:40 +03:00
claude[bot]andSergey Matyunin	2ad20dca2b	docs: review document for #289 ... Issue: #289 User-Visible: no	2026-08-24 15:19:20 +03:00
Sergey Matyunin	0bca6dfb14	docs: add evidence and rollback to resize spec ... Issue: #289 User-Visible: no	2026-08-24 15:19:20 +03:00
claude[bot]andSergey Matyunin	8877e8c6d6	docs: review document for #289 ... Issue: #289 User-Visible: no	2026-08-24 15:19:20 +03:00
Sergey Matyunin	6a4e665d33	docs: specify mixed-role resize guard ... Issue: #289 User-Visible: no	2026-08-24 15:19:20 +03:00
Sergey Matyunin	5272287671	test: accept fixture wall key baselines ... Accepted the complete Linux artifact after visual review. Only the dark and light isometric geometry views change intentionally; 106 passing scenarios keep their prior bytes. Issue: #260 User-Visible: no Release: v1.67.0-beta.10 Baseline-Reviewed: https://github.com/Matysh/houseplan-card/actions/runs/32725286757	2026-08-24 15:13:41 +03:00
ClaudeandSergey Matyunin	c14dcecb98	test(fixtures): write the real wall key in one place ... Refresh the shared wall-key fixture contract and keep generated frontend bundles synchronized with the fingerprinted geometry fixtures. Issue: #260 User-Visible: no	2026-08-24 15:06:06 +03:00
Claude	523190d8f4	test: one thickness record must not describe two wall roles ... The continuity gate cannot see the defect from the owner's 66.json: masonry is continuous there and the record agrees with what is painted. The record itself is wrong — a partial resize left 43 steps of a former shared boundary as an exterior wall while it kept the 20 cm of that boundary, next to 30 cm exterior neighbours. Thickness followed the key, not the role of the edge. A width check would not have caught it, and I built one before throwing it away. It compares the painted body against the record, and here the two agree. On real plans it also fires where masonry is legitimately wider — columns, junction influence, abutting parallel walls: 76 to 82 steps measured against 4 expected, every case legal. A gate that needs explaining half the time is noise. The defect is expressible in a single state instead: one record whose span is partly shared and partly exterior. Nobody sets that on purpose. Roles come from the polygons — a stretch is shared when another room's edge covers it — so the check needs neither a build nor product code. Two traps found by measurement, both of which produced false positives. Count distinct rooms rather than edges: in a corner one room owns two edges, and counting edges called every exterior corner a shared boundary — 12 and 14 false positives. And do not sample the endpoints: an endpoint is a node, where a wall legitimately touches two rooms, and including them reported 95 per cent exterior on every wall abutting a shared one. Mutation coverage, stated honestly: the endpoint mutant is killed by the real-plan test. The rooms-versus-edges mutant survived — once endpoints are excluded, counting edges gives the same answer on real plans, so that choice is not load-bearing. I removed the mutant rather than ship a surviving one, and said so in the code. Issue: #287 User-Visible: no	2026-08-24 13:20:34 +03:00