@astram/guide 0.2.5 → 0.2.6

package/CAPABILITIES.md

@@ -317,12 +317,48 @@ upload(@Req() req: Record<string, unknown>) {
 - 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).
 
+## Database names and several environments on one server (`SHIELD_DB_NAMESPACE`, ADR-0037)
+- The framework uses four databases, `<ns>_app`, `<ns>_identity`, `<ns>_authz` and `<ns>_audit`,
+  with its own accounts (`<ns>_core`, `<ns>_migrate`, `<ns>_audit_ops`, …). If you leave
+  `SHIELD_DB_NAMESPACE` unset, `<ns>` is `shield` (`shield_app`, …), which is unchanged from
+  earlier releases.
+- **To run dev and beta on one MariaDB server**, give each environment its own namespace. It must
+  be lowercase letters and digits only (`beta`, `staging2`; no `_`). Then:
+  1. Provision it with the framework's `db-provision --namespace beta` (from the astram-framework
+     repo, runbook §6). Use distinct passwords per namespace.
+  2. Set `SHIELD_DB_NAMESPACE=beta` for both the server and `npm run migration:run`. The same
+     value must reach both.
+  3. Run migrations (the ledger is `beta_app.schema_migrations`), then start the server.
+- Defaults follow the namespace: `APP_DB_USER` ⇒ `<ns>_core`, `APP_DB_NAME` ⇒ `<ns>_identity`,
+  `DDL_DB_USER` ⇒ `<ns>_migrate`. Explicit values win.
+- **Rules your app must follow:**
+  - `APP_DB_NAME` must be one of the four framework databases, even with the namespace unset.
+    Any other value refuses to boot.
+  - An invalid namespace refuses to boot and to migrate.
+  - Use a separate Redis (instance or DB index) per environment: Redis keys are not namespaced.
+  - Your own object types keep a literal `schema` or none. Do not hard-code `shield_*` names in
+    app SQL or migrations: read them from the injected `FRAMEWORK_SCHEMAS` (`@astram/guard`).
+- **Boot check:** outside development/test (an unset `NODE_ENV` counts as production), the server
+  refuses to start when framework migrations are missing from the ledger, no ledger is found, or
+  the ledger is unreachable. Run `migration:run` before starting. With the namespace unset, the
+  server looks for the ledger in `DDL_DB_NAME`, its own `APP_DB_NAME`, then `shield_app`, so
+  `migration:run` with the server's `.env` is found. If your migrate job uses a different
+  `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).
+
 ## Migrations (`@astram/migrate`)
 - `migrate` / `migrate:revert` / `migrate:status` with the deploy-time DDL account (`DDL_DB_*`);
   the running app never holds DDL. Framework migrations merge with yours (`APP_MIGRATION_DIR`).
 - Numeric ordering, duplicate-id detection, a database lock so concurrent deploys never apply a
   migration twice (`APP_MIGRATION_LOCK_TIMEOUT`, default 120 s), and drift detection (a changed
   applied file is reported; `--strict` fails on it). Never edit a migration that already ran.
+- Upgrade `@astram/migrate` together with `@astram/guard` and `@astram/identity`. The framework
+  migrations read the database names from the migrate context (`ctx.schemas`). An older migrate
+  works only while `SHIELD_DB_NAMESPACE` is unset, and stops with "upgrade @astram/migrate"
+  otherwise. On upgrade, `migrate:status --strict` reports the framework's rewritten migrations as
+  SUPERSEDED, not drift, and `migrate` updates their ledger rows without re-running them.
 
 ## Frontend (`@astram/frontend-core`, `@astram/sdk`, scaffolded `frontend/`)
 - `@astram/frontend-core`: auth, account, identity, audit, record-policy, share, cross-tenant and
@@ -353,5 +389,6 @@ 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.5",
+  "version": "0.2.6",
   "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",