Skip to content

Fix: enforce assignment and linked-evidence write authority - #2

Merged
ScaleLeanChris merged 1 commit into
mainfrom
fix/assignment-shared-write-guard
Oct 10, 2026
Merged

ScaleLeanChris merged 1 commit into
mainfrom
fix/assignment-shared-write-guard

Conversation

@ScaleLeanChris

Copy link
Copy Markdown
Contributor

Summary

Enforces assignment and linked-evidence write authority at shared server boundaries. Preserves dedicated lifecycle operations, legacy aliases, and ordinary shared-record workflows. Adds an authority table through schema migration 3 → 4.

Verification

  • Local live service was patched and verified before publication; forbidden generic assignment write returned 403-equivalent and the record revision stayed unchanged.
  • 85 repository tests and 39 Hermes-plugin tests passed independently.
  • Production build and isolated multi-file backup, upgrade, restore, and rollback rehearsal passed.
  • Seven company databases upgraded to schema 4; local health, web, and unauthenticated denial probes passed.

Release note

Schema-3 servers cannot read upgraded company files. Rollback needs a consistent pre-upgrade backup and loses writes after that snapshot. Existing evidence is not retroactively repaired. Review residual legacy conflicts before editing those records.

This PR makes the now-live local fix durable upstream; it does not introduce additional service changes.

@ScaleLeanChris
ScaleLeanChris merged commit 8c6ed5e into main Oct 10, 2026
1 check passed
@ScaleLeanChris
ScaleLeanChris deleted the fix/assignment-shared-write-guard branch October 10, 2026 07:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant