queen actors: the decision log as a three-way conformance spec (wasm, reference, t27b) #1727

Part of #1712. Follows #1718 / #1725 (lane 1: telemetry and the decision log).

Problem

The decision log replays on fresh instances of the same wasm cards (replayDecisions()), so it checks the wasm against itself. The owner asked on 2026-10-10 ("yes") for a three-way check: production's wasm, the reference path (t27c test-report: gen, then zig) and t27b's native AArch64 JIT must give the same answer to every call the runtime made.

What lands here

Test glue only, no runtime change:

• apps/server/tests/api/queen-decision-spec.ts turns a decision log into one t27 module per card: one assert fn(args) == result per distinct (fn, args), typed by the card's own signatures. A call answered two ways, or a value no literal of its declared type can hold, is refused.
• queen-actors-telemetry.test.ts: with QUEEN_DECISION_SPEC_OUT=<t27 checkout>, the seeded reviewer run (seed 7852) writes those modules to specs/queen/replay/ there. A small test covers the typing and the refusals.

The generated modules land in gHashTag/t27#8313.