@astram/guide 0.2.1 → 0.2.3

package/CAPABILITIES.md

@@ -20,13 +20,9 @@ below is wired by the two `forRoot` calls in your `app.module.ts`; you write no
 import { ShieldModule } from '@astram/guard';
 import {
   IdentityFeatureModule, identityAuthActionKeys, identityControlPlaneKeys,
-  buildIdentityRecordAuthorization,
 } from '@astram/identity';
-// Raw-pool factory: composition root only (app.module.ts), never exported from it.
-import { createIdentityAuthzPool } from '@astram/identity/internal';
 
 const rootIds = ['<platform-admin user uuid>'];   // from config, never from a request
-const authzPool = createIdentityAuthzPool();
 
 imports: [
   ShieldModule.forRoot({
@@ -35,14 +31,15 @@ imports: [
     rootIds,
     identityActionKeys: identityAuthActionKeys,
     identityControlPlaneKeys,
-    recordAuthorization: buildIdentityRecordAuthorization(authzPool, [/* YourType */]),
+    // no recordAuthorization: IdentityFeatureModule provides it
   }),
   IdentityFeatureModule.forRoot({ rootIds, extraObjects: [/* YourType */] }),
 ],
 ```
 
 - **`ShieldModule.forRoot(options?)`** (`@astram/guard`; `forRootAsync` for DI-computed options).
-  Options: `auth?`, `recordAuthorization?` (or a pre-built `decisionAuthority?`, never both),
+  Options: `auth?`, `recordAuthorization?` (or a pre-built `decisionAuthority?`; only for an app
+  WITHOUT `IdentityFeatureModule`, never both),
   `emailSender?: EmailSender | 'disabled'`, `rootIds?`, `identityActionKeys?`,
   `identityControlPlaneKeys?`, `config?`, and optional overrides `credentialResolver?`,
   `profileResolver?`, `credentialWriter?`, `resetTokenStore?`, `recoveryCodeStore?`,
@@ -50,11 +47,12 @@ imports: [
   `sessionFactsProjector?`, `scopeSubtreeResolver?`, `membershipChecker?`. With `auth: true` every
   override has a MariaDB/Redis default; leave them out unless you have a reason.
 - **`IdentityFeatureModule.forRoot({ rootIds?, extraObjects? })`** (`@astram/identity`). Pass the
-  SAME `rootIds` as `ShieldModule`, and the SAME `extraObjects` as
-  `buildIdentityRecordAuthorization`. Without `rootIds` it logs a boot warning.
-- `ShieldModule.forRoot()` with no options = enforcement only (no DB, no Redis, boots without
-  `.env`). Omitting `recordAuthorization` (and `decisionAuthority`) binds a stub that denies every
-  `@Classified` route.
+  SAME `rootIds` as `ShieldModule`. `extraObjects` (your own registered object types) are given
+  HERE ONLY: the module builds the record authorization from them and `ShieldModule` decides with
+  it. Passing `recordAuthorization`/`decisionAuthority` to `ShieldModule` as well fails the boot.
+  Without `rootIds` it logs a boot warning.
+- `ShieldModule.forRoot()` with no options and no identity module = enforcement only (no DB, no
+  Redis, boots without `.env`); it binds a stub that denies every `@Classified` route.
 
 ## Enforcement (`@astram/guard`)
 - **Global deny-by-default guard** — every route is denied unless `@Public()` or
@@ -142,7 +140,8 @@ imports: [
   `readScope` declares the subtree wall; `create: 'unscoped'` opts a type out of the create wall.
 - **Physical wall** — the raw DB pool is sealed in the engine. The scaffold's
   `server/eslint.config.mjs` fails lint on driver imports, raw pools, `.query()` and the
-  framework's internal DB exports anywhere in `src/**` except `app.module.ts` and `main.ts`. A lint
+  framework's internal DB exports anywhere in `src/**` except `app.module.ts` and `main.ts`, and on
+  uuid-named route/body inputs read without `UuidPipe` / `uuidField` (`@astram/guard`). A lint
   rule is a backstop, not a sandbox: do not go around it.
 - **Gap signal** — an unsupported field type or operation throws `CapabilityNotSupportedError`
   (a Rule-4 STOP). Field types this version: `string`, `number`, `boolean`, `uuid`, `timestamp`,

package/FRAMEWORK_RULES.md

@@ -71,6 +71,14 @@ app refuses to boot with one — a forgotten declaration locks the door instead
 silently exposing it. Never make a route public to "make it work"; classify it
 correctly.
 
+**Validate uuid inputs at the edge.** Every uuid route param uses `UuidPipe`
+(`@Param('uuid', UuidPipe)`) and every uuid body or query field goes through
+`uuidField` / `optionalUuidField` / `uuidArrayField` (all from `@astram/guard`). They
+answer 400 for anything that is not a strict uuid and hand you the canonical lower-case
+form. The database matches uuids ignoring case, trailing spaces and character width, so
+a raw `"<id> "` reaches the row while your exact checks in code miss it. The lint wall
+flags uuid-named inputs (`id`, `uuid`, `…Id(s)`, `…Uuid(s)`) read without them.
+
 ## 4. When the framework can't do it: STOP and FLAG the gap — do NOT work around it
 
 This is the most important rule. When a feature needs a capability the framework does

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@astram/guide",
-  "version": "0.2.1",
+  "version": "0.2.3",
   "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",