Project

claude-code-marketplace

Build Model

sonnet

Review Model

codex-5.5

Runtime Model

sonnet

Rounds

1

Work Item

Open in Airtable

Output

Open PR

Time by Role

Agent Dispatches

Tokens by Role

Token breakdown by type pending; only aggregate usage is available.

Code

Validation Contract

# Validation Contract — recpo2hb6y2fI0xd6 docs(adva-engineer): create the missing docs/telemetry.md the README links to

Generated from: https://airtable.com/app1ofkkx1WnmxVF2/tbliZY3lFYlV5dP89/recpo2hb6y2fI0xd6
Generated at: 2026-05-26T00:00:00Z

## Assertions

1. [A] The file `plugins/adva-engineer/docs/telemetry.md` exists and is tracked by git.
2. [A] The file's first line starts with `# Telemetry` (H1 title matching airtable-schema.md convention).
3. [A] The file contains at least 5 H2 headings (`^## `): one each for "Env vars / wiring", "Emission points", "Token capture", "Resilience", and "See also".
4. [A] The file contains the literal strings `contract_generated`, `emit_diff_stats`, and `mission-control-gamma-snowy.vercel.app`.
5. [A] The file's Emission points section names, at minimum: `contract_generated` (§3c → Validation Contract panel), `dispatch_started` (§6), `validator_verdict` (§6, §8), `blocked` (§6), `merger.completed`/`merger.blocked` (§7), `pr_opened` (§9), `completed` (§10), and `emit_diff_stats` (§10 → Code panel / Run Diff Stats table).
6. [A] The Token capture section explains what `extract_usage` parses (total_tokens, duration_ms from `<usage>` envelopes), what stays null (Tokens In / Tokens Out / Cache Read / Cache Creation) and why, and references the slice-2 spike finding.
7. [A] The diff scope is limited to creating `plugins/adva-engineer/docs/telemetry.md` — no other files are added, modified, or deleted. Verifiable via `git diff --name-status main...HEAD`.
8. [A] The file contains no secrets — only env var NAMES (e.g. `AIRTABLE_API_KEY`), never values.
9. [A] The file's formatting matches `plugins/adva-engineer/docs/airtable-schema.md`: H1 title, H2 section heads, GFM tables where tabular, fenced code blocks for record IDs, no emojis.

## Coverage Rules

- `[A]` assertions MUST have a corresponding failing test (or grep/file check for markdown-only repos) in the dev's first commit.
- `[R]` assertions MUST be verified by the runtime validator against a running instance of the app.
- The reviewer MUST reject any first commit that has no `[A]` verification for each `[A]` assertion.
- Tag `[A]` when: the assertion can be verified by reading files, running unit/integration tests, or static analysis.
- Tag `[R]` when: the assertion requires spawning a server, opening a browser, or running a CLI against a live process.

Event Timeline (6 events)