Codex/v2 backup before v1 restore 20260706

.agents/skills/industry-pack-generator/SKILL.md

@@ -0,0 +1,61 @@
+---
+name: industry-pack-generator
+description: Generate Pascal industrial profile packs from an industry brief, factory equipment list, or request such as "make a cement/electrolytic aluminum/food processing industry pack"; create a structured pack spec, scaffold profiles and quality rules, validate with repository QA gates, and prepare the pack for the simulated cloud.
+---
+
+# Industry Pack Generator
+
+Use this skill to create or expand installable Pascal geometry knowledge/profile packs.
+
+## Workflow
+
+1. Read the current project rules:
+   - `PROFILE_PACK_AUTHORING_STANDARD.md`
+   - `LLM_PRIMITIVE_GENERATION_ARCHITECTURE.md` when architecture context is needed
+   - `references/industry-pack-spec.md` for the scaffold spec shape
+2. Identify package scope:
+   - Use one focused industry or extension domain per pack.
+   - Prefer `industry.{industry}.basic` for a self-contained base pack.
+   - Prefer `industry.{industry}.{extension}` with `dependsOn` for extensions.
+3. Draft a v2 industry pack spec JSON with equipment profiles, parts, primary roles, aliases, visual cues, quality constraints, and equipment-node intent.
+   - For basic packs, include `factoryArchitectures` and `processTemplates`.
+   - For extension packs, include them only when the extension adds a new factory-level process.
+   - For recipe-backed equipment, include `recipeId`, `processPorts`, and `equipmentDefaults` so the scaffold can emit `equipmentBindings`.
+4. Run the scaffold:
+
+```bash
+bun apps/editor/scripts/scaffold-industry-profile-pack.ts --spec <spec.json> --force
+```
+
+5. Validate and QA:
+
+```bash
+bun apps/editor/scripts/profile-pack-qa.ts <pack-id>@<version> --validate-only
+bun apps/editor/scripts/profile-pack-qa.ts <pack-id>@<version> --limit 3
+```
+
+6. Review generated profiles:
+   - Ensure every `parts[].kind` exists in the Part Registry.
+   - Ensure `primarySemanticRole` appears in required roles.
+   - Ensure aliases include Chinese and English terms when useful.
+   - Keep `shapeCount.max` realistic; avoid bloated geometry.
+
+## Pack Authoring Rules
+
+- Generate data first, not TypeScript hardcoding.
+- Reuse common part kinds from `packages/core/src/lib/part-registry.ts`.
+- Default new packages to schema v2 with `dependsOnPlugins` and `equipmentBindings`.
+- Use `generic_industrial_layout` unless a known layout family is clearly better.
+- Put device-specific knowledge in profiles and quality rules.
+- Do not invent a new family/layout for one equipment unless the layout is reusable.
+- For unknown equipment, model major visible assemblies: body, frame, drive, ports, platforms, legs, hoppers, ducts, panels, sensors.
+
+## Output Contract
+
+When finishing, report:
+
+- Pack id and output directory.
+- Device count and profile ids.
+- Whether factory architectures and process templates were generated.
+- Validation/QA command results.
+- Any low-confidence devices that need visual reference review.

.agents/skills/industry-pack-generator/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Industry Pack Generator"
+  short_description: "Generate and validate Pascal industrial profile packs."
+  default_prompt: "Generate a Pascal industry profile pack from an industry brief, then validate it with the repository QA gates."

.agents/skills/industry-pack-generator/references/industry-pack-spec.md

