docs(help): say 'Factorio', not 'Pyanodons', in mod-agnostic help text

Per the app's mod-agnostic direction (#68): help/UI copy that describes
the loaded data generically shouldn't hard-code Py. Browse now reads
'the loaded Factorio data' and 'the recipe graph'; the block-editor
'how it solves' help and the heat/pollution tooltips drop Py where the
mechanic is Factorio-general. Concrete examples (iron plate,
iron-pulp-07) stay. Genuinely Py-specific, data-gated features keep
their attribution — the TURD tab and the AI assistant (a Py expert by
its system prompt) still name Pyanodons, which is accurate.

Author: ApocDev

app/src/components/block/balance-card.tsx

@@ -242,7 +242,7 @@ export function BalanceCard({
                 {Math.abs(res.power.pollutionPerMin) > 0.005 && (
                   <span
                     className={`flex items-center gap-1 ${res.power.pollutionPerMin < 0 ? "text-success" : "text-warning/80"}`}
-                    title="pollution per minute from this block's machines (base emissions × energy-consumption × pollution module effects; fuel-type multipliers not modelled). Negative = net absorption — Py forestry and plantations soak pollution like trees."
+                    title="pollution per minute from this block's machines (base emissions × energy-consumption × pollution module effects; fuel-type multipliers not modelled). Negative = net absorption — some buildings (forestry, plantations) soak pollution like trees."
                   >
                     <Cloud className="size-3.5" /> {num(Math.abs(res.power.pollutionPerMin))}
                     <span className="text-muted-foreground">
@@ -253,7 +253,7 @@ export function BalanceCard({
                 {res.power.heatW > 0 && (
                   <span
                     className="flex items-center gap-1 text-warning"
-                    title="Heat-powered buildings (Py hard mode). Heat doesn't travel far (~15 tiles), so a heat source — e.g. a py-heat-exchanger — must be built LOCAL to this block."
+                    title="Heat-powered buildings. Heat doesn't travel far (~15 tiles), so a heat source (e.g. a heat exchanger) must be built LOCAL to this block."
                   >
                     <Flame className="size-3.5" /> {fmtW(res.power.heatW)}{" "}
                     <span className="text-muted-foreground">heat · local source needed</span>

app/src/components/block/block-toolbar.tsx

@@ -291,8 +291,8 @@ export function BlockToolbar({
           production must cover consumption, surplus exports, and it never imports. Everything else
           is free — consumption imports, and an incidental byproduct just offsets the import
           (it's never scaled up to cover demand). The solver picks the cheapest run-rates
-          (fewest machine-seconds) satisfying the goals, marks, and pins — it handles Py's
-          cyclic recipe chains, and identical inputs always solve identically.
+          (fewest machine-seconds) satisfying the goals, marks, and pins — it handles cyclic recipe
+          chains, and identical inputs always solve identically.
         </p>
         <p>
           <span className="text-foreground">You drive it, not an optimizer.</span> You choose the

app/src/routes/browse.tsx

@@ -83,20 +83,19 @@ function Browse() {
               <HelpButton title="What is Browse?">
                 <p>
                   Search every <span className="text-foreground">item and fluid</span> in the loaded
-                  Pyanodons data. Pick one to see its recipes — what makes it, what it&apos;s used
-                  in — plus its properties (stack size, fuel value, spoilage, temperatures, and so
-                  on).
+                  Factorio data. Pick one to see its recipes — what makes it, what it&apos;s used in
+                  — plus its properties (stack size, fuel value, spoilage, temperatures, and so on).
                 </p>
                 <p>
-                  Use it to explore Py&apos;s tangled recipe graph, and to find the{" "}
+                  Use it to explore the recipe graph, and to find the{" "}
                   <span className="text-foreground">internal names</span> that blocks and the
                   assistant refer to (e.g. <span className="text-foreground">iron-pulp-07</span>).
                 </p>
                 <p>
                   <span className="text-foreground">Worked example.</span> Search{" "}
                   <span className="text-foreground">iron plate</span> and pick it:{" "}
                   <span className="text-foreground">Produced by</span> lists every recipe that makes
-                  it (Py often has several tiers), and{" "}
+                  it (overhaul mods often have several tiers), and{" "}
                   <span className="text-foreground">Consumed by</span> lists where it&apos;s used.
                   Click any ingredient or product chip in a recipe to jump to that good and keep
                   walking upstream — that&apos;s how you trace a chain back to raw ores. A good