@stravica-ai/digital-operator-pa 0.1.52 → 0.1.53

package/dist/engineering-pa-scaffold/src/generator.mjs

@@ -348,6 +348,12 @@ export function buildGitignore() {
     '# nature, so it is never committed or synced between hosts.',
     'operator/config/preferences.local.json',
     '',
+    '# Review surface — per-install submit token (never committed) and the',
+    "# reviews inbox itself (a colleague's inline comments are their own",
+    '# working notes, not shared source).',
+    'operator/config/review-token.local.json',
+    'operator/content/reviews/',
+    '',
   ].join('\n');
 }
 
@@ -765,7 +771,7 @@ export function buildDistillationScheduleJson(config, seams = {}) {
 /**
  * Build the .claude/settings.json contents.
  *
- * Three things:
+ * Four things:
  *   1. `permissions.deny` for the built-in `deep-research` skill and
  *      workflow. The core operating model (Bucket 4) directs the PA to
  *      the `/research` verb, which persists a session and promotes
@@ -773,27 +779,67 @@ export function buildDistillationScheduleJson(config, seams = {}) {
  *      `deep-research` skill produces no such trail and would silently
  *      short-circuit the discipline; deny is the correct default.
  *
- *   2. `hooks.PreToolUse` wiring `pa-coordinator-hook` for the matcher
+ *   2. `permissions.allow` scoped to the invoking instance's own
+ *      `com.<paName>.*` launchd labels and the `pnpm exec scheduler`
+ *      verbs the mandatory librarian step drives. The `/onboard`
+ *      walkthrough fires `launchctl kickstart -k gui/<uid>/com.<paName>.<paName>-distillation-sweep`
+ *      as its distillation-schedule proof; without a preauth the
+ *      built-in permission classifier hard-stops that call on a fresh
+ *      colleague estate, and the whole self-learning loop fails to
+ *      wire on first session (w-2026-09-19-dave-004). The allow-list
+ *      is scoped to THIS instance's own paName so a laptop that
+ *      carries another estate's plists is never preauthorised to
+ *      touch them.
+ *
+ *   3. `hooks.PreToolUse` wiring `pa-coordinator-hook` for the matcher
  *      the coordinator-hook doc gives. The hook is a no-op unless the
  *      operator sets `PA_COORDINATOR_MODE=1` in their shell, so the
  *      scaffold ships the wiring inert. A per-repo overlay slot is
  *      scaffolded alongside as `.claude/coordinator-overlay.json`.
  *
- *   3. `hooks.SessionStart` wiring `distill health --hook-envelope` so
+ *   4. `hooks.SessionStart` wiring `distill health --hook-envelope` so
  *      every session boots with a `distillationHealth (live)` block at
  *      the top of the context. Reads the local distill ledger + the
- *      scaffolded schedule file — never spawns claude, never triggers a
+ *      scaffolded schedule file, never spawns claude, never triggers a
  *      sweep, cheap to run. The block warns loudly when the schedule is
  *      missing (fresh scaffold pre-/onboard), disabled, or the last run
  *      is stale, so the whole self-learning loop cannot die silently
  *      the way it did on the WSD-laptop cold install of 0.1.41. Invoked
  *      through `pnpm exec` because Claude Code hook subprocesses do not
  *      inherit the pnpm-augmented PATH the interactive session enjoys.
+ *
+ * @param {object} [opts]
+ * @param {string} [opts.paName] - Instance paName. When set, the allow
+ *   list is scoped to `com.<paName>.*` labels only. When omitted, the
+ *   allow list is empty (callers with no paName in scope get the same
+ *   pre-feature shape).
  */
-export function buildClaudeSettingsJson() {
+export function buildClaudeSettingsJson(opts = {}) {
+  const paName = typeof opts.paName === 'string' && opts.paName.length > 0
+    ? opts.paName
+    : null;
+  const allow = paName
+    ? [
+      // launchctl verbs scoped to this instance's own labels. The
+      // wildcard is on the id half; the `com.<paName>.` prefix is
+      // fixed so the preauth never widens beyond this estate.
+      `Bash(launchctl kickstart -k gui/*/com.${paName}.*)`,
+      `Bash(launchctl bootout gui/*/com.${paName}.*)`,
+      `Bash(launchctl bootstrap gui/* */Library/LaunchAgents/com.${paName}.*.plist)`,
+      // The mandatory librarian step's exact command line, plus the
+      // scheduler verbs adjacent to it so a fresh-instance operator
+      // does not hit a permission prompt in the middle of onboarding.
+      'Bash(pnpm exec scheduler install *)',
+      'Bash(pnpm exec scheduler list*)',
+      'Bash(pnpm exec scheduler remove *)',
+      'Bash(pnpm exec scheduler verify *)',
+      'Bash(pnpm exec scheduler detect*)',
+    ]
+    : [];
   return {
     permissions: {
       deny: ['Skill(skill:deep-research)', 'Workflow(name:deep-research)'],
+      ...(allow.length ? { allow } : {}),
     },
     hooks: {
       PreToolUse: [
@@ -941,7 +987,7 @@ export function buildPlanFromTemplates(config, templates) {
   plan.push({ kind: 'file', path: '.nvmrc', contents: '24\n' });
   plan.push({ kind: 'file', path: 'pnpm-workspace.yaml', contents: buildInstanceWorkspaceYaml() });
 
-  plan.push({ kind: 'json', path: '.claude/settings.json', contents: buildClaudeSettingsJson() });
+  plan.push({ kind: 'json', path: '.claude/settings.json', contents: buildClaudeSettingsJson({ paName }) });
   // /research slash command: rendered from the packaged core doc so the
   // command a colleague gets is exactly what the platform ships. The scaffold
   // never re-authors it, and there is no template to drift.

package/dist/engineering-pa-scaffold/templates/CLAUDE.md.template

@@ -72,6 +72,21 @@ Stay available for {OPERATOR_NAME}. Preserve main-thread context. Lead the team
 10. **All tool development via tool-developer, in Node.js.** No shell scripts, ever -- cross-platform breakage.
 11. **When work returns, evaluate the process as well as the result.** Feed team improvement continuously -- role defs, briefs, autonomy envelopes, roster.
 
+### Dispatch routing (recognise-and-hand-off cues)
+
+This block is the routing surface the PA consults when deciding inline-versus-dispatch. Roles that need to fire on cues rather than name-checks ship their cues here as liftable blocks. A missed first routing is a common case, so recovery cues sit alongside primary cues.
+
+**Agentic Workflow Designer (`agentic-workflow-designer`).** Dispatch when a correct answer would contain a flow -- more than one actor, or at least one decision or approval point -- and NEVER sketch the flow inline first. Do not answer inline and offer a designed version later; the inline sketch anchors the operator on an unruled, unmapped design and forecloses the role's actual deliverable.
+
+- "design a process / workflow / pipeline / automation" for anything
+- anything involving status transitions, approval steps, handoffs, triage rules, escalation paths, or "who does what when"
+- any automation that will run unattended: scheduled, triggered, or looping
+- a correction of a prose answer toward an artefact ("as a designed workflow", "produce the real artefact", "not prose") -- a second ask in this shape after an inline answer means the first ask was a missed dispatch, not that a new kind of request has arrived
+
+Non-cues (answer inline): a status question about an existing workflow; a factual question about the role or the Rule of Two; a prose edit to a ruled diagram's supporting text that changes no lane, gate, or mapping.
+
+Project bootstrap is the designer's own first act -- the dispatching brief does not need to pre-create a project. A workflow design is project work, never knowledge capture: writing the design under `knowledge/` or `operator/knowledge/` is a routing failure even when the content is good, because the knowledge tree is the cheap path only because it needs no bootstrap.
+
 **Deeper reference:** `operator/knowledge/delegation-dispatch/` -- briefing contract examples, delegation-mode selection tree, task-group patterns, role catalogue, team improvement loop, dispatch envelope (capability matrix, isolation semantics, MCP inheritance).
 
 <!-- OPERATOR: add operator-specific dispatch patterns here (surface-specific brief bolt-ons, an operator-specialised role list, per-project orchestration convention). -->

package/dist/engineering-pa-workspace/app/nav.json

@@ -48,6 +48,12 @@
     "href": "/core/tools/workspace/app/repos.html",
     "section": "Workspace"
   },
+  {
+    "id": "reviews",
+    "label": "Reviews",
+    "href": "/core/tools/workspace/app/reviews.html",
+    "section": "Workspace"
+  },
   {
     "id": "delegations",
     "label": "Delegations",