BOMWiki/partmode

Why this matters The repository explicitly says no dedicated real-Chrome sheet-metal lifecycle gate exists. Current tests prove schema and kernel behavior, but not the visible base-flange and edge-flange workflow. Scope Add a small editable sheet-metal profile fixture. Drive the existing base-flange and edge-flange dialogs through real mouse and keyboard interaction. Verify edit, delete, save and reopen, and exact settlement. Keep this issue independent of the currently typed-only corner-relief, bend-table, and flat-pattern dialogs. Relevant files tests/fixtures/sheet-metal-profile.partmode.json tests/fixtures/README.md scripts/browser-smoke.ts docs/sheet-metal.md Acceptance evidence Chrome opens a real project through the visible file boundary. The visible dialog creates a base flange and one edge flange. Document and kernel revisions settle together with no browser, console, network, or CAD errors. Exact B-rep validity, expected analytic volume, and complete topology names are a

Why this matters The exact derived flat body and deterministic flat-dxf writer already exist, but neither has a normal human workflow. Scope Add a visible command that chooses an eligible base flange and dispatches sheetMetal.flatPattern.create. Present the derived body as read-only. Add a visible download action using the existing flat-dxf implementation and selected flat feature ID. Support deleting the flat pattern through the existing typed lifecycle. Keep bend-line annotations, scaling, kerf, nesting, unfold and fold, and non-90-degree bends out of scope. Relevant files src/page.html src/static/studio.js src/static/studio-v6-ui-registry.js scripts/studio-sheet-metal-flat-smoke.ts scripts/browser-smoke.ts docs/sheet-metal.md Acceptance evidence The visible command creates one read-only derived flat body. Its exact volume equals flatArea * thickness. Save and reopen reproduce the same canonical result. The downloaded DXF is byte-deterministic and passes the existing independent

Why this matters Rectangular and circular corner reliefs already have a typed lifecycle, schema validation, exact kernel execution, and tests, but they remain unavailable from the visible ribbon. Scope Add a visible command for selecting a base flange, eligible corner, and relief style. Dispatch only sheetMetal.cornerRelief.create. Show the derived relief size bendRadius + thickness as read-only evidence. Reuse the existing sheet-metal deletion route. Keep non-perpendicular reliefs and per-flange size overrides out of scope. Relevant files src/page.html src/static/studio.js src/static/studio-v6-ui-registry.js scripts/studio-sheet-metal-smoke.ts docs/sheet-metal.md Acceptance evidence An ordinary mouse and keyboard flow creates a corner-relief record without direct document mutation. The feature is inserted before dependent edge flanges. The exact volume decreases by the documented rectangular or quarter-disc amount. Canonical save and reopen preserve the relief. Invalid or duplica

Why this matters Bend tables already drive associative K-factor resolution, but users can author them only through typed operations. Scope Add a manager for 1 to 64 { thickness, bendRadius, kFactor } rows. Route changes through sheetMetal.bendTable.set and deletion through sheetMetal.bendTable.delete. Display the canonical sorted order after apply. When a table is active, make flange dialogs explain that K-factor comes from the exact matching row. Do not add gauge tables, interpolation, unit conversion, or CSV import. Relevant files src/page.html src/static/studio.js src/static/studio-v6-ui-registry.js scripts/studio-sheet-metal-smoke.ts docs/sheet-metal.md Acceptance evidence Unsorted visible input persists in canonical thickness and radius order. Editing a row associatively updates every dependent flange K-factor and bend allowance. Exact folded bodies rebuild successfully after the update. Missing row, duplicate row, and invalid value failures do not mutate the project. Deletin

Why this matters The add-in API documentation has an inline example, but contributors cannot download and load a checked-in working module. A small real example shortens the path from reading the API to making a first contribution. Scope Add examples/addins/height-tools.mjs. Make its no-argument command work on the Starter plate by resolving exactly one height parameter and updating it through api.document.transact. Return a clear error if the parameter is missing or ambiguous. Link the example and loading instructions from the add-in documentation. Exercise the real example module from the existing add-in smoke instead of duplicating its implementation inside the test. Relevant files examples/addins/height-tools.mjs docs/addin-api.md scripts/studio-addin-api-smoke.ts Acceptance evidence Loading registers the manifest but grants no document access before approval. Enabling the add-in registers one namespaced command. Running the command changes the Starter plate height through a t