Platform Automation — Distribution Spike

This page hosts the Phase 0 spike CRX for browser-matrix testing. Not a real product. Purpose: verify that sideload .crx with custom update_url works on Chrome / Edge / Brave / Opera × Win + Mac before we commit to Phase 1A.

This extension only logs heartbeats and reads (does NOT write) Facebook / Instagram pages. Cookies stay local. Do not install on a personal account if you are concerned — use a fresh browser profile (see test plan).

1. Download

spike CRX — drag onto chrome://extensions
update.xml — auto-update manifest
_build-info.json — Extension ID + version + build timestamp

2. Install (consumer flow — Test T1)

Open chrome://extensions in a fresh profile
Developer Mode toggle: OFF (mimics real customer)
Drag the .crx file onto the page
Record what happens — install dialog? warning text? failure?

If T1 fails on Chrome Win/Mac, that confirms Codex round 3 P0-1. Fall back to T2 (Developer Mode ON) and continue the matrix.

3. Run the full test matrix

See design/distribution/browser-matrix-test-plan.md in the repo for tests T1–T7 across all four browsers × two operating systems.

After each browser, click the extension icon → Copy diagnostic JSON → paste into design/distribution/browser-matrix.md per the template.

4. Decision gate

≥ 10 / 12 SHIP including Chrome Win + Mac → D-09 validated, Phase 1A green light
Chrome Win + Mac both DROP → STOP Phase 1A, trigger pivot decision

What this spike does NOT test

Posting to FB / IG (deferred to Phase 1A)
License gating
AI proxy calls
Anti-detection patterns

Built via scripts/build-spike.sh. Source: design/distribution/spike-crx/. Issue #1.