docs: sync error-codes + backfill changelog (M23/M24/M25)

[indykish]

Summary

• c336be5 — sync error-codes.mdx with source cleanup (pre-existing)
• 8d5a05c — backfill changelog with three accumulated entries:
  • v0.15.0 — Live Zombie Steering (M23_001)
  • v0.16.0 — REST Workspace-Scoped Route Refactor (M24_001)
  • v0.16.1 — zBench Micro-Benchmark Catalog (M25_001)

Test plan

• changelog.mdx renders — MDX syntax preserved
• No breaking moves to already-published blocks

🤖 Generated with Claude Code

Greptile Summary

This PR backfills three changelog entries (v0.15.0 Live Steering, v0.16.0 Route Refactor, v0.16.1 zBench) and syncs error-codes.mdx with a pre-existing source cleanup that retired several error codes. The MDX syntax is valid throughout and changelog ordering (newest-first) is preserved.

Confidence Score: 5/5

Safe to merge — documentation-only PR with no logic changes; all blocking concerns were raised in prior review threads.

Both files contain only MDX content changes. The error-code removals are a source-sync cleanup, changelog entries are factually consistent with each other and with prior entries, and MDX syntax is valid throughout. The open concerns (stale operator page, UZ-EXEC-009 conflict) were already raised in previous review threads and are not new findings from this pass.

No files require special attention beyond the operator-page staleness already flagged in prior threads.

Important Files Changed

Filename	Overview
changelog.mdx	Three new changelog entries (v0.15.0–v0.16.1) added in correct newest-first order; MDX syntax, route tables, and code blocks all look well-formed.
api-reference/error-codes.mdx	Pre-existing source cleanup removes ~20 error codes across several sections; the stale-operator-page and UZ-EXEC-009 conflicts were flagged in previous review threads.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    Client["API Client"]

    subgraph v0_15["v0.15.0 — Live Steering (M23_001)"]
        S1["POST /v1/zombies/{id}:steer"]
        R1["Redis zombie:{id}:steer\n(300s TTL)"]
        W1["Worker polls key\nat event loop top"]
        E1["Synthetic steer event\ninjected into stream"]
        S1 --> R1 --> W1 --> E1
    end

    subgraph v0_16["v0.16.0 — Route Refactor (M24_001)"]
        direction LR
        OLD["Flat /v1/zombies/*\n→ 404"]
        NEW["Workspace-scoped\n/v1/workspaces/{ws}/zombies/*"]
        OLD -. "Breaking change" .-> NEW
    end

    Client --> S1
    Client --> OLD
    Client --> NEW

Loading

_{Reviews (2): Last reviewed commit: "docs: backfill changelog v0.15.0 (M23) +..." | Re-trigger Greptile}

[greptile-apps]

Operator error-codes page not updated in sync

operator/observability/error-codes.mdx still documents every code this PR removes — UZ-EXEC-004 through UZ-EXEC-011, UZ-CRED-002, and UZ-SANDBOX-001 — with detailed operator remediation steps. Since this PR claims those codes were deleted from the source, the operator page is now stale and will give wrong guidance to anyone who encounters one of those codes in logs. The same codes are also referenced inline in operator/security/sandbox.mdx (lines 87–89) and operator/security/model.mdx (lines 39–40).

Prompt To Fix With AI

This is a comment left during a code review.
Path: api-reference/error-codes.mdx
Line: 179-186

Comment:
**Operator error-codes page not updated in sync**

`operator/observability/error-codes.mdx` still documents every code this PR removes — `UZ-EXEC-004` through `UZ-EXEC-011`, `UZ-CRED-002`, and `UZ-SANDBOX-001` — with detailed operator remediation steps. Since this PR claims those codes were deleted from the source, the operator page is now stale and will give wrong guidance to anyone who encounters one of those codes in logs. The same codes are also referenced inline in `operator/security/sandbox.mdx` (lines 87–89) and `operator/security/model.mdx` (lines 39–40).

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

[greptile-apps]

UZ-EXEC-009 description conflicts between pages

This page (synced with source) describes UZ-EXEC-009 as "Execution startup posture failure", but operator/observability/error-codes.mdx line 24 describes the same code as "OOM killed" (EXECUTOR_MEMORY_LIMIT_MB exceeded). The two meanings are contradictory — an operator hitting this code will get the wrong remediation advice from the operator reference page.

Prompt To Fix With AI

This is a comment left during a code review.
Path: api-reference/error-codes.mdx
Line: 183

Comment:
**`UZ-EXEC-009` description conflicts between pages**

This page (synced with source) describes `UZ-EXEC-009` as **"Execution startup posture failure"**, but `operator/observability/error-codes.mdx` line 24 describes the same code as **"OOM killed"** (`EXECUTOR_MEMORY_LIMIT_MB` exceeded). The two meanings are contradictory — an operator hitting this code will get the wrong remediation advice from the operator reference page.

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