fix: align read retry status and validation fixtures

Signed-off-by: Jeremi Joslin <jeremi@joslin.fr>

Author: jeremi

crates/registry-breg/src/api/tests/immediate_action_tests.rs

@@ -858,9 +858,11 @@ async fn human_identity_is_the_principal_claim_and_a_human_token_without_it_is_r
     let registry = compiled();
     let idp = MockIdp::start().await;
     let audience = "urn:example:breg";
+    let mut verifier = oidc_verifier_config(idp.issuer(), vec![audience.to_owned()]);
+    verifier.allowed_clients = vec!["agent-client".to_owned()];
     let auth = RegistryAuthenticator::new(
         &registry,
-        oidc_verifier_config(idp.issuer(), vec![audience.to_owned()]),
+        verifier,
         Arc::new(JwksFetcher::new_with_fetch_url_policy(
             idp.jwks_uri(),
             JwksFetcherConfig::defaults(),
@@ -871,6 +873,7 @@ async fn human_identity_is_the_principal_claim_and_a_human_token_without_it_is_r
     .expect("human verifier config is valid");
     let claims = json!({
         "aud": audience,
+        "azp": "agent-client",
         "registry_principal": "reviewer-principal",
         "registry_actor_kind": "human",
         "registry_purpose": "case-management",

crates/registry-coordinator/src/store.rs

@@ -2531,6 +2531,11 @@ impl DispatchStore for Store {
             || audit.record.cancel_requested && !uncertain
         {
             "cancelled"
+        } else if matches!(
+            audit.transition,
+            Transition::LeaseLapsed(Disposition::RetryPending)
+        ) {
+            "running"
         } else if !uncertain && matches!(audit.transition, Transition::Expired { .. }) {
             "expired"
         } else {

crates/registry-coordinator/tests/read_lease_recovery.rs

@@ -388,6 +388,9 @@ async fn lapsed_read_retries_and_fences_the_old_attempt() {
     let worker = Worker::new(harness.store.clone(), replacement.clone());
     worker.tick().await.expect("recover lapsed read");
     assert_eq!(harness.job(run, "read").await.0, "pending");
+    let retrying = harness.store.status(run).await.expect("retrying status");
+    assert_eq!(retrying.state, "running");
+    assert!(retrying.next_due_at.is_some());
     harness.assert_lapse_audit();
 
     harness.make_retry_due(run).await;

products/coordinator/README.md

@@ -245,6 +245,8 @@ only. `coordinatorctl test` rejects misspelled fake record members with `scenari
 and invalid computed template data with `scenario.call-input`. Aliases without `record` or
 `template` retain their general contracts. Regenerate imports when the owning project changes.
 
+Template data schemas use [Messaging's supported reference form](../messaging/README.md#running-locally).
+
 These imports grant no access. Messaging still checks the connection's caller, sender profile
 and template at request time. The [earlier appointment alert](examples/earlier-appointment-alerts/README.md)
 shows both imports alongside their owning projects.

products/messaging/README.md

@@ -271,6 +271,10 @@ value as `dataSchema`. The export is separate from the immutable
 package inputs and never changes the package digest; an existing output file
 is refused rather than overwritten.
 
+Use local JSON Pointer references, such as `#/$defs/name`, in template data
+schemas. The current schema validator does not support named anchors or dynamic
+references.
+
 `--data` names a JSON file, read relative to the directory the command runs
 in like any other relative path; each template version's `sample.json`
 serves. `messagingctl plan` and `status` use the runtime credential in

products/platform/conformance/yaml/expected-failures.yaml

@@ -55,6 +55,8 @@ unreachedFormats:
   reason: syntax json; the corpus mutates YAML text
 - format: messaging/dev-state
   reason: syntax json; the corpus mutates YAML text
+- format: messaging/template-contracts
+  reason: syntax json; the corpus mutates YAML text
 - format: platform/thunderid-session
   reason: syntax json; the corpus mutates YAML text
 inapplicableCases: []