Unify GoalOS public site and add Cloud MVP 0.2 software proof

[MontrealAI]

Motivation

• Consolidate a fragmented public site into one canonical GoalOS shell and footer so the GitHub Pages site presents a single, institutional GoalOS · Proof Gradient experience.
• Add a self-contained, browser-based GoalOS Cloud MVP 0.2 software proof that demonstrates the Run → Score → Prove → Diagnose → Improve → Approve → Version → Monitor → Re-run loop without secrets or external APIs.
• Prevent accidental publication of paid/private delivery artifacts by adding a guard and tightening validation of public deploy paths.
• Preserve the public AEP standards layer and existing production-foundation files while making the public site reviewable and CI-validated.

Description

• Added canonical site assets site/assets/goalos-site-v2.css and site/assets/goalos-site-v2.js and unified public pages to include the GOALOS-CANONICAL-SHELL and GOALOS-CANONICAL-FOOTER markers.
• Created/verified the Cloud MVP at site/app/goalos-cloud-mvp/ including assets/enterprise-core.mjs, assets/app.js, assets/styles.css, schemas/*, openapi.json, tests/enterprise-core.test.mjs, README.md, and supporting manifest/docs.
• Implemented paid-artifact guard scripts/check_no_paid_artifacts.py and hardened scripts/validate_goalos_site_v2.py to detect duplicate topbars, old GoalOS shell markers, broken internal /proof-gradient/ links, and disallowed paid artifact patterns; removed the active public-site ZIP site/standards/AEP-001/complete-package.zip from the deploy root to comply with the guard.
• Updated documentation and manifests: docs/GOALOS_REPO_AUDIT.md, docs/GOALOS_PUBLIC_SITE_REPAIR.md, docs/GOALOS_CLOUD_MVP_0_2.md, docs/GOALOS_COMMERCIALIZATION_STATUS.md, docs/GOALOS_PAID_ARTIFACT_POLICY.md, docs/GOALOS_RECURSIVE_WORKFLOW_OS.md, and generated site/goalos-site-repair-v2-report.json and site/goalos-site-manifest-v2.json; added/updated GitHub Actions workflows for shell repair, Cloud MVP build, and public-site refresh.

Testing

• Ran the Cloud MVP unit test with Node: node site/app/goalos-cloud-mvp/tests/enterprise-core.test.mjs and it passed (report: v11 compliance improved, graph nodes/edges present).
• Ran static-site validation and guards: python scripts/validate_goalos_site_v2.py and python scripts/check_no_paid_artifacts.py and both passed for 206 public HTML pages and no paid/private artifacts in active site/.
• Ran full test matrix: pytest (72 tests passed, 3 warnings after installing editable dev deps), make test (56 unittest tests passed), and internal site/link/product validators (scripts/check_site_links.py, scripts/validate_goalos_products.py) — all passed.
• Notes: initial pytest/make test collection required installing editable dev dependencies (python -m pip install -e .[dev]); after installing the editable package and dependencies the test suites passed and JSON artifacts (openapi.json, schemas, site manifests) validated successfully.

---

Codex Task

[chatgpt-codex-connector]

💡 Codex Review

https://github.com/MontrealAI/proof-gradient/blob/9065bf0cee80e69f3c3eecf60f100cc1143fece8/site/standards/AEP-001/complete-package.zip#L1
Regenerate public manifests after removing the ZIP

After this deletion, rg complete-package.zip site/*.json still finds site/site-manifest.json, site/goalos-product-ladder-site-manifest.json, site/goalos-complete-site-manifest.json, and site/goalos-unified-site-manifest.json listing standards/AEP-001/complete-package.zip, but the file is no longer present under site/. Any viewer or automation that treats those deployed manifests as the site inventory will advertise a downloadable artifact that now 404s, so the manifests should be regenerated or pruned as part of the removal.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 044a8c7784

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Finish canonicalizing the proof pages

When this page (and the two sibling proof pages changed the same way) gets the canonical shell inserted here, the old per-page <nav> remains before <main> and no GOALOS-CANONICAL-FOOTER:START is added. I checked the Pages workflows (.github/workflows/refresh-complete-goalos-public-site.yml and repair-goalos-canonical-shell-v2.yml), which run python scripts/validate_goalos_site_v2.py; running that command on this commit fails for these pages with duplicate topbar/header/nav blocks and missing canonical footer, so the deploy validation is blocked.

Useful? React with 👍 / 👎.