[AdaWorldAPI]

What

Adds the projection emitter to ogar-emitter — the read-arm twin of
emit_do_adapters. It turns a typed column→field projection recipe into a
deterministic impl From<Row> for Domain module (the Pattern A
projection consumers hand-write today as impl From<XRow> for Domain).

Why

Session B's Patient furnace turn (CODEGEN-PARITY-SESSION-SPLIT.md).
The furnace's "no hand-roll" rule: when a consumer wants to hand-author a
projection, that means the generator is missing an arm. OGAR had the
DO/behavioral emitter (emit_do_adapters) and a struct-declaration
emitter (RustStruct) but no projection emitter — that gap is filled
here so Session A can replay its value oracle against generated output
instead of the hand-written projection.

Shape

• ProjectionClass / FieldProjection / FieldSource — corpus-agnostic
  typed input (no corpus data in the module), mirroring do_adapter.rs.
• FieldSource is a closed transform set derived from the real
  medcare PatientRow→Patient projection: Passthrough /
  UnwrapOrDefault / MapNaiveDate / IntFlagToBool / Const. A
  transform not in the set is a Core gap → extend the enum deliberately
  (Core-First), never hand-patch generated output.
• classid provenance stamped from the codebook (canonical_concept_id);
  patient = 0x0901 (already minted). Unminted concepts get a visible
  marker, never silent.
• Fully deterministic (classes sorted by domain type; field order = recipe
  order) → diffable as a golden artifact.

Proof

• Pinned golden test reproduces the hand-written medcare
  PatientRow→Patient projection byte-for-byte in behavior — this is
  the Patient shakedown; Session A replays its medcare-parity-fixtures
  value oracle against this generated output.
• Determinism test (class-order invariance) + unminted-marker test.
• cargo test -p ogar-emitter → 38 pass; cargo clippy -p ogar-emitter --all-targets -- -D warnings clean; cargo fmt clean.

Handoff

Session A: wire the emitted impl From<PatientRow> for Patient as the
generated Patient adapter and re-run the
projected_patient_matches_csharp_fixture-style replay against it. The
value-oracle side is ready to receive it.

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_af8e9675-8f5f-4594-99f6-5702afe01240)