docs(index): pivot statement and April 11 pre-release notice

[indykish]

Summary

• Removes hardcoded April 5 launch date from Early Access tip
• Adds product pivot statement
• Adds spec-to-PR description
• Sets expectation of revised release by April 11

🤖 Generated with Claude Code

[greptile-apps]

Greptile Summary

This PR updates the docs landing page with a product pivot statement and pre-release notice, refreshes changelog.mdx with the v0.4.0 release entry (mid-run agent steering, live CLI streaming, billing breakdown, and a breaking SSE id: field change), and introduces a new operator/observability/posthog-events.mdx PostHog event catalogue.

• changelog.mdx: The v0.4.0 entry is well-structured and terminology-compliant; the breaking change notice is clearly called out.
• index.mdx: Pivot statement and spec-to-PR description added to the Early Access tip; prior review threads flagged the concrete "April 11" date and a third-person sentence — those remain unresolved.
• operator/observability/posthog-events.mdx: Three AGENTS.md content-boundary violations — vault identifiers and internal playbook paths in the Provisioning Contract section, internal source file paths in the Runtime Events emitter columns, and title-case headings used throughout the file.

Confidence Score: 4/5

Safe to merge after addressing vault path exposure and internal pipeline details in the new posthog-events.mdx file.

The changelog and index changes are straightforward and low-risk. The new posthog-events.mdx contains two P1 violations of AGENTS.md content boundaries (vault paths/internal playbook references, and internal pipeline file paths) that should be resolved before the page ships to operators.

operator/observability/posthog-events.mdx requires the most attention — the Provisioning Contract and Runtime Events sections need to be revised to remove vault identifiers, internal playbook paths, and internal source file references.

Important Files Changed

Filename	Overview
changelog.mdx	Adds v0.4.0 release entry with multiple new features and a clear breaking change notice; terminology and style are consistent with AGENTS.md.
index.mdx	Removes hardcoded April 5 date and adds pivot statement; prior review threads flagged the date reference and third-person voice, which remain unresolved.
operator/observability/posthog-events.mdx	New PostHog event catalogue; violates AGENTS.md content boundaries by exposing vault paths, internal playbook references, and internal pipeline file paths, and uses title-case headings throughout.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Developer submits spec] --> B[Agent implements spec]
    B --> C{Quality gates pass?}
    C -- No --> D[Agent self-repairs]
    D --> C
    C -- Yes --> E[PR opened with scorecard]
    E --> F[Operator reviews one PR]

    subgraph PostHog observability
        B --> G[run_started]
        D --> H[run_retried]
        C --> I[agent.run.scored]
        E --> J[run_completed]
    end

Loading

Prompt To Fix All With AI

This is a comment left during a code review.
Path: operator/observability/posthog-events.mdx
Line: 14-24

Comment:
**Vault paths and internal playbook paths in public docs**

The Provisioning Contract section violates two AGENTS.md content boundaries:

1. **Vault paths exposed**: `ZMB_CD_DEV`, `ZMB_CD_PROD`, `posthog-dev`, and `posthog-prod` are vault identifiers and item names. AGENTS.md explicitly prohibits exposing vault paths or 1Password references in docs.
2. **Internal deployment playbooks referenced**: The propagation list (`playbooks/001_bootstrap/001_playbook.md`, `playbooks/002_preflight/001_gate.sh`, `playbooks/gates/m2_001/section-2-procurement-readiness.sh`) documents internal deployment playbooks that are meant to live only in the main repo.

Consider replacing the Provisioning Contract section with operator-level guidance on _what_ to configure (e.g., "set the PostHog project key per environment") without referencing internal vault names or playbook paths.

**Context Used:** AGENTS.md ([source](https://app.greptile.com/review/custom-context?memory=e994989b-b25e-4468-be5d-6bde3ddb0ce6))

How can I resolve this? If you propose a fix, please make it concise.

---

This is a comment left during a code review.
Path: operator/observability/posthog-events.mdx
Line: 113

Comment:
**Internal pipeline file paths in operator docs**

The Runtime Events section lists internal emitter file paths (`src/observability/posthog_events.zig`, `pipeline/worker_stage_executor.zig`, `pipeline/scoring.zig`, `cmd/serve.zig`, `cmd/worker.zig`, `auth_sessions_http.zig`, `workspaces_lifecycle.zig`, `github_callback.zig`, `runs/start.zig`, `runs/retry.zig`) as the Emitter column in every table.

AGENTS.md specifies: "Do not document internal agent pipeline internals — keep operator docs at the operational level." Surfacing internal source file paths couples the public docs to the implementation layout and violates this boundary.

Consider dropping the Emitter column from the Runtime Events tables entirely, or replacing specific file paths with the responsible subsystem name (e.g., "agent pipeline", "auth middleware", "run scheduler").

**Context Used:** AGENTS.md ([source](https://app.greptile.com/review/custom-context?memory=e994989b-b25e-4468-be5d-6bde3ddb0ce6))

How can I resolve this? If you propose a fix, please make it concise.

---

This is a comment left during a code review.
Path: operator/observability/posthog-events.mdx
Line: 1

Comment:
**Title-case headings throughout — AGENTS.md requires sentence case**

AGENTS.md requires sentence case for all headings. Every heading in this new file uses title case. Examples that need correcting:

- `# PostHog Product Analytics — Event Catalogue` → `# PostHog product analytics — event catalogue`
- `## Provisioning Contract` → `## Provisioning contract`
- `## Surface Configuration` → `## Surface configuration`
- `## Website Events` → `## Website events`
- `## App Events` → `## App events`
- `## CLI Events` → `## CLI events`
- `## Runtime Events` → `## Runtime events`
- `### Startup Lifecycle` → `### Startup lifecycle`
- `### Auth Lifecycle` → `### Auth lifecycle`
- `### Workspace Lifecycle` → `### Workspace lifecycle`
- `### Run Lifecycle` → `### Run lifecycle`
- `### Policy & Billing` → `### Policy and billing`
- `## Error Code Coverage` → `## Error code coverage`
- `## Adding New Events` → `## Adding new events`

**Context Used:** AGENTS.md ([source](https://app.greptile.com/review/custom-context?memory=e994989b-b25e-4468-be5d-6bde3ddb0ce6))

How can I resolve this? If you propose a fix, please make it concise.

_{Reviews (2): Last reviewed commit: "docs: add v0.4.0 changelog entry, add po..." | Re-trigger Greptile}