Preserve fluid temperatures across factory boundaries with ingredient pins

[ApocDev]

Problem

The block solver models fluid-temperature variants internally, but folds them to the base fluid name before persisting block boundary flows. Factory Scenario therefore treats all temperatures of a fluid as interchangeable. It can allocate scarce high-temperature supply to an unrestricted consumer or accept low-temperature supply for a strict consumer.

Direction

• Let a user select Auto or an exact known compatible temperature on each recipe fluid ingredient.
• Keep Factorio fluid prototypes canonical; temperature variants remain planner identities.
• Preserve exact producer temperatures and consumer accepted ranges through cached block flows and composed/factory solves.
• Compile qualified flows into exact variants and compatibility pools in the factory LP.
• Keep supply priority behavior within compatible supplies.
• Make the implementation generic for every temperature-sensitive fluid, not steam-specific.

Acceptance criteria

• A consumer pinned to 250 C cannot be satisfied by 2000 C supply.
• A consumer requiring 2000 C cannot be satisfied by 250 C supply.
• An Auto consumer can use any recipe-compatible known temperature.
• Temperature choices are filtered to the ingredient prototype range.
• Existing blocks without selections retain Auto behavior.
• Temperature identity survives saved block flows, composed blocks, Factory Scenario preview/apply validation, and supply-allocation reporting.
• Main UI flow has E2E coverage and planner behavior has focused unit tests.
• User and development documentation describe temperature selection and factory routing.

Follow-up to #110: in-block temperature identity exists, but its original factory-boundary scope is still folded away.

[ApocDev]

Implemented in the working tree: per-recipe fluid temperature choices, temperature-qualified block boundaries and composed modules, compatibility-aware Factory Scenario allocation, inline chip UI, migration, docs, unit coverage, and a mutating browser test. Verified with app check (804 tests), docs build, and the dedicated Playwright flow. Leaving the issue open until the changes are committed.

[ApocDev]

Implemented the Factory Overview follow-up in the working tree: temperature-qualified fluids now render as distinct localized rows (for example Steam 250°), an exact producer nets with a consumer pinned to the same temperature, and single-temperature fluids such as Formic acid remain unqualified. Added DB/unit coverage plus a mutating Playwright flow covering both cases. Verification: app vp check; 100 files / 810 tests; docs check + build; focused Playwright 2/2. Leaving the issue open until the uncommitted feature work is committed.

[ApocDev]

Finished two additional working-tree follow-ups. Fluid temperature menus now support a per-fluid favorite star; compatible newly added recipe rows bake that exact temperature as their initial pin, while explicit existing rows are untouched and incompatible favorites fall back to the recipe range. Also fixed producer-only temperature display: the variant scan now includes products and resolves an unspecified product temperature through the fluid default, so offshore-pump Water shows 15° while single-temperature Formic acid stays unqualified. Verification: app vp check; 100 files / 812 tests; docs check + build; focused Playwright 3/3 (favorite Steam default, Formic acid suppression, offshore Water 15°). Leaving the issue open until the uncommitted feature is committed.

[ApocDev]

Finished the remaining goal/drill-down consistency pass in the working tree. Temperature-sensitive fluid goals now have the same clickable exact/range selector as recipe inputs, constrain the block solver to the selected real produced variant, persist/copy/diff that qualifier, and inherit a valid per-fluid favorite when newly added. Factory Overview drill-down now queries by the normalized qualified flow identity, so Steam 250° shows exact-250 producers plus 250-pinned consumers while Steam ≥15° shows only the wider range contract; creating a block from an exact row carries the temperature into its goal. Added solver, block-compute, query/store, and browser coverage. Verification: app vp check; 100 files / 815 tests; docs check + build; focused Playwright 3/3. No commit created; leaving #158 open until the working-tree feature is committed.

[ApocDev]

Implemented and verified in commit b5b1d2b. Fluid temperature identities now persist across block boundaries, goals, favorites, Factory Overview, and Scenario routing.