FS-116: coordinated DXF drawing packages

[michaelfutol]

What changed

• replaces the partial current-floor DXF path with a coordinated multi-floor drawing package
• exports layout and tributary plans for every floor plus foundation or base reactions
• adds synchronized column, beam, slab, and footing/reaction schedules, load summary, and preliminary BOQ tables
• preserves FT structural layers, CENTER2 grids, HIDDEN2 corner framing, floor-aware member state, and local-date filenames
• adds package-completeness and layer regression coverage

Why

The former exporter skipped floors, cantilevers, foundation content, schedules, and BOQ data and bypassed corrected floor-aware geometry. Browser URL cleanup could also race the download.

Validation

• node v3/tools/check-fs.js --no-browser
• node v3/tools/check-fs.js
• Playwright DXF-button download against the default two-floor model
• Playwright DXF-button download against FutolStructure_2026-7-03 - Olango.fstr
• generated DXF audit: valid EOF, no NaN/undefined coordinates, governed column/beam/slab/grid/text layers

Scope

This remains preliminary drafting/quantity output. It does not claim final design, BBS, or permit-ready documents.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
futolstructure	Ready	Preview, Comment	Jul 12, 2026 10:55pm

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: ad98f879f9

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Scope base reaction rows to the foundation floor

When exporting in base-reactions-only mode while an upper floor is selected, this unscoped getBaseReactionRows() call reads state.floors[state.currentFloorIndex] and filters through isFoundationColumnForPlan, so columns deleted or inactive on the selected story can be omitted from the BASE REACTION SCHEDULE even though the foundation/base reaction plan is drawn for state.floors[0]. The schedule should be generated under the same foundation-floor context used by drawFoundationPlanPackage.

Useful? React with 👍 / 👎.