feat: designer-facing card flags, deduped property chips, readable auto-fit, zone geometry

[timurbazhirov]

Five wove-owned fixes from the workflow designer UX review (SOF-8024, mat3ra/workflow-designer#12). Each stands alone.

1. Flowchart IDs hidden behind showDeveloperInfo (default off)

CardHeader printed the flowchart UUID under every unit and subworkflow card. It identifies nothing to a person reading a card, and it consumes the entire subheader — it was the single most repeated element on the designer screen. Now off by default; hosts expose it behind a "developer info" toggle.

2. showStatus gates the run-status badge

Status belongs to a job's execution. In a designer, every unit is perpetually "idle", so the badge is pure noise. Threaded through UnitCard, WorkflowUnitCard, WorkflowUnitsFlowchart, UnitsFlowchartContainer and the react-flow NodeData so a designer can switch it off while job views keep it (default stays true — no change for existing consumers).

3. Property chips deduped and humanized

Several units in one subworkflow commonly report the same property (an scf and an nscf step both yield fermi_energy), and the subworkflow lists every occurrence — so the same chip rendered twice with nothing to tell the copies apart. Now deduped, with total_energy → "Total energy" and the raw key kept as the tooltip.

4. Auto-fit clamped to a readable zoom

fitView shrank long workflows until unit names were illegible — a ten-unit subworkflow landed around 6px type, on a canvas that was mostly empty grid anyway. Auto-fit now stops at a legible scale and lets the result scroll.

5. Brillouin zone geometry passed to the injected component

This addresses the standing TODO in context/utils.tsx:

Do not hardcode web-app public paths here (/images/brillouin_zone/...) … so wove stays path-agnostic.

imgSrc points at an asset that ships in no package — only the web app serves it, so every other consumer renders a broken image (confirmed 404 in the workflow-designer demo), and the absolute path cannot resolve under a non-root deployment base. One image per lattice type is lossy besides: a graphene monolayer and bulk GaN are both HEX, but the monolayer's vacuum padding flattens its zone.

ExtraImportantSettingsByContextProvider now also passes faces — the zone derived from the material's own reciprocal lattice — so components can draw it. Feature-detected against ReciprocalLattice.brillouinZone (mat3ra/made#295), so older made pins keep building and simply fall back to imgSrc; imgSrc is unchanged for hosts that do serve the artwork. Renderer: mat3ra/move#5.

Validation

• Tests: npm test → 31 passing (3 new: zone geometry forwarded with the right face counts for FCC, and property-name humanizing).
• Types: tsc --noEmit clean on src.
• Lint: on the 13 source files this PR touches, this branch reports 34 errors / 40 warnings versus main's 41 / 39 — no new problems, and 7 fewer errors than before (running prettier over the touched files cleaned up existing formatting). The new test file is lint-clean; the single remaining error in extraImportantSettings.tests.tsx (@mat3ra/utils listed as extraneous) is pre-existing on main.
• Demo: verified in wove's own standalone demo — unit cards render without UUIDs, everything else unchanged.

Note for maintainers: npm run lint cannot run from a clean checkout

package.json declares no eslint, prettier, or @exabyte-io/eslint-config dependencies, though .eslintrc.json extends that config and the lint script invokes both tools. To lint this branch I had to install the toolchain explicitly; the working combination is eslint 8 + eslint-plugin-prettier 5 + prettier 3 (plugin-prettier 4 breaks on prettier 3, and eslint 9+ rejects .eslintrc.json). Separately, main itself does not pass prettier --check src (6 files). Happy to open a small follow-up PR adding the devDependencies and formatting those files if that's wanted — kept out of this one deliberately.

🤖 Generated with Claude Code

https://claude.ai/code/session_01FFFpkKD3zHysJXgAbT2uYV