Update: pin Trust v1.1.1 and SpecSync 5.1.1

[0xLeif]

Pins changed

• CorvidLabs/trust@9d32b5786d2e9e4d39fc581c0091c721ee3d4226 # v1.0.0 → CorvidLabs/trust@a239f78658e5ad0f12fa230f494890e40c6e4d7b # v1.1.1
• CorvidLabs/spec-sync@59bbfa766c6cce01ab815ab47db195b0629cc014 # v5.0.1 → CorvidLabs/spec-sync@a89d827e93fa0bc9e6168447e66a0ad30fa92e65 # v5.1.1
• version: 5.0.1 → version: "5.1.1"

All in .github/workflows/trust.yml.

Migration

python3 /tmp/migrate_specsync_5_1_records.py . output:

migrated 0 fields across 2 ledgers

No ledger fields required backfilling for SpecSync 5.1.1.

Changes re-accepted

The pin bump made two accepted changes stale on the governed input .github/workflows/trust.yml. Both went through the full reopen → verify → accept cycle (actor user:0xLeif):

• CHG-0001-adopt-specsync-5-0-1-and-trust-1-0-0-governance-for-swift-valid — verification passed (2 command(s), 0 requirement(s)); re-accepted.
• CHG-0002-document-the-existing-swift-valid-api-at-complete-coverage-and-correct-rollout-p — verification passed (2 command(s), 10 requirement(s); 109/109 tests); re-accepted.

Canonical deltas were already integrated and were not replayed.

Final specsync check

✓ SDD lifecycle valid (2 active change(s))

⊘ Skipped 1 unchanged spec(s) (use --force/--no-cache to re-validate all)
  ℹ Cache: /private/tmp/swift-valid/.specsync/hashes.json

All specs unchanged — nothing to validate.
File coverage: 12/12 (100%)
LOC coverage:  1526/1526 (100%)

Exit code 0 — error-free.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.