Complete scenario-2 name-filter assertion and refresh the harness for v0.4.0 #529

Merged
weichen merged 4 commits from feature/rdm-increment-settings-duties into main 2026-10-13 15:02:14 +00:00
4 Commits
Author SHA1 Message Date
weichen 0dc6ee2644 Re-record the ten-scenario run at the committed head
ci / svc-realcombo (pull_request) Successful in 2m34s
ci / test (pull_request) Successful in 5m38s
ci / test-pg (pull_request) Successful in 9m11s
Why: task-sync flagged the earlier rows as recorded with uncommitted script
changes; the gate requires key checks re-run at a committed head.

Evidence: SELF row via make evidence - 25/25 PASS on a fresh rdm@84ca64f
disposable instance.

Impact: task card only.

Refs: task feature/rdm-increment-settings-duties.
2026-10-13 14:52:31 +00:00
weichen abea6f3332 Record the sync checkpoint
Why: bind the task validation checkpoint to the latest integration baseline.

Evidence: SELF recursive component checks; sync_base=ee9b437b22b49f96e1bc65f79417b22e8e82a37c; candidate=d9850fccadf63c8a8512a9497cc7c583ae1f34e3.

Impact: task metadata only.

Refs: .task/feature-rdm-increment-settings-duties.md
2026-10-13 14:51:58 +00:00
weichen d9850fccad Merge authoritative main into the task branch
Why: include the current integration baseline before verification.

Evidence: fetched origin/main=ee9b437b22b49f96e1bc65f79417b22e8e82a37c.

Impact: integrate upstream changes without rewriting task history.

Refs: task-sync
2026-10-13 14:51:35 +00:00
weichen 252d9d4af1 Complete scenario-2 name-filter assertion and refresh the harness for v0.4.0
Why: with the four-repo v0.4.0 release live, the account.list query/name
passthrough (RDM #356) enables the deferred full assertion of scenario 2; the
harness also needed v0.4.0 adaptations discovered on the combo instance.

Evidence: tool-written rows on the card - full ten-scenario run on a disposable
rdm@84ca64f combo instance (25/25 PASS incl. 2b name-substring, 2c
case-insensitive owner filter, 2d limit truncation), and dev service status
(rdm@84ca64f running against the live dev database, auth gate 401).

Harness fixes: rdm.project.member.setRole renamed to set-role (RDM #350);
command envelope parsed via payload; re-login after the password gate (base
#195 revokes sessions on password change); RDM world provisioning via
rdm.project.create + bind with the domain admin self-removing so owner2 is the
sole owner (creator is seeded as owner); scenario 8b asserts allow:true in the
current response shape; scenario 10b now meaningful (base #195 admits member
conversations through RDM project membership).

Impact: integration script and task card only; no product code.

Refs: task feature/rdm-increment-settings-duties; RDM #356; base v0.4.0 tags.
2026-10-13 14:51:25 +00:00