openehr-rails 0.7.0 → 0.8.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 065a9ba44f893adaea9e6c0ccf6f3c5f8a0af8c8c3897379cd008e5642e99a7a
-  data.tar.gz: 98f81ad0baf2b086e2193102c25804b3affcd2fa1ffb4c0730952d6a916e3a58
+  metadata.gz: a30bd4a561f8193c0603c1e43e1873e1c8835d2e7c418b95c429ac6e2b397e83
+  data.tar.gz: 180145cf2e294cc68ae84ddc35b147e07e6fb52f99062d14f8df3cb0e306108e
 SHA512:
-  metadata.gz: 42353942db8a02b901e3727a85446fe1995f3c953fd33f3da2dfea68d7018b533de95b97494db856593df77ccbacd8d57f0f4bb4cdcedee086da6c4e44035a04
-  data.tar.gz: 4fd7e793d2d77230e585dcf06204147926d3b36a86a576525614d19395930f80b4fe38bc0b534de5a0f6b26e98e0859d5c8275ce865a1efedf3aa942dc1d272e
+  metadata.gz: 46b84468c263139208e522562831d103cd43d8d3c865aa274fe7cf6db7ebe486fa67329b4e175564a9fc0f94d0a0a4454d679f3d42735ac4c7214b739fa7ba3a
+  data.tar.gz: dc189063ef16d43253287e9fed472bdc7d69b0b0c72fb5f393f772cf9adbe596ebd24b6dbea57514435c3a6afe8cdba048fd4b1c3c2e73e39b4a17315ad03b6d

data/.github/workflows/release.yml

@@ -26,6 +26,8 @@ jobs:
         run: bundle exec rake release:check
       - name: Build gem
         run: bundle exec rake build
