@beignet/cli 0.0.49 → 0.0.50

package/src/templates/agents.ts

@@ -64,6 +64,8 @@ is a silent failure — the file exists but never runs:
   fallback and rejects unmarked custom inline wiring as a conflict.
 - Listeners must be added to the \`listeners\` array in \`server/listeners.ts\`
   and wired through a \`registerListeners(...)\` call in server provider wiring.
+  Register them in \`start()\`, await \`registration.ready\`, and await
+  \`registration.unsubscribe()\` in \`stop()\`.
 - Apps using Inngest must also spread feature job registries into
   \`inngestJobs\` in \`server/inngest.ts\`.
 - Apps using runtime integrity must list workflow registries in
@@ -157,6 +159,15 @@ to one feature. The graph honors the app's complete TypeScript \`baseUrl\` and
 edges as proof that no relationship exists. Registration diagnostics expose
 the declaration as \`subject.file\` and \`subject.exportName\`.
 
+After editing in a Git worktree, run \`${cli} map --changed\` before the full
+check. It reports direct changes, reverse imports, one-hop semantic consumers,
+feature context, and unresolved evidence without claiming that the change is
+correct. Use \`--base <local-ref>\` for branch-wide impact from the merge base;
+Beignet never fetches the ref. Recognized guide files and
+root documentation-directory content stay non-impacting; other \`.mdx\` and
+\`.txt\` paths remain application changes. Changed files with no mapped concept
+appear as explicit gaps.
+
 ## Package skills
 
 This app trusts Beignet's package-shipped agent skills through
@@ -173,6 +184,12 @@ skill-loading block.
 
 ## Placement rules
 
+- Checked-in SQL migrations and Drizzle metadata live in root \`drizzle/\`.
+- Seed generators compose feature seeds through the optional
+  \`server/seed.ts\` entrypoint.
+- Long-running runtime entrypoints such as BullMQ workers live under optional
+  \`server/workers/\`; never start worker loops in lifecycle providers or
+  serverless route modules.
 - Feature artifacts live under \`features/<feature>/\`, with tests in
   \`features/<feature>/tests/\` (not \`__tests__/\`).
 - Feature-specific client data-fetching helpers, query options, mutation
@@ -204,7 +221,10 @@ stable operation IDs, hashes, exact patches, and current diagnostics before
 passing its \`planId\` and optional \`fixIds\` to \`doctor_fix\`. Guarded
 apply returns the same plan metadata and inspection payload as the CLI. Use
 \`app_map\` before broad code search and pass a feature
-or node kinds to keep context focused. Use \`explain\` for source-backed
+or node kinds to keep context focused. After edits, pass
+\`{ changed: true, base?: string }\` for the same report as
+\`${cli} map --changed --json\`; changed mode rejects projection and diagnostic
+inputs. Use \`explain\` for source-backed
 relationships, conventions, findings, and suggested files for any mapped
 concept or diagnostic; its kinds match the app map. Use \`check\` after edits
 to run the complete validation loop; it returns the same versioned result as

package/src/templates/base.ts

@@ -324,7 +324,10 @@ Use \`${cli} make feature projects --recipe full-slice\` when you want a richer
 
 Run \`${cli} map\` for the current architecture or \`${cli} map --json\` for
 the versioned graph used by coding agents. Add \`--feature todos\` to focus on
-one slice and its direct relationships.
+one slice and its direct relationships. After editing in a Git worktree, run
+\`${cli} map --changed\` to inspect direct changes, potential semantic
+consumers, feature context, and unresolved evidence before \`${cli} check\`.
+The changed map is report-only and does not prove correctness.
 
 - \`features/todos/contracts.ts\` owns the HTTP contract and reuses shared feature schemas.
 - \`features/todos/schemas.ts\` owns shared DTO and validation schemas used by contracts, use cases, ports, tests, and clients.