Rent v0.4.0

This release makes privileged access explicit and improves system references and permission fixtures.

Scoped clients for request handlers

Bind the authenticated viewer once, then pass the resulting ScopedClient to handlers and services. It exposes ordinary CRUD while keeping privileged operations on the root client. Transactions and clones preserve the scoped identity.

When upgrading, regenerate the client and update request/service parameters to ScopedClient. Keep RootClient in bootstrap code and narrow trusted adapters. Follow the scoped-client guide.

Explicit system references

Use @rent.reference when an application record should reference an existing system record without granting access to that record's contents. Tenant boundaries, foreign keys and source-write permissions remain enforced. See system references.

Richer permission fixtures

Permission fixtures support nullable circular relationships, such as an account and its root workspace. Native PostgreSQL fixtures can exercise database-specific indexes. SQLite remains a convenient isolated default. See permission fixtures.

Use matching Rent dependencies and CLI versions, then run rent generate. See installation.