pages: /beta — Praxen 2.0 beta docs area

[virtualsteve-exa]

Adds a self-contained beta/ directory to main (the Pages source) serving the 2.0 beta program's single tester URL: https://open-agent-ai-security.github.io/praxen/beta/

• The 2.0 landing page (threat-model front door), full styled guide, examples, and the 12-target baseline with threat models + suite health — all relative links resolve within beta/
• Built from v2-beta @ 5a79699: install/quickstart point at the praxen-beta marketplace entry (plugins#7), versions read 2.0.0-beta.1
• Nothing outside beta/ changes — production site, skill, and baselines untouched
• Re-synced from v2-beta per beta cut; deleted at GA

Companion PR: open-agent-ai-security/plugins#7 (the praxen-beta marketplace entry).

🤖 Generated with Claude Code

https://claude.ai/code/session_01AzQr69UcAjFS7avZsRmap6

[virtualsteve-exa]

Automated review (background agent):

Reviewed the full 142-file diff (all HTML surface pages read in full; v1.3-opus5 baseline artifacts sampled as verbatim mirrors), with a scripted resolution check of every relative href/src in beta/index.html, beta/news.html, and all 14 beta/guide/*.html pages against the PR file list.

1. Scope containment — PASS

All 142 files are status added and every path is under beta/. Nothing outside beta/ is touched (confirmed via the paginated files API, not the capped 100-file view).

2. Link integrity — 2 blockers

Two asset files referenced by the copied pages were not copied into beta/ (they exist only at main's root, so the relative links 404 under /praxen/beta/):

• beta/assets/praxen-theme.css is missing. beta/index.html:72 and beta/news.html:84 load assets/praxen-theme.css, but the PR only copies beta/assets/count.js. Per the file's own comment this stylesheet carries the shared design tokens, base styles, buttons, and the Google Fonts import — the beta landing page and news page will render essentially unstyled. (The guide/ pages inline their CSS and are unaffected.)
• beta/graphics/exabeam-logo-white.svg is missing. beta/index.html:686 references graphics/exabeam-logo-white.svg; only graphics/brand/ and graphics/web/ were copied. Broken footer image.

Everything else resolves cleanly inside beta/: all guide-page cross-links, ../graphics/, ../assets/count.js, and the landing page's tests/baselines/v1.3-opus5/... report links point at files present in the PR. No ../examples or ../tests escapes from guide pages.

3. Install commands — mostly correct, 3 stragglers

Landing copy-button (index.html:621 and the JS at :712), guide/index.html:390, and the installation-page install blocks all correctly use praxen-beta@open-agent-ai-security. Plugin-key confirm strings (plugin list output showing praxen@…) left as-is, per convention. Remaining actionable commands still targeting the stable key in beta/guide/installation.html:

• Updating (Claude Code): claude plugin update praxen@open-agent-ai-security (~line 357) — updates the stable plugin, not the beta.
• Uninstalling: claude plugin uninstall praxen@… and codex plugin remove praxen@… — same mismatch if the beta installs under the praxen-beta key.

Ordering note (not a PR defect): praxen-beta is not yet in the community catalog (open-agent-ai-security/plugins currently lists only praxen and socxen), so the documented install will fail until that entry ships — worth sequencing before/with the Pages promote.

4. Version strings — PASS

The only explicit version strings are the two v2.0.0-beta.1 confirm strings in guide/installation.html (lines ~300/315) — correct. No stale 1.3.0 anywhere in the beta docs surface; the v1.3-opus5 mentions on the landing page are baseline-directory links, which is intended.

5. Production-site effects — PASS

No name collisions (beta/ is a new directory on main). sitemap.xml and root pages untouched, so nothing changes for the indexed production surface. Beta pages carry robots: index,follow but their canonical/og:url point at the production URLs (e.g., beta/guide/installation.html → /praxen/guide/installation.html), so search engines consolidate to prod rather than indexing /beta as competing duplicates — reads as intentional. GoatCounter beacon posts to the same analytics site; beta hits remain distinguishable by path.

Verdict: needs-fixes

The two missing assets (beta/assets/praxen-theme.css, beta/graphics/exabeam-logo-white.svg) will visibly break the beta landing and news pages the moment Pages publishes. Copy those two files into beta/ (and ideally fix the three praxen@ update/uninstall commands in guide/installation.html) — after that, the PR looks promote-safe.

[virtualsteve-exa]

Review fixes applied in 3c03598: assets/praxen-theme.css and graphics/exabeam-logo-white.svg now ship inside beta/ (landing + news styling restored); update/uninstall commands fixed to the praxen-beta entry at the source on v2-beta (48db543) and re-copied. All root-page asset refs verified to resolve within beta/. Sequencing note from the review stands: merge plugins#7 (the praxen-beta catalog entry) before or with this so the install commands on the beta pages resolve.

[virtualsteve-exa]

One page re-synced from v2-beta: the beta channel's delivery design changed to a vendored payload in the community catalog (open-agent-ai-security/plugins#9 + #7), and with it the plugin now installs under its own key praxen-beta@open-agent-ai-security, side by side with production. beta/guide/installation.html updated accordingly (confirm-lines, disable-production note, migration notes). No other beta page hardcodes the key; the landing page's install commands were already entry-based and unchanged.