@fitzzero/quickdraw-skills 5.0.0 → 5.0.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@fitzzero/quickdraw-skills",
-  "version": "5.0.0",
+  "version": "5.0.1",
   "description": "Agent rules and skills for quickdraw 5.0 apps, linked into .claude/ by the quickdraw-skills command",
   "keywords": [
     "agents",

package/rules/quickdraw-access.md

@@ -88,7 +88,7 @@ compile time.
 | `members({ model, entry, user, level, levels? })`      | a membership table row                          |
 | `inherit({ from: projectContract, via: "projectId" })` | the level on the parent row in another service  |
 | `anyOf(policyA, policyB)`                              | the highest level any of them gives             |
-| `resolver({ levelsFor, where? })`                      | your code, one batched read for all ids         |
+| `resolver({ levelsFor, where?, reads })`               | your code, one batched read for all ids         |
 | `everyone("Read")`                                     | every signed-in user, on every row; no read     |
 
 - `entry` forms need a policy and `scope` forms a `model`; a service without
@@ -100,6 +100,17 @@ compile time.
   `anyOf(owner("id"), everyone("Read"))`, never a hand-written `resolver`
   answering `Read` for every id: `rowless: true` covers one method, not
   subscriptions.
+- A `resolver` declares what its levels depend on, or nothing re-checks it
+  and a removed member keeps their live rows:
+  `reads: { columns: ["visibility"], memberships: [{ model: "teamMember", entry: "projectId", user: "userId", level: "role" }] }`
+  (columns of the service's model; membership tables as `members` takes
+  them, `entry` holding this service's row id). Tracked writes to them then
+  revoke and re-check as for the other policies, and `tools.rows(ids)` reads
+  the declared columns. `reads: "none"` only when nothing a tracked write
+  changes can change a level (the principal's grants alone). Without either
+  the server warns `[quickdraw:resolver-without-reads]` and a strict test
+  app fails to start. A level from another service's row is `inherit`'s
+  job, alone or in `anyOf`.
 - Lookups are batched per call: checking 60 ids costs what one does.
   `createServer({ access: { cacheMs } })` keeps them across calls; tracked
   writes to the columns and tables a policy reads evict them.

package/rules/quickdraw-services.md

@@ -186,6 +186,11 @@ Contract halves come from `@fitzzero/quickdraw-core`, handlers from
 - `sharing.contract({ mode: "acl" | "members" })` with `sharing.handlers(project)`,
   on a service whose policy has a `jsonAcl` or `members`.
 - `admin.contract({ entity })` with `admin.handlers(task)` (`{ service: "Admin" }` by default).
+  Name what an admin may change with `editable: ["title", "status"]` (on
+  `admin.contract` too, so the input schemas and MCP tools name only those):
+  every other field is read-only, and a write naming one is `VALIDATION`.
+  Without it the kit writes every field it shows but `id` and the
+  timestamps, owner and foreign-key columns included.
   On a users service, `admin.handlers(user, { grants: true })` lets the admin
   screen edit `serviceAccess` through `adminUpdate` (service-wide Admins
   only); never hand-write a `setServiceAccess` method for it. `adminMeta`

package/rules/quickdraw-testing.md

@@ -122,9 +122,10 @@ test that caused it (an oversized reply fails an in-process `app.as(...)`
 call; over a socket or HTTP the reply was already sent, so it is logged, not
 thrown). Warnings outside its calls (an `ambient-write` while seeding) are
 logged, and `app.close()` ends it. `tiered-field-in-output` (a method's own
-output schema declares a tiered field, at any depth) is thrown by
-`createTestApp` itself: answer `"entity"` from that method rather than
-turning strictness off.
+output schema declares a tiered field, at any depth) and
+`resolver-without-reads` (a `resolver` policy declares no `reads`) are
+thrown by `createTestApp` itself: answer `"entity"` from that method, or
+declare the resolver's `reads`, rather than turning strictness off.
 Turn it on for service suites.
 `createRecordingSink()` passed as `flushSink` records what each flush wrote.