@astram/guide 0.2.6 → 0.2.7

package/CAPABILITIES.md

@@ -313,7 +313,7 @@ upload(@Req() req: Record<string, unknown>) {
   the upload check.
 - **Lint wall** — the scaffold bans `multer`, `@aws-sdk/*`, `minio`, `fs` / `node:fs` (and
   `/promises`) in `src/features/**`: use `FileIntake` and `FilesService`, never the bucket.
-- Do not grant `stored_file:create` to app roles; uploads go through `FilesService`.
+- Roles that upload need `stored_file:create` (FilesService creates the record as the caller), but app code must create `stored_file` rows only through `FilesService.store()` — never `records.create('stored_file', …)` / `createMany`, which would let a caller set its own `storageKey` (downloads still refuse a key outside the caller's tenant, KI #137).
 - Not provided: malware scanning, per-tenant encryption of file bytes (SSE-S3 only), streaming
   downloads, dedup (each upload is its own record; `sha256` is returned so you can detect repeats).
 
@@ -346,7 +346,41 @@ upload(@Req() req: Record<string, unknown>) {
   `APP_DB_NAME`, set the same `DDL_DB_NAME` for migrate and the server.
 - The `<ns>_backup` and `<ns>_monitor` accounts keep server-wide grants and can see every
   namespace on the server.
-- One database per account (some managed hosts) is NOT supported yet (needs the four databases).
+- One database per account (some managed hosts): see the single-database layout below.
+
+## Single-database layout (`SHIELD_DB_LAYOUT=single`, ADR-0041, opt-in, reduced isolation)
+- For hosts that give one database per account. The four-database layout stays the default.
+- **Set:** `SHIELD_DB_LAYOUT=single`, `SHIELD_DB_NAME=<db>` (`^[a-z0-9_]{1,64}$`),
+  `SHIELD_DB_LAYOUT_ACK_REDUCED_ISOLATION=1` (exactly `1`, every environment, production
+  included), `APP_DB_USER`. Leave `SHIELD_DB_NAMESPACE` unset; `APP_DB_NAME`/`DDL_DB_NAME` unset
+  or `<db>`. Same values for the server and `npm run migration:run`. Anything else refuses to boot
+  and to migrate.
+- **Set `POOL_MAX_ENGINE`** (e.g. 10). Unset, the engine pool uses `APP_DB_MAX_CONNECTIONS`, and
+  the single-layout budget `workers × (POOL_MAX_CORE + POOL_MAX_ENGINE + APP_AUTHZ_POOL_MAX) +
+  headroom` fails boot. `APP_DB_MAX_USER_CONNECTIONS` (the account's cap, if the host sets one) is
+  checked too.
+- All framework tables keep their names in `<db>`; your tables live there too. **Reserved
+  table names:** your object types and migrations must not use a framework table name (`companies`,
+  `users`, `roles`, `departments`, `branches`, `company_membership`, `membership_posting`,
+  `company_departments`, `company_branches`, `service_account`, `shared_resource`, `stored_file`,
+  `identity_credential`, `session`, `refresh_token`, `mfa_device`, `password_reset_token`,
+  `mfa_recovery_code`, `email_change_token`, `permission`, `role_permission`,
+  `authz_permission_version`, `access_bundle`, `access_bundle_permission`,
+  `record_permission_rule`, `record_share`, `scope_closure`, `service_account_key`,
+  `cross_tenant_grant`, `audit_log`, the ledger `schema_migrations`) or `prune_audit`. In single
+  mode a clash refuses to boot (object type) or to migrate (`CREATE TABLE` in your migrations);
+  in the four layout it only warns, so you see it early. The migration check reads whole files,
+  `down()` included: an app whose migrations ever created or renamed onto a reserved name cannot
+  migrate in single mode.
+- **One account** (`DDL_DB_*` unset ⇒ `APP_DB_*`): migrations and the server share the account
+  (`ALL PRIVILEGES ON <db>.*`). You lose append-only audit (#6), no runtime DDL and schema
+  separation (#11), the DB-enforced retention floor, and the separate DDL account; `audit:prune`
+  refuses to run. Boot logs this list every time (the privilege probe runs with
+  `ShieldModule.forRoot({ auth: true })`).
+- **Two accounts** (if the host allows a second user): the framework repo's
+  `db-provision --layout single` keeps `audit_log` append-only and the runtime free of DDL, and
+  installs `prune_audit`; re-run it after a migration adds a table. Schema separation is still lost.
+- Choose the layout at install: switching an existing install is not supported. MariaDB only.
 
 ## Migrations (`@astram/migrate`)
 - `migrate` / `migrate:revert` / `migrate:status` with the deploy-time DDL account (`DDL_DB_*`);
@@ -389,6 +423,5 @@ upload(@Req() req: Record<string, unknown>) {
 - External identity providers (OIDC, SAML, LDAP, Entra ID, Cognito, Okta, Google Workspace) and
   WebAuthn ceremonies.
 - Tenant- or role-mandated MFA (MFA is enforced for users who enrolled a device).
-- Single-database hosting (all framework tables in one database per account).
 
 If you need one of these, STOP and flag it in `.astram/guide/gaps.md` (Rule 4).

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@astram/guide",
-  "version": "0.2.6",
+  "version": "0.2.7",
   "license": "MIT",
   "description": "Astram framework — the AI/dev GUIDE layer (ADR-0025). Ships the framework's hard rules + capabilities manifest as installed, upgrade-refreshed docs. A consumer app's CLAUDE.md references FRAMEWORK_RULES.md from this package; `npm update` replaces it wholesale so new rules arrive cleanly, while the app's own .astram/guide/ layer is never touched. This is the framework-owned FLOOR: an app rule may tighten it, never weaken it.",
   "type": "commonjs",