refactor(studio): have the BFF report each schedule fire's outcome

[kantord]

Summary

The mapping from the daemon's stop reason to a fire outcome lived in the web app. The BFF now owns it, so every client reads the same vocabulary.

Part of #2303 ("Tiny follow-up fixes"); it does not close it. This is PR 7 of 14 in a stack of draft PRs, reviewed and merged in order.

What changed

• Contract: scheduleFireOutcomeSchema enum (claimed, in_flight, completed, failed, cancelled, timed_out, limit_reached, stopped) and a required outcome on scheduleFireSchema. stop, error and inFlight are unchanged. The schema comment says consumers must treat unknown future values as stopped.
• BFF: fireOutcome(fire), ported verbatim from the web function with its precedence and DECISION comment. no_progress stays stopped.
• Web: the stop-reason sets are gone; OUTCOME_LABEL and OUTCOME_VARIANT are Records over the generated union (compile-time exhaustive). An unknown or missing outcome reads "Stopped". The raw "Stop: ..." line is kept.
• openapi.json and types.gen.ts regenerated with pnpm run generate.

Behavior changes

None user-visible; labels and badge variants are identical to before.

API compatibility

• Scope: the Studio BFF /api/v1 OpenAPI contract, not the daemon wire API. engine/session and contracts/proto are untouched, and none of the paths in .claude/rules/wire-api-compatibility.md are touched, so the rule is not triggered. The wire policy (docs/architecture/api-surface.md#wire-api-compatibility) says additions stay in-major and stop reasons remain open strings; nothing here changes that.
• Additive: one new required response field. Existing readers of stop, error and inFlight are unaffected.
• No version skew: the BFF and web ship together.
• If the enum later grows, third-party BFF consumers must tolerate unknown values (documented in the schema).

Verification

Biome, typecheck, the full Studio test suite and pnpm generated:check pass on this branch, run on the assembled stack. The full Playwright suite passes on the stack tip (122 passed, 30 skipped, 0 failed, including chat-approval against a real mecated build). A 17-case BFF table test (including no_progress and an unknown stop) asserts it covers every enum value; a service test asserts stop, error and inFlight are still emitted. Only the two service-level server tests fail without the production change; the table and web tests call functions that exist only with this change.

Not included

The daemon, its protobuf contracts and the stop-reason vocabulary.

Fully or partially written by an AI agent.

🤖 Generated with Claude Code

[peppescg]

Thanks Daniel. Moving the stop-reason mapping into the BFF with a closed enum, typed label maps on the web, and a test that checks every enum value is covered is exactly the shape I hoped for.

Nits:

• apps/server/src/mecatl/schedules.ts:234: type FireOutcome = z.infer<typeof scheduleFireOutcomeSchema> would tie the BFF to the schema directly instead of going through the generated response type.