ecoportal-api-graphql 1.3.12 → 1.3.14

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 74b442ca224440bee94f3f88522a4233b995d187db1b70ba31a0801e0691d3eb
-  data.tar.gz: 5d5d05fdf46fac5a32a12c5d4c8e47c21b913332bbe04c40a3ab81beeacbab9a
+  metadata.gz: 5cbeb13326afff8c35946fd492b9bd6cd050e28819497b643bb4ea6c4b41caca
+  data.tar.gz: ad4660f8fa032e08d0c5f09b199f280d8b42a4e234144ad2fab4041b154fe835
 SHA512:
-  metadata.gz: 7d667e7ed09fc6ed6fd200695567eb25a8bb5f4f41b3b98882e04d84acd1775c1a17dc7d424e82f26b7f89d4f826bb46c25fddc0ef5fc526e8731aaccd73193b
-  data.tar.gz: 324b54e96de9f7ae82e71bf1b2c0427fa6fd4ed99d0153ec836a85cf68d76d5ce8f8462865b29cddd446015caa2b4a5fcaf940c5c2866970d7814a2d0495a73b
+  metadata.gz: 7337308796e0a6800e9dd678d8b9317978d4cf13f6514b2ba95e5d6eaac95b9833be786ca573b7e59613660077aaa78c808a62c4bbef0c9e2f1a08e0c752e857
+  data.tar.gz: 602edaca4d582eeb876549bba42735fc17fc07d832de713fd3ba84234cc2a876aea876beb51c4fb54eef3faf5a334b889443d922d9c6debe196545389b2715e6

data/.ai-assistance/bridge/archive/oscar-a1b2c3d-gitlab-mcp-doc-update.inbox.md

@@ -1,29 +1,29 @@
-# TASK: Update gitlab-mcp.md with new PAT scopes and rotation info
-
-STATUS: PENDING
-CREATED: 2026-06-04T00:00:00Z
-FROM: cowork
-TO: code
-
-## File to update
-
-`.claude/integrations/gitlab-mcp.md`
-
-## Changes
-
-### Scopes table — replace entirely
-
-| `read_api`       | Read MRs, issues, diffs, repository metadata |
-| `read_repository`| Clone and read repository contents           |
-| `create_runner`  | Register GitLab CI runners                   |
-| `ai_features`    | Access GitLab AI/Duo endpoints               |
-
-### PAT creation note — replace
-
-Enable **rotation** at creation time.
-**Token rotation:** Current token expires **April 2027**. When rotating, update
-in both `.env` and `claude_desktop_config.json`.
-
-### "What it doesn't provide" — remove pipeline management item
-
-`create_runner` + `ai_features` scopes now partially cover CI and AI capabilities.
+# TASK: Update gitlab-mcp.md with new PAT scopes and rotation info
+
+STATUS: PENDING
+CREATED: 2026-06-04T00:00:00Z
+FROM: cowork
+TO: code
+
+## File to update
+
+`.claude/integrations/gitlab-mcp.md`
+
+## Changes
+
+### Scopes table — replace entirely
+
+| `read_api`       | Read MRs, issues, diffs, repository metadata |
+| `read_repository`| Clone and read repository contents           |
+| `create_runner`  | Register GitLab CI runners                   |
+| `ai_features`    | Access GitLab AI/Duo endpoints               |
+
+### PAT creation note — replace
+
+Enable **rotation** at creation time.
+**Token rotation:** Current token expires **April 2027**. When rotating, update
+in both `.env` and `claude_desktop_config.json`.
+
+### "What it doesn't provide" — remove pipeline management item
+
+`create_runner` + `ai_features` scopes now partially cover CI and AI capabilities.

data/.ai-assistance/bridge/archive/oscar-c912c25-gemini-design-review.inbox.md

