deepspace 0.19.1 → 0.19.3

package/dist/schema.d.ts

@@ -62,7 +62,7 @@ interface RolePermissions {
     create: boolean;
     update: PermissionLevel;
     delete: PermissionLevel;
-    /** If set, only these columns can be updated by this role. */
+    /** If set, only these caller-supplied columns can be created or updated by this role. */
     writableFields?: string[];
 }
 interface CollectionSchema {

package/dist/server.d.ts

@@ -423,7 +423,7 @@ interface RolePermissions {
     create: boolean;
     update: PermissionLevel;
     delete: PermissionLevel;
-    /** If set, only these columns can be updated by this role. */
+    /** If set, only these caller-supplied columns can be created or updated by this role. */
     writableFields?: string[];
 }
 interface CollectionSchema {

package/dist/worker.d.ts

@@ -1000,7 +1000,7 @@ interface RolePermissions {
     create: boolean;
     update: PermissionLevel;
     delete: PermissionLevel;
-    /** If set, only these columns can be updated by this role. */
+    /** If set, only these caller-supplied columns can be created or updated by this role. */
     writableFields?: string[];
 }
 interface CollectionSchema {

package/features/admin-page/feature.json

@@ -21,11 +21,10 @@
   },
   "route": {
     "path": "/admin",
-    "protected": true
+    "protected": true,
+    "roles": ["admin"]
   },
   "requires": [],
-  "instructions": [
-    "This layers an admin-only /admin panel on top of the /settings page that every scaffold already ships (that shared src/schemas/admin-schema.ts is why it reports \"Exists (skipped)\" here). Add a nav entry for /admin; keep /settings for per-user settings."
-  ],
+  "instructions": [],
   "patterns": []
 }

package/features/cron/feature.json

@@ -5,10 +5,6 @@
   "description": "Scheduled background tasks via the per-app CronRoom DO",
   "details": "Reference implementation of a working cron job. Registers a 1-minute 'heartbeat' task in src/cron.ts (consumed by AppCronRoom at construction time). Each fire is logged to the DO's cron_history table; /cron-log subscribes via useCronMonitor and renders live history. Useful both as a working example and as the basis for the cron e2e spec.",
   "files": [
-    {
-      "src": "src/cron.ts",
-      "dest": "src/cron.ts"
-    },
     {
       "src": "src/CronLogPage.tsx",
       "dest": "src/pages/cron-log.tsx"
@@ -19,10 +15,17 @@
     "protected": false
   },
   "requires": [],
+  "code": [
+    {
+      "file": "src/cron.ts",
+      "marker": "export const tasks: CronTask[] = []",
+      "insert": "tasks.push({ name: 'heartbeat', intervalMinutes: 1 })"
+    }
+  ],
   "instructions": [
     "Deploy the app: npm run deploy",
     "Within ~90s, visit /cron-log on the deployed app — you should see one new row per minute as the AppCronRoom alarm fires the heartbeat task.",
-    "Open the page on a desktop browser and look at devtools → Network → WS → /ws/cron/app:<APP_NAME> to see live cron.* protocol frames."
+    "Open the page on a desktop browser and inspect /ws/cron/<SCOPE_ID>, where SCOPE_ID is app:<APP_ID> from src/constants.ts; APP_ID is immutable, while APP_NAME is only the mutable URL label."
   ],
   "patterns": [
     "Task config lives in code (src/cron.ts), not JSON. AppCronRoom validates at construction time.",

package/features/tasks/src/TasksPage.tsx

@@ -3,7 +3,7 @@
  *
  * Demonstrates:
  * - 'unclaimed-or-own' permission for claimable tasks
- * - writableFields for restricting which fields can be updated
+ * - writableFields for restricting which fields can be created or updated
  * - timestampTrigger for automatic timestamps
  * - Admin grading workflow
  */

package/features/tasks/src/tasks-schema.ts

@@ -3,7 +3,7 @@
  *
  * A claimable task system demonstrating:
  * - 'unclaimed-or-own' permission for claiming unclaimed items
- * - writableFields for restricting which fields users can update
+ * - writableFields for restricting which fields users can create or update
  * - timestampTrigger for automatic timestamp fields
  * - Admin-only grading workflow
  */

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "deepspace",
-  "version": "0.19.1",
+  "version": "0.19.3",
   "engines": {
     "node": ">=22.15.0 <23 || >=24 <25 || >=26 <27"
   },

package/features/cron/src/cron.ts

@@ -1,25 +0,0 @@
-/**
- * Cron task definitions for the heartbeat reference feature.
- *
- * AppCronRoom (declared in worker.ts) reads `tasks` at construction time
- * and validates them. The DO alarm fires `runTask(name, env)` on the
- * configured schedule; each fire is recorded in the DO's `cron_history`
- * table and pushed to subscribers over `/ws/cron/:roomId`.
- *
- * The heartbeat task here is the low-cost liveness probe used by both
- * the cron e2e spec and as a quick sanity check after a deploy. To add
- * your own task, append a {name, intervalMinutes} or {name, schedule,
- * timezone} entry to `tasks` and dispatch on `name` inside `runTask`.
- */
-
-import type { CronTask } from 'deepspace/worker'
-
-export const tasks: CronTask[] = [
-  { name: 'heartbeat', intervalMinutes: 1 },
-]
-
-export async function runTask(_name: string, _env: unknown): Promise<void> {
-  // No-op work — the DO records every invocation in cron_history regardless,
-  // which is what the e2e spec asserts against. Real apps would dispatch on
-  // `_name` here and call into integrations / records via buildCronContext.
-}