Skip to content

Add expiring scoped proposal reader mode - #183

Merged
Yehonal merged 1 commit into
mainfrom
pr/proposal-reader-expiry
Nov 13, 2026
Merged

Yehonal merged 1 commit into
mainfrom
pr/proposal-reader-expiry

Conversation

@Yehonal

@Yehonal Yehonal commented Nov 13, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Add a dedicated proposal_read_only_scoped registry mode with mandatory expiresAt and the single memory:proposal-read permission.
  • Allow scoped curation proposal listing and payload reads with existing audit and no-store behavior. Deny all other authenticated routes and methods.
  • Validate expiry during each authentication and session revalidation, and enforce the deadline again at permission checks.
  • Document sanitized registry setup and source installer deployment and rollback commands. Runtime operations and credential provisioning require separate approval.

Validation

  • node --test scripts/test-auth-registry.mjs scripts/test-fabric-server.mjs — 49 passed after replay onto current main.
  • npm test — 1,209 passed, 9 skipped on the authoring base before upstream replay. The upstream-added status test also passed in the final targeted run.
  • npm run check — passed.
  • git diff --check — passed.
  • Public diff scanned for private identifiers, addresses, paths, credentials and non-synthetic examples.

The focused coverage checks successful payload reads, scope isolation, mutation and unrelated-read denial, invalid or broader registry grants, and exact-deadline rejection without registry changes. No runtime configuration, credentials, services or live data were modified.

@Yehonal
Yehonal merged commit fbb499f into main Nov 13, 2026
1 check passed
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