@@ -1,42 +1,42 @@
-# TASK: Gemini design review of CoWork↔Code bridge architecture
-STATUS: PENDING
-CREATED: 2026-06-03T00:00:00Z
-FROM: cowork
-TO: code
-
-## Context
-We have designed a file-based bridge system for bidirectional communication between
-Claude in CoWork and Claude Code. The bridge lives in .claude/bridge/ inside a git repo.
-
-Architecture summary:
-- Inbox/outbox pattern with UUID+username prefixed filenames (no merge conflicts)
-- Scripts (bash + TypeScript) handle file ops, env detection, UUID gen — offloading work from AI tokens
-- CLAUDE.md files in each subfolder give each agent scoped instructions
-- capabilities/ folder tracks what each environment can do, with a dated assumptions log
-- conventions/ folder defines gitignore rules and instruction file structure
-- capabilities-check.ts runs periodically using Haiku to flag stale assumptions
-
-Key design decisions:
-- Each agent checks capabilities before bridging (only bridge what you can't do yourself)
-- Archive is committed to git — it's the audit trail
-- Draft tasks (.draft.md) are gitignored — local-only until pushed
-- Code processes only its own username-prefixed tasks
-
-## Request
-Use the Gemini connector (or Gemini API if available) to get an independent review of
-this architecture. Ask Gemini:
-
-1. What are the weaknesses or failure modes of this design?
-2. Is the token-offloading strategy (scripts vs AI prose) well-scoped, or are there gaps?
-3. Are there simpler or more robust alternatives for any part of this?
-4. Anything we haven't considered — especially around git workflows, multi-agent coordination,
-   or long-term maintenance?
-
-If Gemini connector is not available, use web search to find prior art on
-file-based agent coordination patterns and report what you find.
-
-## Expected output
-- Gemini's (or research-based) critique: weaknesses, gaps, alternatives
-- Your own assessment: do you agree with the critique? What would you change?
-- Specific suggested amendments to the design (if any)
-- Update capabilities/connectors.md with Gemini connector status after attempting this
+# TASK: Gemini design review of CoWork↔Code bridge architecture
+STATUS: PENDING
+CREATED: 2026-06-03T00:00:00Z
+FROM: cowork
+TO: code
+
+## Context
+We have designed a file-based bridge system for bidirectional communication between
+Claude in CoWork and Claude Code. The bridge lives in .claude/bridge/ inside a git repo.
+
+Architecture summary:
+- Inbox/outbox pattern with UUID+username prefixed filenames (no merge conflicts)
+- Scripts (bash + TypeScript) handle file ops, env detection, UUID gen — offloading work from AI tokens
+- CLAUDE.md files in each subfolder give each agent scoped instructions
+- capabilities/ folder tracks what each environment can do, with a dated assumptions log
+- conventions/ folder defines gitignore rules and instruction file structure
+- capabilities-check.ts runs periodically using Haiku to flag stale assumptions
+
+Key design decisions:
+- Each agent checks capabilities before bridging (only bridge what you can't do yourself)
+- Archive is committed to git — it's the audit trail
+- Draft tasks (.draft.md) are gitignored — local-only until pushed
+- Code processes only its own username-prefixed tasks
+
+## Request
+Use the Gemini connector (or Gemini API if available) to get an independent review of
+this architecture. Ask Gemini:
+
+1. What are the weaknesses or failure modes of this design?
+2. Is the token-offloading strategy (scripts vs AI prose) well-scoped, or are there gaps?
+3. Are there simpler or more robust alternatives for any part of this?
+4. Anything we haven't considered — especially around git workflows, multi-agent coordination,
+   or long-term maintenance?
+
+If Gemini connector is not available, use web search to find prior art on
+file-based agent coordination patterns and report what you find.
+
+## Expected output
+- Gemini's (or research-based) critique: weaknesses, gaps, alternatives
+- Your own assessment: do you agree with the critique? What would you change?
+- Specific suggested amendments to the design (if any)
+- Update capabilities/connectors.md with Gemini connector status after attempting this

data/.ai-assistance/projects/compat-layer-audit/COMPAT_AUDIT.md

@@ -0,0 +1,244 @@
+# GraphQL COMPAT Layer Audit — contract fidelity vs ecoportal-api-v2
+
+> READ-ONLY audit. No code changed, no git touched. Date: 2026-07-08.
+> Scope: every place the GraphQL gem re-expresses a v2 public API, measured against the
+> v2 contract as source of truth. Consumers surveyed: `multi_org_api/*/config/ooze_cases`,
+> eco-helpers `usecases/graphql` + `OozeRedirect` + `ooze_samples`.
+
+---
+
+## 1. Executive verdict — AD-HOC PATCH, not a faithful mirror
+
+Oscar is **right**. The compat layer is a set of reactive, per-symptom patches, not a
+contract-faithful mirror of the v2 API. Concrete evidence:
+
+1. **Same method, three different return-type decisions, no shared contract.** `get_by_name`
+   is a COLLECTION in v2 for components, forces, and bindings, but a SINGLE for stages. The
+   gem got forces (`base/force/collection.rb:16` → `select`), bindings
+   (`base/force/binding_collection.rb:19` → `select`), and stages
+   (`compat/stage_collection.rb:34` → `find`, correct) right — but got **components wrong**
+   (`base/page/data_field/collection.rb:35` → `find`) and **sections' `get_by_heading` wrong**
+   (`base/page/section_collection.rb:31` → `find`, v2 is `select`). Three files, four
+   independent return-type choices. A faithful mirror would have one rule per v2 method; this
+   has ad-hoc choices that happen to match in some files and not others.
+
+2. **The downstream consumer already contains a workaround for the gem's wrong return type.**
+   eco-helpers `OozeRedirect#with_fields` wraps the component lookup:
+   `[collection.get_by_name(label)].compact` (`ooze_redirect.rb:187`) — i.e. it treats
+   `get_by_name` as returning a SINGLE and re-wraps it into an array to fake the v2 collection
+   contract. That is a patch compensating for a patch. When the gem is made faithful (returns a
+   collection), this line double-wraps → `[[Field]]`. Whack-a-mole in the flesh.
+
+3. **Two conflicting `#components` definitions on the same object.** `Concerns::PageCompat#components`
+   returns `dataFields || []` (`page_compat.rb:22`); `Concerns::DataFieldAccess#components`
+   returns `field_collection` (`data_field_access.rb:22`). Both are `include`d in
+   `Interface::BasePage` (`base_page.rb:6-7`), DataFieldAccess second so it wins — but the dead
+   PageCompat version returning a raw array is a fossil of an earlier, incompatible attempt.
+
+4. **Methods the v2 contract guarantees are simply absent** (not deliberately dropped —
+   nobody enumerated the contract): `DataField::Collection` has no `get_by_id`, no
+   `get_by_type` returning a `reference?`-style API, no `unattached`/`multi_section`;
+   `SectionCollection` has no `get_by_id`, no `ordered`-by-weight, no `between`. Consumers call
+   `components.get_by_id` and `sections.get_by_id` today (§3).
+
+5. **`components.add` has different semantics** — v2 `upsert!`s into the live collection so a
+   later `get_by_name` finds it; the gem stashes into a private `@additions` array
+   (`collection.rb:53-60`) that `each`/`get_by_name` never see.
+
+The through-line: each method was added when a specific script broke, choosing whatever return
+shape that one script needed — never derived from the v2 method's documented contract. That is
+the definition of ad-hoc.
+
+---
+
+## 2. Divergence catalog
+
+Severity: **S1** = silent wrong result / breaks live consumers; **S2** = raises / missing method;
+**S3** = latent (no current consumer but contract-divergent).
+
+| # | Method | v2 contract (file:line) | gem compat (file:line) | Divergence | Sev | Affected consumers |
+|---|--------|-------------------------|------------------------|------------|-----|--------------------|
+| C1 | `components.get_by_name(name, type:)` | `select` → **Array** (`v2/page/components.rb:37`) | `find` → **single DataField** (`base/page/data_field/collection.rb:35`) | Return type: collection vs single | **S1** | act-gov `.first`/`.last`, farmers `.first`, and ~120 `components.get_by_name(...).first` call-sites across multi_org_api (twg, tng, briscoes, alexander, argenta, whittlesea…); eco-helpers `ooze_redirect.rb:184,187` |
+| C2 | `sections.get_by_heading(h, mild:)` | `ordered.select` → **Array** (`v2/page/sections.rb:61`) | `find` → **single Section** (`base/page/section_collection.rb:31`) | Return type + drops `mild:` + no weight-ordering | **S1** | `tng_env_update_case.rb:19` (`.get_by_heading("Details").first`) |
+| C3 | `components.get_by_id(id)` | `find` → single (`v2/page/components.rb:21`) | **absent** on `DataField::Collection` | Missing method → `NoMethodError` | **S2** | `event_changes_case.rb:50` (`components.get_by_id(fld.reference_id)`); eco-helpers `ooze_update_case.rb:10` |
+| C4 | `sections.get_by_id(id)` | `find` → single (`v2/page/sections.rb:46`) | **absent** on `SectionCollection` | Missing method → `NoMethodError` | **S2** | `TnG_Active_sitefix_part2_case.rb:106` |
+| C5 | `components.add(...)` | `upsert!` into live collection; found by later `get_by_name`/`each` (`v2/page/components.rb:53`) | stashes in private `@additions`; NOT in `@fields`; later `get_by_name`/`each` miss it (`collection.rb:53-60`) | Mutation semantics diverge | S2 | any multi-step add-then-read script; `add` kwargs also differ (`id:` required, `doc:` shape) |
+| C6 | `sections.get_by_type(t)` | `ordered.select` → Array (`v2/page/sections.rb:53`) | `select` → Array but **not weight-ordered** (`section_collection.rb:25`) | Ordering: v2 orders by weight, gem uses response order | S3 | ordering-sensitive section scripts (latent) |
+| C7 | `components.get_by_type(t)` | `select` → Array, no ordering (`v2/page/components.rb:28`) | `select` → Array (`collection.rb:27`) | **Match** (return type) | ok | argenta `remove_edit_events_case.rb:21,29` (uses `.select` on result — works only because both are Arrays) |
+| C8 | `forces.get_by_name(name)` | `select` → Array (`v2/page/forces.rb:36`) | `select` → Array (`base/force/collection.rb:16`) | **Match** | ok | all `forces.get_by_name(...).first` sites |
+| C9 | `force.bindings.get_by_name(name, type:)` | `select` → Array (`v2/page/force/bindings.rb:102`) | `select` → Array but **drops `type:` kwarg** (`binding_collection.rb:19`) | Partial: arity narrower | S3 | bindings callers pass name only today; `type:` unused |
+| C10 | `stages.get_by_name(name)` | `find` → single (`v2/page/stages.rb:17`) | `find` → single (`compat/stage_collection.rb:34`) | **Match** | ok | eco-helpers `ooze_base_case.rb:109,144`, `register_export_case.rb:137` |
+| C11 | `stages[id_or_name]` | v2 CollectionModel `[]` by key (id) | id **or** name (`stage_collection.rb:27-30`) | Superset (name-fallback) — benign but non-contract | S3 | eco-helpers `stages[id] || stages.get_by_name` (belt-and-braces) |
+| C12 | `forces.get_by_id`, `.ordered`, `.bindings_by_reference` | present (`v2/page/forces.rb:29,64,20`) | **absent** on gem `Force::Collection` | Missing methods | S3 | not called by surveyed consumers (latent) |
+| C13 | `bindings.get_by_id / get_by_type / get_by_reference / reference? / by_name / by_reference` | present (`v2/page/force/bindings.rb:82,92,68,61,26,42`) | **absent** on gem `BindingCollection` | Missing methods | S3 | not called by surveyed consumers (latent) |
+| C14 | `sections.ordered` (by weight) | `sort_by weight` (`v2/page/sections.rb:86`) | returns `@sections` as-is (`section_collection.rb:41`) | Ordering not applied | S3 | latent |
+| C15 | `page.components` (page-level) | v2 components collection | **two conflicting defs**: PageCompat returns `dataFields`/`[]` array (`page_compat.rb:22`), DataFieldAccess returns `Collection` (`data_field_access.rb:22`); include order (`base_page.rb:6-7`) makes DataFieldAccess win, PageCompat one is dead code | Latent footgun / dead code | S2 | any refactor reordering includes silently swaps behaviour |
+| C16 | `entry.components.get_by_name(...).detect{…}` | Array#detect works on v2 collection | gem returns single → `.detect` = `Enumerable#detect` on a **DataField** (iterates its doc?) | Return-type breakage | **S1** | `risks_migration_case.rb:89` (`.get_by_name("Review frequency:").detect{…}`) |
+| C17 | `force.bindings.get_by_name(x).empty?` | Array#empty? | gem Array → ok (C8/C9 correct) | ok | tng `tng_env_update_case.rb:112` |
+
+### Folded-in prior findings (verified against current code)
+
+These are not `get_by_name`-style return-type bugs but are part of the same "compat built ad hoc"
+thread — the read/write CONVERTER contract was never systematically mirrored. Cross-referenced
+against `.ai-assistance/code/model_input_mapping/SYNTHESIS.md` (2026-07-07). **Note:** SYNTHESIS
+marks several as FIXED on `feature/model-input-fixes` (current branch); status below reflects that.
+
+| # | Prior finding | Current status (verified) | File:line |
+|---|---------------|---------------------------|-----------|
+| P1 | `passarray`/`embeds_many` don't diff via `as_update` (otherTags, locations, filterTags) | **FIXED** — `DIFF_CLASS = Diffable::LeafDiffService` now on `Interface::BasePage` | `interface/base_page.rb:13` |
+| P2 | `IdDiff` set-diff machinery non-functional (ContractorEntity/Action) | Reported FIXED via `id_diff_fields` macro (SYNTHESIS §3.2); **not re-verified in this pass** — flagged for confirm | — |
+| P3 | File/Image/Contractor readers use write-key → `[]` | Reported FIXED (SYNTHESIS §3.3); Image fragment `images[].id` was the blocker | `base/page/data_field/{file_field,image_gallery,contractor_entities}.rb` |
+| P4 | DataField read-key ≠ write-key (shape asymmetry) | Partly FIXED (CrossReference was template); File/Image/Contractor per P3 | `.ai-assistance/code/refactoring/datafield-readwrite-shape-asymmetry.md` |
+| P5 | `SnakeCamelAccess` is a one-way method_missing shim, no specs | **STILL TRUE** — `concerns/snake_camel_access.rb`; no spec file exists (`Glob spec/**/snake_camel*` → none). One-way (snake→camel only); silently no-ops single-word methods (`parts.length < 2` → returns as-is) | `concerns/snake_camel_access.rb:50-54` |
+
+---
+
+## 3. Comprehensive fix plan (contract-faithful) + spec risk
+
+The organising principle: **derive each collection method from the v2 method it mirrors, not from
+the one script that broke.** Recommend a small shared helper module so components/sections/forces/
+bindings collections share one contract per method name.
+
+### Fix C1 — `DataField::Collection#get_by_name` → collection (`select`)
+
+Faithful fix: return `pool.select { … }` (mirror `v2/page/components.rb:37`), keeping `type:`.
+
+**Risks these EXISTING gem specs (they assume single return):**
+- `spec/.../base/page/data_field_spec.rb:397-399` — `coll.get_by_name('name').id` → must become `.first.id`
+- `data_field_spec.rb:408` — `coll.get_by_name('Name').value = 'Bob'` → `.first.value =`
+- `data_field_spec.rb:419` — same
+- `data_field_spec.rb:463` — `field = coll.get_by_name('Name')` → `.first`
+- `base/page/phased/stage_spec.rb:72` — `stage.components.get_by_name('Description').value` → `.first.value`
+- `compat/stage_collection_spec.rb:92` — `stage.components.get_by_name('Description').value` → `.first.value`
+- `compat/stage_view_spec.rb:57` — `view.components.get_by_name('Summary').value` → `.first.value`
+- `input/page/update_spec.rb:136` — `page_with_fields.components.get_by_name('Note').value = 'New'` → `.first.value =`
+- `integration/toocs_submit_replay_spec.rb:38` — `page.components.get_by_name('Coding completed by:')` → `.first`
+
+These 9 spec sites LOCK IN the wrong behaviour and must be updated in lockstep with the fix
+(add `.first`). They also confirm the gem's own test suite was written to the ad-hoc behaviour,
+not the v2 contract.
+
+**Also requires a coordinated eco-helpers change:** `ooze_redirect.rb:184-187` — line 187
+`[collection.get_by_name(label)].compact` must become `collection.get_by_name(label)` (already an
+Array), and line 184-185 `field = collection.get_by_name(label); … [field] : []` must select over
+the collection. This is the cross-repo lockstep the audit brief warns about: a "just remove
+`.first`" workaround in org scripts is itself a dirty patch that re-breaks here.
+
+### Fix C2 — `SectionCollection#get_by_heading` → collection (`select`), add `mild:`, order by weight
+
+Faithful: `ordered.select { same_string?(s.heading, h, mild: mild) }`. Add a `same_string?`
+helper (case-insensitive; `mild:` = alnum-only compare per v2). Requires §Fix-C14 (`ordered` by
+weight) for exact parity.
+
+**Spec risk:** no existing gem spec asserts `get_by_heading` (Grep found none) → **no green
+specs go red.** Add new specs (§4). Consumer `tng_env_update_case.rb:19` already does `.first`, so
+it starts working correctly.
+
+### Fix C3 / C4 — add `get_by_id` to `DataField::Collection` and `SectionCollection`
+
+`find { |x| x.id == id }` (mirror v2). **No spec risk** (new methods). Add coverage.
+
+### Fix C5 — `components.add` upserts into the live collection
+
+Faithful: push the built field into `@fields` (or an upsert-by-id) so later `get_by_name`/`each`
+find it, and keep `dirty_additions` sourced from those. **Spec risk:** check `data_field_spec.rb`
+add-section (`:451-465`) — the deletion test reads `get_by_name('Name')` (existing field, fine);
+the add tests assert `dirty_additions` only, so upserting into `@fields` needs a guard that
+`dirty_inputs` (updates) does not double-count additions. Design the split carefully; lock with a
+"add then get_by_name finds it" spec.
+
+### Fix C6 / C14 — order `get_by_type`/`ordered` by weight in `SectionCollection`
+
+Only if sections carry a weight in the GraphQL doc (verify fragment exposes it; if not, response
+order is the only signal and this stays a documented gap). **No current spec risk.**
+
+### Fix C9 / C12 / C13 — fill missing force/binding contract methods + `type:` on bindings
+
+Add `get_by_id`, `get_by_type`, `get_by_reference`, `reference?`, `by_name`, `by_reference`,
+`ordered`, `bindings_by_reference`, and honour `type:` in `binding.get_by_name`. These are S3
+(no live consumer) — do them to make the mirror complete, not urgently. **No spec risk.**
+
+### Fix C15 — delete the dead `PageCompat#components`
+
+Remove `PageCompat#components` (`page_compat.rb:21-24`); it is shadowed and returns the wrong
+shape if include order ever changes. `page_compat_spec.rb:39-43` asserts `components` is a
+`DataField::Collection` — that stays green (DataFieldAccess provides it). **No spec risk.**
+
+### Fix P5 — add specs (and ideally make two-way) for `SnakeCamelAccess`
+
+At minimum add characterization specs. Consider reusing eco-helpers' polished hash-level
+snake/camel module rather than the bespoke `method_missing` shim (per memory
+`project_snake_camel_access`). Scope decision for Oscar.
+
+### Recommended structural change (kills the class of bug)
+
+Extract a shared `Concerns::V2CollectionContract` (or a `Base::Page::CollectionModel`) that
+defines `get_by_id` (single), `get_by_name`/`get_by_heading`/`get_by_type` (collection, per v2),
+`ordered`, `same_string?(mild:)` **once**, and have DataField/Section/Force/Binding collections
+include it. This turns "one return-type decision per file" into "one contract, four includes" —
+the actual remedy for the ad-hoc philosophy.
+
+---
+
+## 4. Test strategy
+
+### Gem rspec additions (lock the CONTRACT, not the current behaviour)
+- **Return-type contract specs**, one per collection, asserting `get_by_name`/`get_by_heading`
+  return `Array` (C1, C2) and `get_by_id` return a single (C3, C4). Assert `.first` on a
+  multi-match returns the first; assert empty match returns `[]` (not nil) for the collection
+  methods — this is the exact shape act-gov `.first`/`.last` and farmers `.first` depend on.
+- **Add-then-find spec** (C5): `coll.add(id:…){…}; expect(coll.get_by_name(label)).to include(the added)`.
+- **`mild:` parity spec** for `get_by_heading` (C2).
+- **Cross-object consistency meta-spec:** a single spec that asserts all four collections agree
+  on the return type of `get_by_name` (guards against future drift — the root cause here).
+- Update the 9 spec sites listed under Fix-C1 to `.first` in the SAME commit as the fix.
+- Add `SnakeCamelAccess` characterization spec (P5).
+
+### eco-helpers spec additions
+- Update `OozeRedirect#with_fields` (`ooze_redirect.rb:184-189`) and add a spec proving it
+  returns the same shape (Array) whether the field exists or not, against a faithful collection.
+- Regression spec replaying an act-gov-style `get_by_name(...).first` / `.last` through the
+  OozeRedirect path.
+
+### Integration coverage (parity harness, training mini-site)
+- On the all-21-fields template mini-org, run the A/B parity harness (memory
+  `project_parity_test_plan`): execute one representative ooze case using `.get_by_name(...).first`
+  and `.get_by_heading(...).first` against BOTH v2 and GraphQL, assert identical selected field
+  IDs and identical emitted mutation input. **Needs live creds** (mini-site API token) — the only
+  part of this plan that cannot run in CI without secrets.
+- Replay act-gov `20240130_act_disease_title_update_case.rb` (`.first`+`.last`) and the farmers
+  case in `-simulate` mode post-fix to confirm no `.first`-on-single or double-wrap breakage.
+
+---
+
+## 5. Open questions / could not verify
+
+1. **P2/P3 fix status not re-verified.** SYNTHESIS says the IdDiff macro and File/Image/Contractor
+   readers were fixed on this branch; I did not re-open those files this pass. Confirm before
+   relying on them.
+2. **Section weight in the GraphQL fragment.** C6/C14 (order-by-weight) only achievable if the
+   section fragment actually returns a `weight`/ordering field — not confirmed. If absent, response
+   order is the contract and these stay documented gaps.
+3. **`components.add` write path.** Whether an added field can even be created via the current
+   `dataFields.updates`/additions mutation shape without a server-side `buildFromTemplate` ID is a
+   separate question (the collection comment at `collection.rb:47` says it "must reference an
+   existing server-side ID"). Faithful `add` semantics may be bounded by the mutation API.
+4. **Full green-suite baseline.** I did not run `bundle exec rspec`; the 9 spec sites are
+   identified statically. Run the suite before/after to get exact red counts.
+5. **`get_by_type` ordering for components (C7).** v2 does not order components by weight either,
+   so gem matches — but confirm no consumer relies on component order.
+
+---
+
+## Appendix — files inspected
+
+v2 contract: `ecoportal-api-v2/lib/ecoportal/api/v2/page/{components,forces,sections,stages}.rb`,
+`.../page/force/bindings.rb`.
+Gem compat: `lib/.../base/page/data_field/collection.rb`, `.../base/page/section_collection.rb`,
+`.../base/force/{collection,binding_collection,force}.rb`,
+`.../compat/{pages,registers,stage_collection,stage_view}.rb`,
+`.../concerns/{page_compat,data_field_access,snake_camel_access,deprecation}.rb`,
+`.../interface/base_page.rb`.
+Consumers: `multi_org_api/*/config/ooze_cases/*` (grep, ~120 sites),
+`eco-helpers/lib/eco/api/usecases/graphql/compat/ooze_redirect.rb`, `.../ooze_samples/*`.
+Prior findings: `.ai-assistance/code/model_input_mapping/SYNTHESIS.md`.