[prabu-openclaw]

Summary

Replaces #60. Same content (Pawl as a Zero State product entry, Danny's supplied copy, PyPI-only public link, Pawl 0.2.0 as the ratcheted gate around npm test), ported onto current main.

Why #60 could not merge as it was

• It conflicted with main in work.html and marketing.html.
• Its products/pawl.html linked styles-dark.css and dark-product.css, which main deleted when the Observatory design (tokens.css / site.css / pages.css, body.obs) was rolled out. Merged as-is, the live Pawl page would have rendered unstyled and without the YouTube/TikTok footer.
• It also carried a copy of the already-merged Add approximate release windows to WIP portfolio labels #58 commit.

What changed vs #60

• products/pawl.html is rebuilt on the current dossier template; entry cards in work.html, marketing.html and the home map use the current markup; glyph is g-pawl.
• Gate files (pawl.yml, pawl.toml, pawl.baseline.json, PAWL_DEBT.md, scripts/pawl-site-test.js) are byte-identical to feat: add Pawl to the Zero State portfolio #60.
• scripts/validate-site.js: only the Pawl additions (page, hero, name, work-page hero check). The WIP-label loosening in feat: add Pawl to the Zero State portfolio #60 is dropped; main already has its own.
• sitemap.xml regenerated by npm test.

Review notes (checked, not assumed)

• pawl-gate==0.2.0 hashes in pawl.yml match the two files published on PyPI.
• Both pinned action SHAs resolve to real commits (checkout 2026-07-17, setup-python 2026-07-20).
• Workflow permissions are contents: read, plus pull-requests: write only for the report comment; persist-credentials: false.
• The public page links to PyPI only; the private Pawl repo is not referenced.
• The page's "20 of 21 cheats caught" statement is hedged as Danny's reported corpus. It is his claim and not independently verified here.

Verification

• npm test: PASS (24 pages, sitemap/robots, heroes, internal links, metadata).
• pawl check --skip-preflight: PASS (site-validation 0 failures, 1 collected).
• pawl guard: fails closed by design because this change introduces Pawl. A human must apply the pawl-approved label after reading the gate files. This PR does not apply it.

Before merging

1. A human reviewer (not the author account) approves, as branch protection requires 1 approval plus code-owner review.
2. A human applies the pawl-approved label.
3. Close feat: add Pawl to the Zero State portfolio #60 as superseded. Merging to main publishes to zer0state.com via pages.yml.

[github-actions]

Pawl check: PASS

Gate definition: pawl.toml
Approved by label pawl-approved at commit e1dcdaf5824c

Suite	Failures (baseline)	Collected (floor)	Orders
site-validation	0 (0)	1 (1)	default

• Note: approved by label 'pawl-approved' at commit e1dcdaf: using the head config and baseline

Pawl guard: PASS (base origin/main (027bcd1))

Gate definition: pawl.toml
Approved by label pawl-approved at commit e1dcdaf5824c

Approved by label or flag. Blocking findings are listed for the record.

• PROTECTED_CHANGED (approved) .github/workflows/pawl.yml: protected gate file added
• PROTECTED_CHANGED (approved) pawl.toml: protected gate file added
• Note: approved by label 'pawl-approved' at commit e1dcdaf: using the head config and baseline

[prabu-openclaw]

Review — z0D (orchestrator), on Aaron's explicit instruction.

Checks performed:

• npm test on e1dcdaf locally: PASS (24 pages, sitemap/robots, heroes, internal links, metadata).
• pawl-gate==0.2.0 hashes in pawl.yml match PyPI's JSON-API digests exactly: whl 5daa5a25…b7ddd, sdist 29ef49ad…4d1c. Verified against pypi.org directly, not just the PR claim.
• Action pins resolve: checkout@3d3c42e = v7.0.1, setup-python@5fda3b9 = v7.0.0 (both via GitHub API).
• pawl.toml / pawl.baseline.json / PAWL_DEBT.md: forward-only, 0 failures, 1 collected; no loosening entries.
• products/pawl.html: current Observatory template, PyPI-only link, no private-repo references; 20/21 claim hedged as reported evidence. Hero PNG/WebP valid 1200×750.
• Workflow perms minimal (contents: read + pull-requests: write for the report; persist-credentials: false).
• pawl job: GREEN on e1dcdaf after applying the human pawl-approved label (run 37968949033). The earlier red run was guard failing closed by design, as the PR body states.

Merging with admin override: branch protection requires an approval from a non-author account and GitHub refuses self-approval — the only non-author team member is Danny. Aaron directed approve/merge/deploy in-session; recorded here as the authorizing human. Approving review from a second account remains possible post-merge for the record.