page-foundry v2.8.0

v2.8 (2026-07-07)

• Orchestration doctrine made explicit and enforced. page-foundry is an orchestrator; the phases now INVOKE each companion skill as the primary path (handing it the phase's inputs, using its output), and fall back to the reference-file condensed rules only when the companion is missing or declined. Every fallback is flagged to the user and recorded on a new degraded line in the gate report and run log, so a run missing load-bearing companions reads as the partial execution it is
• Rewrote every phase to name, invoke, and gate its companions instead of the old soft "if installed, apply here": product-marketing (Phase 0 brief), customer-research + marketing-psychology (Phase 1), cro plus pricing/competitors/aso/launch/lead-magnets/popups/signup (Phase 2), copywriting + copy-editing (Phase 3), frontend-design + web-design-guidelines + theme-factory (Phase 4), web-artifacts-builder + gstack /design-html (Phase 5), cro + web-design-guidelines + ai-seo + schema + analytics + gstack /design-review //qa (Phase 6)
• Reference files are now explicitly the floor, used only when a companion is absent, not the standard. The voice scan and integrity gate stay page-foundry's own and are never waived by a companion
• Recorded from a real observation: the phases named companions in a table but did not consistently invoke or gate them, so the skill was silently doing subsidiary work itself and producing variable output