@consiliency/agent-board-schema 1.60.0 → 1.64.0

package/README.md

@@ -7,6 +7,12 @@ and materialize it — they do not author `agent_board` DDL.
 
 ## What's in the bundle
 
+Schema 1.64.0 adds `20261014000200_agent_board_last_owner.sql`: a refusal-only
+table-level last-active-owner invariant, preserving the 1.63.0 role-grant policy.
+Concurrent departures serialize per board; recovery remains service_role-only.
+SQL schema version remains 8. See `specs/rpc-contracts.md` for refusal/retry
+semantics. This is the working-tree contract, not a deployment receipt.
+
 - `migrations/` — the ordered, immutable SQL union (frozen baseline + lane
   migrations + the Message Board-owned endpoint compatibility migration).
 - `schema-manifest.json` — package version, `agent_board.schema_version`, ordered
@@ -17,6 +23,86 @@ and materialize it — they do not author `agent_board` DDL.
 - `tests/` — the pgTAP suite + `tests/fixtures/` (adopter-base + test/operator prerequisites).
 - `fixtures/` — plan/check history snapshots.
 
+## SIDSCHEMA foundation (as built 2026-10-08)
+
+SIDOWNER prepares schema package 1.62.0 with
+`20261012000100_agent_board_sidowner.sql`: scoped normalized identity-state and
+strict-lineage child-list reads. SQL schema version remains 8.
+
+Schema package 1.63.0 adds `20261014000100_agent_board_grant_target_role.sql`
+(#674): `grant_board_role` refuses a non-self grant unless the grantor is an owner
+or admin AND strictly outranks the target's current role. SQL schema version
+remains 8.
+
+| Package release | SQL schema version | Forward migration |
+| --- | --- | --- |
+| 1.61.1 | 8 | `20261011000100_agent_board_session_identities.sql` |
+
+The 1.61.1 patch makes seeded migration apply transaction-safe. Each repository
+applier uses one transaction per migration with ON_ERROR_STOP=1; pre-migration
+seed hooks remain separate. A post-backfill flush of only
+`agent_board.session_identities_lease_alias_fkey` precedes later index/trigger/RLS
+DDL, preserving unrelated deferred constraints even for following statements in
+the same transaction. A catalog/event-class pin and whole-file composition
+probe verify that scope; the ALL mutation fails the later deferred-FK assertion.
+A git-derived executable guard enforces transactional appliers in the aggregate
+and CI, names offending sites, and states its scanner limits in its header. The
+failed 1.61.0 production apply rolled back; 1.61.0 was never deployed or published.
+This patch changes apply-ability, not runtime behavior.
+
+The bundle now contains durable session identities/aliases, immutable lineage,
+one-live-holder leases with epoch fencing, depth-two bounded delegation,
+shrink-only continuity, fingerprint approval/freeze, total family revocation and
+fresh-principal owner readmission. Existing principals are backfilled as legacy,
+with actual parent/root/depth and no implicit lease or approval. Excessive or
+cyclic pre-existing lineage refuses instead of being flattened. Backfill also
+refuses a stored-root/computed-root mismatch, reporting the offending ids.
+
+Explicit freeze gates apply to both legacy mint paths and all ancestors without
+requiring implicit approval for never-frozen legacy principals. Approval requires
+exactly resolved readings; human-owner writers enforce the locked permanent
+revocation ledger. Unclaimed supersede revokes only its target; ordinary revoke
+still closes descendants/forks; public fleet/admin/subtree revocation rejects
+the reserved supersede reason. Both human-owner and ancestor approval enforce
+the locked permanent ledger. Tombstone refusal takes precedence over freeze.
+Platform-admin revoke requires a resolved actor only for a family containing a
+session identity; legacy service scripts without `sub` and Portal admins without
+board principals remain supported, never using the target as a fallback actor.
+Local board labels are bounded to 200 characters. CI rechecks the actual
+backfill stored/computed-root refusal, not only driver-local evidence.
+
+Verified instance tombstoning takes every existing board advisory mutex in UUID
+order before owner/instance and identity-family row locks, preserving onboarding
+and placement's board-first ordering. The lock class has no withdrawal-state
+exemption. A new three-permutation isolation spec races actual withdrawal and a
+minted session descendant against onboarding's documented lock-equivalent
+acquisitions; all pre-existing isolation specs and goldens remain unchanged.
+Plan amendment 3 records the catalog-proven nullable/default-free omitted-FK
+INSERT filter, with positive constructor/revoke pins and a non-NULL ledger FK
+mutation that restores the relation pair in FKL-10.
+
+Lease heartbeat/lapse is 60/180 seconds; an approved session grant is at most
+seven days under tighter ancestor/policy/operator ceilings; each issued token
+remains at most 900 seconds. Root limits are 200 active/60 hourly and depth-one
+parent limits 20 active/10 hourly, with mixed legacy/session accounting.
+Legacy operator mints also refuse requests above the tighter operator TTL;
+renewals clamp to that ceiling. Root limits are unconditional, including legacy
+operator-approved mints.
+
+Session-form attestation RPCs are service-role-only. Current public Edge handlers
+do not forward asserted harness/session/fingerprint fields; measured transport,
+extended PoP, holder-secret storage and epoch-bearing JWTs remain SIDSERVER work.
+No hosted-delegate authority is broadened and the client compatibility minimum
+is unchanged. This is a bundle change, not a production deployment or publication.
+
+The transactional-apply patch passes all twelve Verification commands, 181/181 fresh
+caught mutation rows, full pgTAP 148 files/3943 assertions and isolation 60 specs
+at ITER=10. Canonical comparison preserves the accepted Session identities text.
+
+See the [as-built client contract](../../specs/agent-client-contract.md#sidschema-as-built--2026-10-08),
+[exact catalog RPC matrix](../../specs/rpc-contracts.md#sidschema-as-built--2026-10-08),
+and [schema evidence closeout](../../plans/evidence/sid/schema-closeout.md).
+
 ## Adopter CLI (the only supported path)
 
 ```bash

package/fixtures/already-applied.json

@@ -632,6 +632,22 @@
   {
    "id": "20261010000100_agent_board_own_post_not_delivered",
    "sha256": "6cbbe0bb9ccf7ab65402a58de145ee21bc2158ddc7502671ea13a98415ca6421"
+  },
+  {
+   "id": "20261011000100_agent_board_session_identities",
+   "sha256": "0f429d2b7c2a361741fb00019a173c82024a59362ea2d3a70cb11ab594b1d055"
+  },
+  {
+   "id": "20261012000100_agent_board_sidowner",
+   "sha256": "e18fb5a7ce0b00e9cccf12a60cbad49d820612c2c50f65c648d4105c80fbc921"
+  },
+  {
+   "id": "20261014000100_agent_board_grant_target_role",
+   "sha256": "4a6c00546a1d2837f88eece1de082cc76eec1f85cce8cf9ac7998e42bf32a5c5"
+  },
+  {
+   "id": "20261014000200_agent_board_last_owner",
+   "sha256": "2fed8fc5a2c7c0ba9acbb12872b329db3f0902d96597c52cc50e21e4682c2fff"
   }
  ]
 }