[Nemo157]

Unlike the Claude-driven /smoke-test, this needs no LLM: chiplab-cli runs a fixed test suite, so results are reproducible and cheap enough to run on every relevant PR.

Each workflow gets its own Chiplab project so their runs don't mix. CHIPLAB_API_KEY must be switched to a token for the new account that owns these projects.

Closes: DEV-2431

[claude]

Change Summary

Adds .github/workflows/chiplab-smoke.yml, which builds the bare-metal stm32f4-discovery example and runs it through chiplab-cli run-test-suite on pushes to main, PRs touching the example or harness files, and manual dispatch.
Adds the Deno test suite (.github/chiplab/hello-world.test.ts) and board descriptor (.github/chiplab/stm32f4-discovery.board.json) that the CLI consumes.
Documents the per-workflow Chiplab project_ids in a new AGENTS.md section and points the existing Claude-driven /smoke-test prompt at its project.

Closes DEV-2431; I could not retrieve the Linear issue in this environment, so alignment with its acceptance criteria is unverified.

Review notes

Verified against the repo: the Rust target (thumbv7m-none-eabi), the ELF path, the presence of Cargo.lock (needed for --locked), the board key stm32f4_discovery from supported-boards.md, and USART2 as the UART the example writes to all match the workflow and board JSON.

Not verified (no network access in this review run): the chiplab-cli release asset and checksum file names, the run-test-suite flags, the CHIPLAB_TOKEN variable name, the board JSON schema, and the simulation.runUntilUartLine API and its timeout unit.
Please double-check those against the current chiplab-cli README before merging.

Inline comments cover the remaining points.

[Nemo157]

Semi-relatedly: to confirm the token and agents.md update (though it will run with the old workflow prompt) /smoke-test

[vE5li]

Very nice