@@ -0,0 +1,159 @@
+# Industry Pack Scaffold Spec
+
+Use this JSON shape as input to `apps/editor/scripts/scaffold-industry-profile-pack.ts`.
+
+```json
+{
+  "industry": "cement",
+  "id": "industry.cement.basic",
+  "name": "Cement Basic Equipment Pack",
+  "version": "0.1.0",
+  "description": "Focused cement plant equipment pack.",
+  "schemaVersion": "2.0",
+  "dependsOnPlugins": ["pascal:factory-equipment"],
+  "capabilities": ["factory_creation"],
+  "factoryArchitectures": [
+    {
+      "id": "cement.factory.modular",
+      "label": "Cement plant modular architecture",
+      "industry": "cement",
+      "processId": "cement_plant_full",
+      "layoutStyle": "linear",
+      "defaultDimensions": { "length": 60, "width": 24 },
+      "modules": [
+        {
+          "id": "pyro_line",
+          "displayLabel": "Pyro line",
+          "order": 10,
+          "stationIds": ["rotary_kiln"]
+        }
+      ]
+    }
+  ],
+  "processTemplates": [
+    {
+      "processId": "cement_plant_full",
+      "processLabel": "Cement plant",
+      "processDisplayLabel": "Cement plant",
+      "domain": "industrial",
+      "aliases": ["cement plant", "cement factory"],
+      "requiredRoles": ["rotary_kiln"],
+      "defaultLayoutStyle": "linear",
+      "defaultDimensions": { "length": 60, "width": 24 },
+      "stations": [
+        {
+          "id": "rotary_kiln",
+          "label": "Rotary kiln",
+          "displayLabel": "Rotary kiln",
+          "role": "rotary_kiln",
+          "equipmentHint": "cement.rotary_kiln long inclined rotary kiln",
+          "profileId": "cement.rotary_kiln",
+          "footprintHint": "long"
+        }
+      ]
+    }
+  ],
+  "devices": [
+    {
+      "id": "rotary_kiln",
+      "name": "Rotary kiln",
+      "aliases": ["rotary kiln", "cement kiln", "回转窑", "水泥回转窑"],
+      "recipeId": "factory:storage-tank",
+      "layoutFamily": "vessel_layout",
+      "family": "tank",
+      "defaultDimensions": { "length": 12, "width": 2.2, "height": 2.4 },
+      "processPorts": [
+        { "id": "inlet", "side": "left", "diameter": 0.3 },
+        { "id": "outlet", "side": "right", "diameter": 0.28 }
+      ],
+      "equipmentDefaults": { "orientation": "horizontal", "capacity": 30, "liquidLevel": 0.35 },
+      "primarySemanticRole": "kiln_shell",
+      "parts": [
+        {
+          "kind": "cylindrical_tank",
+          "semanticRole": "kiln_shell",
+          "required": true,
+          "length": 12,
+          "radius": 0.65,
+          "axis": "x"
+        }
+      ],
+      "forbiddenRoles": ["vehicle_cabin"],
+      "shapeCount": { "min": 8, "max": 80 },
+      "visualCues": ["long inclined cylinder", "riding rings", "support rollers"]
+    }
+  ]
+}
+```
+
+## Top-Level Fields
+
+- `industry`: required. Use a focused industry id such as `cement`, `food`, `fine-chemical`, or `electrolytic-aluminum`.
+- `id`: optional. Defaults to `industry.{industry}.basic`.
+- `name`: optional. Defaults to `{industry} Basic Equipment Pack`.
+- `version`: optional. Defaults to `0.1.0`.
+- `schemaVersion`: optional. Defaults to `2.0`.
+- `dependsOn`: optional for extension packs, for example `[{ "id": "industry.fine-chemical.basic", "version": ">=0.1.0" }]`.
+- `dependsOnPlugins`: optional. Defaults to `["pascal:factory-equipment"]` for v2 equipment-node packs.
+- `capabilities`: optional. Use `["factory_creation"]` only when the pack includes factory/process knowledge.
+- `factoryArchitectures`: required when `capabilities` includes `factory_creation`; otherwise optional. Defines the whole-plant module tree.
+- `processTemplates`: required when `capabilities` includes `factory_creation`; otherwise optional. Defines stations, aliases, and station connections.
+- `devices`: required non-empty list.
+
+## Factory-Capable Pack Rules
+
+When `capabilities` includes `factory_creation`, QA enforces:
+
+- At least one `factoryArchitectures` resource.
+- At least one `processTemplates` resource.
+- Every station must resolve through `profileId`/`equipmentProfileId` to an `equipmentBindings[]`
+  entry or declare `genericFallback.reason`.
+- Every process-template station must be covered by a device profile, native resolver, or catalog resolver hint.
+- Every architecture module `stationIds[]` entry must exist in the matching process template.
+- Factory creation is intentionally single-process-template per request. Do not add quantity expansion fields such as `parameters`, `flows`, `countParam`, `defaultCount`, `minCount`, `maxCount`, or `replicatedStationIds`.
+
+If the pack only provides equipment profiles, omit `factory_creation`; QA will classify it as a `device-only` pack.
+
+## Device Fields
+
+- `id`, `name`, `aliases`, `parts`, `primarySemanticRole` are required.
+- `layoutFamily` defaults to `generic_industrial_layout`.
+- `family` defaults to `generic`.
+- `recipeId` may reference a registered semantic equipment recipe such as `factory:centrifugal-pump`, `factory:storage-tank`, `factory:distillation-unit`, `factory:refinery-reactor-unit`, or `factory:refinery-auxiliary-unit`; otherwise the scaffold infers known equipment kinds from profile text.
+- `defaultDimensions` should describe the whole equipment envelope.
+- `processPorts` declares device-level ports that v2 `portMap` must cover.
+- `equipmentDefaults` declares equipment-node parameters such as pump type, flow rate, motor power,
+  tank orientation, capacity, or liquid level.
+- `parts[].kind` must exist in the Part Registry.
+- `parts[].semanticRole` should be stable and domain-specific.
+- `qualityRequiredRoles` can add roles beyond required parts.
+- `forbiddenRoles` should prevent common wrong-domain details.
+- `shapeCount` controls QA expectations.
+- Control rooms, MCC rooms, labs, substations, and other occupied-building stations should use
+  `preferredResolver: "profile-parts"` instead of `catalog-item`, with roles for the building body,
+  roof cap/parapet, door/opening, windows, panels, and service entries.
+- Packaged boilers can use a rectangular casing, but should also include boiler-specific process
+  features such as a stack, steam drum or tube bank, steam header/manifold, burner opening, platform,
+  and control box. Avoid profiles that are only `generic_body` plus one accessory.
+
+## Generated Files
+
+The scaffold writes:
+
+- `pack.json`
+- `README.md`
+- `profiles/generated.json`
+- `factory-architectures/generated.json` when `factoryArchitectures` is provided
+- `process-templates/generated.json` when `processTemplates` is provided
+- `quality-rules/generated-quality.json`
+- `<pack-id>-<version>.zip` beside the generated source directory, unless `--skip-zip` is used
+
+The generated `README.md` labels the pack as `factory-capable` or `device-only` and lists supported factory/process templates when factory creation is enabled.
+The generated `pack.json` uses schema v2, includes `dependsOnPlugins`, and writes inferred
+`equipmentBindings` for profiles that map to factory equipment nodes.
+
+Run validation after generation:
+
+```bash
+bun apps/editor/scripts/profile-pack-qa.ts <pack-id>@<version> --validate-only
+```