+      - name: Record sha256
+        run: sha256sum pkg/*.gem | tee pkg/SHA256SUMS
       - name: Upload gem artifact
         uses: actions/upload-artifact@v7
         with:

data/.ruby-version

@@ -1 +1 @@
-4.0.6
+4.0.7

data/CHANGELOG.md

@@ -7,6 +7,63 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.8.0] - 2026-10-12
+
+> **Upgrade note.** A stored Composition holding a `SECTION` or an `INSTRUCTION`
+> (with its `ACTIVITY`s) now reads back through `to_rm` and AQL; the ones 0.7.1
+> skipped with `openehr-rails AQL: skipping composition uid=...` are exactly the
+> ones that become visible, so query row counts can grow. Two injected defaults
+> are approximations until a later release persists them as columns: an
+> INSTRUCTION without a stored narrative reads back with its node name as
+> `narrative`, and every ACTIVITY with `action_archetype_id` `'/.*/'`.
+
+### Added
+- `RmObjectBuilder` rebuilds `SECTION`, `INSTRUCTION` and `ACTIVITY` nodes (and
+  every CARE_ENTRY's `protocol`), so compositions holding them -- a referral's
+  `service_request` with its requester/receiver under `protocol[...]`, entries
+  nested in a `SECTION` -- become readable through `to_rm` and queryable by AQL
+  instead of being skipped with the 0.7.1 warning (#45). Two values are
+  **approximations** because the graph does not carry them yet: an INSTRUCTION
+  without a stored narrative gets its node name as `narrative`, and every
+  ACTIVITY gets `action_archetype_id` `'/.*/'` (any ACTION archetype). Both will
+  be persisted as columns in a later release. `ACTION`, `ITEM_SINGLE` and
+  `ITEM_TABLE` are still unsupported (skipped with the warning).
+- `FieldExtractor` fields carry `rm_type_alternatives`: every value type the OPT
+  allows for the ELEMENT, in OPT order (e.g. `["DV_TEXT", "DV_CODED_TEXT"]` for
+  `problem_diagnosis` at0002). Additive; the chosen `rm_type` is unchanged. Lets a
+  host app tell an OR-constrained coded text (free text allowed) from a coded-only
+  one instead of rendering an empty select (#52, anlage #33).
+
+### Fixed
+- An entry with no extracted leaves (today every `INSTRUCTION`, see #47) no
+  longer gets a profile consisting of the archetype `code` rules and an empty
+  `component` slicing header; it is skipped and reported through `#skipped`
+  with a message saying the entry has no leaves, whatever its resource (#49).
+
+## [0.7.1] - 2026-09-25
+
+> **Upgrade note.** AQL now skips a stored composition that holds an RM type
+> `RmObjectBuilder` cannot rebuild, with a warning
+> (`openehr-rails AQL: skipping composition uid=...`), instead of failing every
+> query in the store. No host-app change is needed; if that line appears in
+> your log, the composition is a #45 case (SECTION / INSTRUCTION / ACTIVITY
+> read-back, next minor release).
+
+### Fixed
+- A single-leaf entry mapped to a resource other than `Observation` and without a
+  `TypeMap::ENTRY_ELEMENT_MAPS` row no longer produces `<Resource>.value[x]`, which
+  `Condition`/`ServiceRequest`/`Procedure`/`Encounter` do not have; it is skipped and
+  reported through `#skipped` like the multi-leaf case since 0.7.0 (#38). The
+  `UnsupportedProfileError` message now names both missing elements.
+- AQL no longer fails for the whole store when one stored composition cannot be
+  rebuilt as RM objects (a node type outside `RmObjectBuilder::TYPE_CLASSES`,
+  such as `SECTION`/`INSTRUCTION`, or an RM constructor rejecting stored data).
+  `DatasetAdapter` now warns (`Rails.logger` when present, else stderr), naming
+  the composition uid and the cause, and skips that composition; queries on the
+  rest of the store return their rows. `RmObjectBuilder` raises
+  `OpenehrRails::Rm::UnsupportedRmTypeError` (composition uid, node path,
+  rm_type) instead of an accidental `NoMethodError` (#44).
+
 ## [0.7.0] - 2026-09-10
 
 > **Upgrade note.** Regenerate `app/fhir/profiles/*.json`. `Condition.component`

data/CLAUDE.md

@@ -61,6 +61,13 @@ documentation files and `lib/` was byte-identical - but nothing in the release
 path caught it. Measurements in `docs/reports/fsh-generator-log.md` R8; the
 matching `release:check` guard is `skoba/openehr-rails#34`.)
 
+**Local dev Ruby tracks the patch release CI builds with.** `.ruby-version`
+moved 4.0.6 -> 4.0.7 (2026-10-12) so a local rebuild at the tag stamps the same
+`rubygems_version` (4.0.20) as `ruby/setup-ruby`'s ruby 4.0 image did for 0.7.1,
+whose `metadata.gz` differed from the local rebuild by that one line
+(`docs/reports/referral-upstream-log.md` R2). The cross-check still judges by
+`data.tar.gz`, not the whole-gem sha256: the two toolchains can drift apart again.
+
 **Confirm publication by checksum, not by version number.** RubyGems publishes
 the sha256 it recorded at push time (`/api/v1/gems/openehr-rails.json` `sha`, and
 the `checksum:` field in `https://index.rubygems.org/info/openehr-rails`). The
@@ -225,7 +232,7 @@ This is `openehr-rails`, a Rails engine gem that turns an openEHR Operational Te
 
 ## Development Notes
 
-- Ruby 3.3+ required (raised from 3.0 in 2026-08 to track the `openehr` gem dependency dropping Ruby 3.2 support at EOL); CI matrix covers 3.3/3.4/4.0, local dev pinned via `.ruby-version` (currently 4.0.6)
+- Ruby 3.3+ required (raised from 3.0 in 2026-08 to track the `openehr` gem dependency dropping Ruby 3.2 support at EOL); CI matrix covers 3.3/3.4/4.0, local dev pinned via `.ruby-version` (currently 4.0.7)
 - Rails 7.0+ and Rails 8.x supported (CI matrix: `gemfiles/rails_{7_2,8_0,8_1}.gemfile`; demo app runs on Rails 8.1)
 - URI compatibility workaround implemented for Ruby 3.4
 - `ostruct` is an explicit development dependency — it left Ruby's default gems as of 4.0, and a couple of specs use `OpenStruct` as a lightweight test double

data/docs/backlog.md

@@ -74,6 +74,26 @@ that verification is deferred to the next real release (>= 0.5.0), not simulated
 
 ## Release automation
 
+- **`release.yml` records no sha256 of the built `.gem`** (found at the 0.7.0
+  release, 2026-09-10, `docs/reports/fsh-generator-log.md` R14). The only digest in
+  the run log is `actions/upload-artifact`'s "SHA256 digest of uploaded artifact",
+  which hashes the uploaded archive, not the gem file, so `CLAUDE.md`'s "compare
+  against the value recorded for that run" cannot be followed literally; the
+  tag-rebuild cross-check is what pins the bytes today. Add a "Record sha256" step
+  after `rake build` (`sha256sum pkg/*.gem`), as openehr-ruby's `release.yml` has.
+  CI-only change; needs a PR, no Issue. **In PR #51 as `1410274` (2026-10-12,
+  `docs/reports/referral-upstream-log.md` R5)**; first run that prints it will be
+  the `v0.8.0` tag's.
+- **The tag-rebuild cross-check compares `data.tar.gz`, not the whole `.gem`**
+  (0.7.1, 2026-09-25, `docs/reports/referral-upstream-log.md` R2). A `.gem` embeds
+  `rubygems_version` in `metadata.gz`, so a rebuild on a different ruby/rubygems
+  (local 4.0.6/4.0.16 vs CI 4.0.7/4.0.20) yields a different whole-gem sha256 with
+  byte-identical shipped files. Procedure: `tar xf` both gems, compare
+  `sha256sum data.tar.gz` (must match) and `diff` the gunzipped `metadata.gz`
+  (only `rubygems_version` may differ). 0.7.0's whole-gem match was a coincidence
+  of equal toolchains. Fold this into `CLAUDE.md`'s Release convention together
+  with the "Record sha256" step above.
+
 **Done (2026-08-23, PR #28)** — kept below for the original rationale; see the CI
 status entry above for verification details.
 
@@ -122,6 +142,14 @@ status entry above for verification details.
 
 ## Fixture conventions
 
+- **`spec/templates/sample_blood_pressure.opt` does not parse** -- `OpenehrRails::Opt.parse`
+  raises `ArgumentError: invalid archetype id form` from
+  `OpenEHR::RM::Support::Identification::ArchetypeID` under openehr 2.4.2 *and* 2.4.3
+  (measured 2026-09-10 while checking fixtures for #38), and no spec, script or
+  generator references the file. Orphan fixture: either find which archetype id in
+  it is malformed and decide whether that is an openehr-ruby parser gap worth an
+  upstream Issue, or delete the file. Not touched in 0.7.0.
+
 - **Licensed terminology-code literals in spec expectations: keep minimal, cite the
   source fixture's file:line.** Adopted from Anlage's C2 firewall precedent (SNOMED
   CT is a licensed terminology; reproducing its codes verbatim in more places than

data/docs/design/multi-leaf-non-observation-plan.md

@@ -365,3 +365,34 @@ Still **minor**, on top of §8.5: `#skipped` and `UnsupportedProfileError` are
 new public API; the `category` anchor and the `comment` change the JSON facade's
 shape again for `EVALUATION` entries. `CHANGELOG.md` `[Unreleased]` updated in
 the same change.
+
+## 9.7 #38 (2026-09-10 ruling): the decision point widened to any leaf count
+
+The ruling on 9.5 allowed #38 to ride in 0.7.0 if it stayed on the same
+decision point, small, and green. It does: `TypeMap.assert_supported!` drops
+its `fields.size <= 1` early return, so *any* entry whose base resource is not
+`Observation` and which has no `ENTRY_ELEMENT_MAPS` row is skipped and
+reported -- a single leaf would have produced `<Resource>.value[x]`, which
+`Condition` / `ServiceRequest` / `Procedure` / `Encounter` lack just as they
+lack `component` (measured: 1 sushi Error on the 9.5 probe). The error message
+now names both missing elements and the leaf count in the singular where it is
+one. Resolution shape (a) bug.
+
+- **Fixture check before widening**: every OPT under `spec/templates/`,
+  `spec/generators/templates/` and `demo_assets/templates/` was listed with
+  `FieldExtractor#entries` -- all single-leaf entries are `OBSERVATION`
+  (`height.v2`, `body_weight.v2`, `heart_rate-pulse.v1`); the only
+  non-`Observation` entry is `problem_diagnosis.v1` (5 leaves, mapped). So no
+  fixture's output changes. (`spec/templates/sample_blood_pressure.opt` does not
+  parse at all -- `ArgumentError: invalid archetype id form` -- under openehr
+  2.4.2 *and* 2.4.3, and no spec references it; pre-existing, noted in
+  `docs/backlog.md`, not touched here.)
+- **Red**: 4 new examples (two per generator, synthetic single-leaf
+  `EVALUATION` entry `openEHR-EHR-EVALUATION.synthetic_single_leaf_test.v1`):
+  **40 examples, 4 failures** across the two spec files.
+- **Green**: the same files 40/0; `spec/openehr_rails/fhir/` 52/0; full suite
+  308/0. Regenerated FSH for `problem_list.opt` + `bmi_calculation.opt`
+  byte-identical to before and **0 Errors** under `sushi` 3.16.0 -- the pin.
+- **Semver**: 0.7.1 (0.7.0 shipped before PR #43 was merged; see log R13); a bug fix (patch) that changes no
+  fixture output, only what an unmapped single-leaf non-`Observation` entry
+  yields (invalid FHIR before, a `#skipped` entry now).

data/docs/design/rm-object-builder-section-instruction-plan.md

@@ -0,0 +1,134 @@
+# Plan: `RmObjectBuilder` reads back SECTION / INSTRUCTION / ACTIVITY
+
+- Status: **explore + plan, awaiting approval** (2026-09-25). No code written.
+- Issue: [#45](https://github.com/skoba/openehr-rails/issues/45) (anlage upstream candidate 15)
+- Log: `docs/reports/referral-upstream-log.md` R1
+- Prerequisite landed as its own fix: #44 / PR #50 (a failing `to_rm` no longer
+  fails the whole store; unknown types raise `UnsupportedRmTypeError`).
+
+## 1. Current behaviour (measured, `file:line` on `master` after PR #50)
+
+**Write side accepts the types.** `Rm::TypeMap::NODE_TYPES`
+(`lib/openehr_rails/rm/type_map.rb:9-26`) lists SECTION, INSTRUCTION, ACTION,
+ACTIVITY (and ITEM_SINGLE, ITEM_TABLE); the STI classes exist
+(`lib/openehr_rails/rm/nodes.rb:10,14,15,18`). `GraphBuilder#infer_type`
+(`lib/openehr_rails/rm/graph_builder.rb:111-122`) maps `activities` -> ACTIVITY and
+`protocol` / `description` -> ITEM_TREE for `_type`-less hashes. `build_children`
+(`:64-79`) persists Hash-valued attributes as child nodes or data-value rows and
+Array-valued ones as ordered children; **String-valued attributes are dropped** --
+so `ACTIVITY.action_archetype_id` never reaches the graph. `INSTRUCTION.narrative`
+(DV_TEXT), `ACTIVITY.timing` (DV_PARSABLE: `text_value` + `formalism`, `:180-181`)
+and `INSTRUCTION.expiry_time` (DV_DATE_TIME) are stored as data-value rows keyed by
+`rm_attribute_name`.
+
+**Read side does not.** `RmObjectBuilder::TYPE_CLASSES`
+(`lib/openehr_rails/rm/rm_object_builder.rb`, 10 entries) has none of them;
+`build_node` sets entry defaults only for Observation / Evaluation / AdminEntry,
+`data` only for `EntryNode`, and never `protocol`, `narrative`, `activities`,
+`description`. After PR #50 such a node raises `UnsupportedRmTypeError` and the
+composition is skipped from AQL with a warning; before it, the whole store failed
+(anlage referral-intake-log R6).
+
+**What the openehr gem (2.4.3) demands of the objects** (`openehr-ruby`
+`lib/openehr/rm/composition/content/`):
+
+| class | mandatory | optional / notes |
+|---|---|---|
+| `Navigation::Section` (`navigation.rb:12-27`) | -- | `items` must be nil or non-empty; `path_attribute :items` |
+| `Entry::Instruction` (`entry.rb:112-138`) | Entry: `language`, `encoding`, `subject`; `narrative` | `activities` nil or non-empty; `expiry_time`, `wf_definition`; CareEntry `protocol`, `guideline_id` (`entry.rb:69-78`); `path_attribute :activities, :protocol` |
+| `Entry::Activity` (`entry.rb:140-171`) | `description`, `action_archetype_id` (non-empty String) | `timing` optional since RM 1.1.0; `path_attribute :description` |
+| `Entry::Action` (`entry.rb:173-204`) | Entry attrs; `time`, `description`, `ism_transition` (with `current_state` validated against the openEHR terminology, `:236-275`) | out of scope here, see section 5 |
+
+`OpenEHR::RM::Composition::Composition` has `path_attribute :content, :context`,
+so objects built with the attributes above are navigable by the AQL engine's
+path evaluator without engine changes.
+
+## 2. Design -- phase A, no schema change
+
+1. `TYPE_CLASSES` gains `SECTION`, `INSTRUCTION`, `ACTIVITY`.
+2. `build_node` gains, per type (each in its own small private helper, because
+   `build_node` already sits at rubocop's AbcSize/complexity limits -- PR #50 had to
+   extract `node_class` for a one-line change):
+   - **Section**: `items` = children built in position order; `nil` when there
+     are none (the constructor rejects `[]`).
+   - **Instruction**: the same entry defaults as the other entries
+     (`language` / `encoding` / `subject`; extend the `is_a?` list);
+     `narrative` = the `narrative` data-value row as DvText, **defaulting to the
+     node's name** when the row is absent (an injected default, documented like
+     `language`); `activities` = children with `rm_attribute_name == 'activities'`,
+     `nil` when none; `expiry_time` when its row exists.
+   - **Activity**: `description` = the `description` child (ITEM_TREE) -- no
+     default: a missing description is an RM-conformance failure and surfaces
+     through #44's warning; `timing` = the `timing` row as
+     `OpenEHR::RM::DataTypes::Encapsulated::DvParsable` when present;
+     `action_archetype_id` = the injected default `'/.*/'` (the RM's "any ACTION
+     archetype" pattern) because the graph cannot carry it yet (section 5).
+   - **`protocol` for every CareEntry** (Observation, Evaluation, Instruction):
+     `attrs[:protocol] = build_node(protocol child)` when present. Same
+     mechanism, and it is where `jp_referral` keeps 紹介先/紹介元
+     (`service_request` `protocol[at0008]`, anlage memory of 2026-09-25) -- without
+     it the INSTRUCTION would be readable but its most-queried data not.
+3. `UnsupportedRmTypeError` keeps covering ACTION, ITEM_SINGLE, ITEM_TABLE.
+
+Injected defaults are listed in the class comment next to the existing ones.
+
+## 3. Spec plan (t-wada: red before green), resolution shape (b) enhancement
+
+- **Fixture**: a spec-level synthetic canonical hash (invented ids, stated in the
+  comment with this section as design authority; no real canonical JSON with
+  SECTION/INSTRUCTION exists in this repo -- anlage's is hand-mapped and outside):
+  COMPOSITION whose `content` is `[SECTION { items: [EVALUATION { data: ITEM_TREE {
+  items: [ELEMENT DV_TEXT] } }] }, INSTRUCTION { narrative, protocol: ITEM_TREE {
+  items: [ELEMENT DV_TEXT] }, activities: [ACTIVITY { description: ITEM_TREE {
+  items: [ELEMENT DV_TEXT] }, timing: DV_PARSABLE }] }]`, committed with
+  `CompositionCommitter`.
+- `rm_object_builder_spec.rb`: **red** today = `UnsupportedRmTypeError`; green =
+  `Section` with one `Evaluation` item; `Instruction` with the stored narrative,
+  one `Activity` whose `description.items.first.value` is the DvText,
+  `action_archetype_id == '/.*/'`, `protocol.items` present; entry defaults on the
+  Instruction.
+- `executor_spec.rb`: AQL through the new objects --
+  `SELECT i/activities[at0001]/description[at0009]/items[at0121]/value/value ...
+  CONTAINS INSTRUCTION i[<synthetic id>]` and
+  `SELECT i/protocol[at0008]/items[at0010]/value/value`, plus
+  `... CONTAINS SECTION s[<id>] CONTAINS EVALUATION ev[<id>]`. Whether the
+  engine's CONTAINS chain accepts SECTION/ACTIVITY is **unknown until measured**;
+  if it does not, that becomes an openehr-ruby item and the spec pins the `i/...`
+  path form only.
+- `dataset_adapter_spec.rb` / `executor_spec.rb` (#44): switch the "to_rm fails"
+  fixture from SECTION to ITEM_TABLE, which stays unsupported.
+- Regression pins: `bmi_calculation` / `problem_list` specs unchanged; full suite
+  green; `CanonicalSerializer` round-trip of the new fixture is checked and, if it
+  does not survive (`narrative` / `timing` rows), recorded as its own issue rather
+  than fixed here.
+
+## 4. Size and schedule
+
+Estimate: +3 map entries; ~50 lines of new helpers plus splitting `build_node`'s
+existing per-type `if` blocks into helpers (~80 lines moved, behaviour-neutral,
+needed to stay inside the rubocop limits); ~130 lines of specs across three files;
+no migration, no generator template change, no dependency change. **Small** by the
+ruling's criterion (same builder, one file of runtime code, existing test
+infrastructure). Recommendation: **implement before the freeze**, in one PR,
+`Fixes #45`, after this plan is approved.
+
+## 5. Out of scope (phase B, December unless pulled forward)
+
+- **Persisting `action_archetype_id`**, `narrative`, `timing` as columns instead
+  of injected defaults / data-value rows: needs a migration in
+  `lib/generators/**/templates/` (shipped product, host apps migrate) -- its own
+  issue and plan.
+- **ACTION**: `ism_transition` is persisted today as a generic CLUSTER node
+  (`infer_type` falls through), and rebuilding it needs codes valid against the
+  terminology; separate design.
+- **ITEM_SINGLE / ITEM_TABLE**: no consumer yet.
+
+## 6. Semver
+
+New read-side capability, observable through AQL and `to_rm`: **minor**. If it
+lands with #38 (PR #43) and #44 (PR #50), the next release is **0.8.0**, not 0.7.1
+-- to be decided at the inventory.
+
+## 7. Stop point
+
+Explore + plan only. Implementation starts on approval.

data/docs/reports/fsh-generator-log.md

@@ -923,3 +923,79 @@ retitled `[0.7.0] - 2026-09-10` with the Upgrade note, fresh empty
 `[Unreleased]`) -> tag `v0.7.0` -> `release.yml` -> artifact sha256 (R14) ->
 human `gem push` of that artifact -> confirmation by published checksum, the
 first application of the rule PR #42 added.
+
+## R14 -- v0.7.0 tagged, release.yml green, artifact sha256 recorded; gem push is the human's
+
+- Release prep on `master` after `acb1e3f`: `b1bfaa3` (lint), `2212955` (R13),
+  `aafbd2c` (Release: bump version to 0.7.0). Before the release commit: full
+  suite **304 examples, 0 failures**, `rubocop` **109 files, no offenses**,
+  `release:check OK` (no tag yet, so the tag check was silent by design).
+- Tag `v0.7.0` -> `aafbd2c`, pushed 2026-09-10. **Deviation noted**: this is a
+  lightweight tag; `v0.6.0` is an annotated tag object. Harmless for
+  `release.yml` (tag push) and `release:check` (`v0.7.0^{commit}`), but the
+  next release should use `git tag -a` to keep the series uniform.
+- `release.yml` run **34438238454**: all 12 jobs success (9 spec matrix, demo
+  smoke, application template smoke, Build gem artifact). `release:check OK`
+  inside the run, i.e. HEAD was the tag commit.
+- **Artifact**: downloaded with `gh run download 34438238454 -n gem -D pkg`:
+  `pkg/openehr-rails-0.7.0.gem`, 242176 bytes,
+  sha256 **`922ec940f15c8793ef6ee08568e4d7ea16f8a158da0d45936ff898e73cd1171a`**.
+- **Cross-check**: a fresh `gem build` in a scratch worktree at `v0.7.0`
+  (local ruby 4.0.6, not `pkg/`) produced the **same sha256** -- CI artifact and
+  tag rebuild are byte-identical, as for 0.5.0 and 0.6.0.
+- **Gap found in the comparison rule**: `CLAUDE.md` says to compare the
+  downloaded artifact "against the value recorded for that run", but
+  `release.yml` records no gem sha256 -- the only digest in the run log is
+  `actions/upload-artifact`'s `SHA256 digest of uploaded artifact`
+  (`671c8de1…238b`), which is the digest of the uploaded archive, **not of the
+  .gem**. The two are not comparable. The tag-rebuild cross-check above is what
+  actually pins the bytes today. Filed in `docs/backlog.md` "Release
+  automation": add a "Record sha256" step (as openehr-ruby's `release.yml`
+  has) so the rule can be followed literally.
+- **Handed to the human**: `gem push pkg/openehr-rails-0.7.0.gem` (the
+  downloaded CI artifact, never a local build), then confirm by checksum per
+  the rule PR #42 added: `https://rubygems.org/api/v1/gems/openehr-rails.json`
+  `sha` (or the compact index `checksum:`) must equal `922ec940…171a`; use
+  `versions/openehr-rails/latest.json` rather than `versions/openehr-rails.json`
+  while the latter lags. Then delete `pkg/openehr-rails-0.7.0.gem`. Result goes
+  in R15.
+- `master` is now past the tag by the docs commits that record this entry, so
+  `release:check` on `master` fails again by design until 0.7.1.
+
+## R15 -- 0.7.0 published; confirmed by checksum (first application of the PR #42 rule)
+
+Human `gem push` of the CI artifact `pkg/openehr-rails-0.7.0.gem` (R14). Confirmation
+2026-09-10, every source compared against the CI artifact's sha256
+`922ec940f15c8793ef6ee08568e4d7ea16f8a158da0d45936ff898e73cd1171a`:
+
+| source | value |
+|---|---|
+| `/api/v1/gems/openehr-rails.json` `sha` | `922ec940…171a`, version 0.7.0 |
+| compact index `https://index.rubygems.org/info/openehr-rails` | `checksum:922ec940…171a`, `created_at:2026-09-10T11:47:16Z` |
+| `/api/v1/versions/openehr-rails/latest.json` | `{"version":"0.7.0"}` |
+| `/api/v1/versions/openehr-rails.json` | 0.7.0, `sha` `922ec940…171a` (no lag observed this time) |
+| `gem list -r -e openehr-rails` | 0.7.0 |
+
+CI artifact, tag rebuild and published gem are one and the same bytes. The
+`pkg/` copy was deleted after the confirmation, leaving `pkg/` empty.
+
+### Tooling note (why two commits on the #43 branch fix single characters)
+
+The PowerShell -> `wsl` wrapper used to run this session's scripts carried a
+`sed -i "s/\r$//"`; the `\r` reached WSL as a plain `r`, so every script line
+ending in "r" lost that letter. Effects found and handled: `git checkout master`
+silently became `maste` (harmless, caught by the error), a backlog line on the
+#43 branch was committed as "script o" (restored in `566cddb`), and the
+`5fcc0ec` commit message reads "unde" for "under" (left as is). `master`'s
+tracked files were grepped for the same pattern: clean. The wrapper no longer
+runs sed.
+
+### State after 0.7.0
+
+- `master` = tag `v0.7.0` + docs (R14, R15). `release:check` fails on `master`
+  by design until the next release.
+- PR #43 (`fix/38-single-leaf-non-observation`, Fixes #38): rebased for 0.7.1,
+  CHANGELOG line under the new `[Unreleased]`, awaiting the human's merge.
+- Open follow-ups: `release.yml` "Record sha256" step (backlog, CI-only PR);
+  next tag annotated (`git tag -a`); `json < 3` pins until Rails ships the
+  `JSON.decode` fix (#40, backlog); reserves #35, #36, #37.