@aperant/framework 0.9.0 → 0.11.0

package/dist/cli/verify-proof/runtime-detect.mjs

@@ -1,209 +1,14 @@
 /**
- * runtime-detect.mjs — pure project-shape capability detection.
+ * verify-proof/runtime-detect.mjs — pure project-shape capability detection.
  *
- * Extracted from packages/core/src/prompts/prompt-loader.ts:572-595 so the
- * framework CLI is self-contained (no @aperant/core dep). Same heuristics:
- * read package.json's dependencies + devDependencies, return a capability
- * record the resolver can score against.
- *
- * Pattern: pure data in → pure data out. No filesystem walking, no exec.
- * Use loadRuntimeCapabilities(projectDir) for the cwd-rooted variant.
- *
- * v0.8.6 — `loadRuntimeCapabilities` now ALSO walks `apps/*` by default
- * (configurable via the second arg `{monorepo_globs}`) and OR-merges
- * each match's `package.json` capabilities with the root. The default
- * `['apps/*']` matches the canonical Aperant monorepo layout; adopters
- * whose monorepo lives elsewhere (e.g. `packages/apps/*`) pass a
- * custom `monorepo_globs`. Setting `monorepo_globs: []` disables the
- * walk entirely (root-only escape hatch).
- */
-import { existsSync, readdirSync, readFileSync, statSync } from 'node:fs';
-import { join, resolve } from 'node:path';
-/**
- * @typedef {Object} RuntimeCapabilities
- * @property {boolean} is_electron
- * @property {boolean} is_tauri
- * @property {boolean} is_nextjs
- * @property {boolean} is_nuxt
- * @property {boolean} is_web_frontend
- * @property {boolean} is_expo
- * @property {boolean} is_react_native
- * @property {boolean} has_node
- */
-/** A capability record with every flag defaulted to false. */
-function emptyCapabilities() {
-    return {
-        is_electron: false,
-        is_tauri: false,
-        is_nextjs: false,
-        is_nuxt: false,
-        is_web_frontend: false,
-        is_expo: false,
-        is_react_native: false,
-        has_node: false,
-    };
-}
-/**
- * Detect runtime capabilities from a parsed package.json object.
- *
- * @param {Record<string, unknown> | null} packageJson
- * @returns {RuntimeCapabilities}
+ * The implementation now lives in util/runtime-capabilities.mjs so the install
+ * layer can share it WITHOUT install/ importing from verify-proof/ (the
+ * layer-boundary rule). Re-exported here byte-for-byte so every existing
+ * `import { … } from '../verify-proof/runtime-detect.mjs'` call site (and the
+ * `RuntimeCapabilities` typedef references) keep working unchanged.
  */
-export function detectFromPackageJson(packageJson) {
-    const capabilities = emptyCapabilities();
-    if (packageJson === null || typeof packageJson !== 'object')
-        return capabilities;
-    const allDeps = {
-        ...(packageJson.dependencies ?? {}) /** @type {Record<string,string>} */,
-        ...(packageJson.devDependencies ?? {}) /** @type {Record<string,string>} */,
-    };
-    const deps = new Set(Object.keys(allDeps).map((k) => k.toLowerCase()));
-    if (deps.has('electron') || [...deps].some((d) => d.startsWith('@electron'))) {
-        capabilities.is_electron = true;
-    }
-    if (deps.has('@tauri-apps/api') || deps.has('tauri')) {
-        capabilities.is_tauri = true;
-    }
-    if (deps.has('expo'))
-        capabilities.is_expo = true;
-    if (deps.has('react-native'))
-        capabilities.is_react_native = true;
-    // Web frontends — react/vue/svelte/angular/solid → frontend. BUT: an
-    // Electron app commonly bundles React as its renderer; in that case the
-    // runtime is "electron", not "web_frontend". Electron + react-native +
-    // expo + tauri all win over the web flag.
-    const isNativeContainer = capabilities.is_electron ||
-        capabilities.is_tauri ||
-        capabilities.is_react_native ||
-        capabilities.is_expo;
-    const webFrameworks = ['react', 'vue', 'svelte', 'angular', 'solid'];
-    if (!isNativeContainer && webFrameworks.some((f) => deps.has(f))) {
-        capabilities.is_web_frontend = true;
-    }
-    if (deps.has('next')) {
-        capabilities.is_nextjs = true;
-        capabilities.is_web_frontend = true;
-    }
-    if (deps.has('nuxt')) {
-        capabilities.is_nuxt = true;
-        capabilities.is_web_frontend = true;
-    }
-    if (deps.has('vite') && !isNativeContainer) {
-        capabilities.is_web_frontend = true;
-    }
-    // Node-ish? Anything with a package.json + an entry point counts.
-    if (typeof packageJson.main === 'string' || typeof packageJson.module === 'string') {
-        capabilities.has_node = true;
-    }
-    if (!capabilities.has_node && packageJson.scripts && typeof packageJson.scripts === 'object') {
-        capabilities.has_node = true;
-    }
-    return capabilities;
-}
+export { detectFromPackageJson, loadRuntimeCapabilities, } from '../util/runtime-capabilities.mjs';
 /**
- * Load and detect capabilities from a project directory's package.json.
- * v0.8.6 — also walks `monorepo_globs` (default `['apps/*']`) and
- * OR-merges each match's capabilities with the root.
- *
- * @param {string} projectDir
- * @param {{monorepo_globs?: string[]}} [opts]
- * @returns {RuntimeCapabilities}
- */
-export function loadRuntimeCapabilities(projectDir, opts) {
-    const root = resolve(projectDir);
-    const rootPkgPath = join(root, 'package.json');
-    let rootCaps = emptyCapabilities();
-    if (existsSync(rootPkgPath)) {
-        try {
-            rootCaps = detectFromPackageJson(JSON.parse(readFileSync(rootPkgPath, 'utf-8')));
-        }
-        catch {
-            /* fall through with empty caps */
-        }
-    }
-    // Default to the canonical Aperant monorepo layout. Passing `[]`
-    // disables the walk entirely (root-only escape hatch per spec ID-05).
-    const globs = opts && Array.isArray(opts.monorepo_globs) ? opts.monorepo_globs : ['apps/*'];
-    if (globs.length === 0)
-        return rootCaps;
-    let merged = rootCaps;
-    for (const glob of globs) {
-        const matches = expandSimpleGlob(root, glob);
-        for (const dir of matches) {
-            const childPkgPath = join(dir, 'package.json');
-            if (!existsSync(childPkgPath))
-                continue;
-            try {
-                const childCaps = detectFromPackageJson(JSON.parse(readFileSync(childPkgPath, 'utf-8')));
-                merged = orMergeCapabilities(merged, childCaps);
-            }
-            catch {
-                /* skip malformed package.json */
-            }
-        }
-    }
-    return merged;
-}
-/**
- * Expand a simple `prefix/*` glob against the root. Supports ONLY the
- * `<dir>/*` shape (matches each direct subdirectory of `<dir>`). Other
- * glob syntax is intentionally rejected — v1 keeps the dep surface
- * small. Fails closed on malformed patterns (returns []).
- *
- * @param {string} root
- * @param {string} glob
- * @returns {string[]}
- */
-function expandSimpleGlob(root, glob) {
-    if (typeof glob !== 'string' || !glob.endsWith('/*'))
-        return [];
-    const prefix = glob.slice(0, -2);
-    if (prefix.length === 0 || prefix.includes('*'))
-        return [];
-    const dir = join(root, prefix);
-    if (!existsSync(dir))
-        return [];
-    let entries;
-    try {
-        entries = readdirSync(dir);
-    }
-    catch {
-        return [];
-    }
-    const matches = [];
-    for (const name of entries) {
-        const sub = join(dir, name);
-        try {
-            if (statSync(sub).isDirectory())
-                matches.push(sub);
-        }
-        catch {
-            /* skip unreadable entries */
-        }
-    }
-    return matches;
-}
-/**
- * Boolean OR-merge of two capability records. Any flag true in either
- * input is true in the output. The "Electron wins over web" rule from
- * `detectFromPackageJson` is preserved when this is called repeatedly —
- * each child's flags are honest about that child's own shape, and the
- * OR-merge just unions them.
- *
- * @param {RuntimeCapabilities} a
- * @param {RuntimeCapabilities} b
- * @returns {RuntimeCapabilities}
+ * @typedef {import('../util/runtime-capabilities.mjs').RuntimeCapabilities} RuntimeCapabilities
  */
-function orMergeCapabilities(a, b) {
-    return {
-        is_electron: a.is_electron || b.is_electron,
-        is_tauri: a.is_tauri || b.is_tauri,
-        is_nextjs: a.is_nextjs || b.is_nextjs,
-        is_nuxt: a.is_nuxt || b.is_nuxt,
-        is_web_frontend: a.is_web_frontend || b.is_web_frontend,
-        is_expo: a.is_expo || b.is_expo,
-        is_react_native: a.is_react_native || b.is_react_native,
-        has_node: a.has_node || b.has_node,
-    };
-}
 //# sourceMappingURL=runtime-detect.mjs.map

package/dist/cli/verify-proof/runtime-detect.mjs.map

@@ -1 +1 @@
-{"version":3,"file":"runtime-detect.mjs","sourceRoot":"","sources":["../../../src/cli/verify-proof/runtime-detect.mjs"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;GAkBG;AAEH,OAAO,EAAE,UAAU,EAAE,WAAW,EAAE,YAAY,EAAE,QAAQ,EAAE,MAAM,SAAS,CAAA;AACzE,OAAO,EAAE,IAAI,EAAE,OAAO,EAAE,MAAM,WAAW,CAAA;AAEzC;;;;;;;;;;GAUG;AAEH,8DAA8D;AAC9D,SAAS,iBAAiB;IACzB,OAAO;QACN,WAAW,EAAE,KAAK;QAClB,QAAQ,EAAE,KAAK;QACf,SAAS,EAAE,KAAK;QAChB,OAAO,EAAE,KAAK;QACd,eAAe,EAAE,KAAK;QACtB,OAAO,EAAE,KAAK;QACd,eAAe,EAAE,KAAK;QACtB,QAAQ,EAAE,KAAK;KACf,CAAA;AACF,CAAC;AAED;;;;;GAKG;AACH,MAAM,UAAU,qBAAqB,CAAC,WAAW;IAChD,MAAM,YAAY,GAAG,iBAAiB,EAAE,CAAA;IACxC,IAAI,WAAW,KAAK,IAAI,IAAI,OAAO,WAAW,KAAK,QAAQ;QAAE,OAAO,YAAY,CAAA;IAEhF,MAAM,OAAO,GAAG;QACf,GAAG,CAAC,WAAW,CAAC,YAAY,IAAI,EAAE,CAAC,CAAC,oCAAoC;QACxE,GAAG,CAAC,WAAW,CAAC,eAAe,IAAI,EAAE,CAAC,CAAC,oCAAoC;KAC3E,CAAA;IACD,MAAM,IAAI,GAAG,IAAI,GAAG,CAAC,MAAM,CAAC,IAAI,CAAC,OAAO,CAAC,CAAC,GAAG,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,WAAW,EAAE,CAAC,CAAC,CAAA;IAEtE,IAAI,IAAI,CAAC,GAAG,CAAC,UAAU,CAAC,IAAI,CAAC,GAAG,IAAI,CAAC,CAAC,IAAI,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,UAAU,CAAC,WAAW,CAAC,CAAC,EAAE,CAAC;QAC9E,YAAY,CAAC,WAAW,GAAG,IAAI,CAAA;IAChC,CAAC;IACD,IAAI,IAAI,CAAC,GAAG,CAAC,iBAAiB,CAAC,IAAI,IAAI,CAAC,GAAG,CAAC,OAAO,CAAC,EAAE,CAAC;QACtD,YAAY,CAAC,QAAQ,GAAG,IAAI,CAAA;IAC7B,CAAC;IACD,IAAI,IAAI,CAAC,GAAG,CAAC,MAAM,CAAC;QAAE,YAAY,CAAC,OAAO,GAAG,IAAI,CAAA;IACjD,IAAI,IAAI,CAAC,GAAG,CAAC,cAAc,CAAC;QAAE,YAAY,CAAC,eAAe,GAAG,IAAI,CAAA;IAEjE,qEAAqE;IACrE,wEAAwE;IACxE,uEAAuE;IACvE,0CAA0C;IAC1C,MAAM,iBAAiB,GACtB,YAAY,CAAC,WAAW;QACxB,YAAY,CAAC,QAAQ;QACrB,YAAY,CAAC,eAAe;QAC5B,YAAY,CAAC,OAAO,CAAA;IACrB,MAAM,aAAa,GAAG,CAAC,OAAO,EAAE,KAAK,EAAE,QAAQ,EAAE,SAAS,EAAE,OAAO,CAAC,CAAA;IACpE,IAAI,CAAC,iBAAiB,IAAI,aAAa,CAAC,IAAI,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,IAAI,CAAC,GAAG,CAAC,CAAC,CAAC,CAAC,EAAE,CAAC;QAClE,YAAY,CAAC,eAAe,GAAG,IAAI,CAAA;IACpC,CAAC;IAED,IAAI,IAAI,CAAC,GAAG,CAAC,MAAM,CAAC,EAAE,CAAC;QACtB,YAAY,CAAC,SAAS,GAAG,IAAI,CAAA;QAC7B,YAAY,CAAC,eAAe,GAAG,IAAI,CAAA;IACpC,CAAC;IACD,IAAI,IAAI,CAAC,GAAG,CAAC,MAAM,CAAC,EAAE,CAAC;QACtB,YAAY,CAAC,OAAO,GAAG,IAAI,CAAA;QAC3B,YAAY,CAAC,eAAe,GAAG,IAAI,CAAA;IACpC,CAAC;IACD,IAAI,IAAI,CAAC,GAAG,CAAC,MAAM,CAAC,IAAI,CAAC,iBAAiB,EAAE,CAAC;QAC5C,YAAY,CAAC,eAAe,GAAG,IAAI,CAAA;IACpC,CAAC;IAED,kEAAkE;IAClE,IAAI,OAAO,WAAW,CAAC,IAAI,KAAK,QAAQ,IAAI,OAAO,WAAW,CAAC,MAAM,KAAK,QAAQ,EAAE,CAAC;QACpF,YAAY,CAAC,QAAQ,GAAG,IAAI,CAAA;IAC7B,CAAC;IACD,IAAI,CAAC,YAAY,CAAC,QAAQ,IAAI,WAAW,CAAC,OAAO,IAAI,OAAO,WAAW,CAAC,OAAO,KAAK,QAAQ,EAAE,CAAC;QAC9F,YAAY,CAAC,QAAQ,GAAG,IAAI,CAAA;IAC7B,CAAC;IAED,OAAO,YAAY,CAAA;AACpB,CAAC;AAED;;;;;;;;GAQG;AACH,MAAM,UAAU,uBAAuB,CAAC,UAAU,EAAE,IAAI;IACvD,MAAM,IAAI,GAAG,OAAO,CAAC,UAAU,CAAC,CAAA;IAChC,MAAM,WAAW,GAAG,IAAI,CAAC,IAAI,EAAE,cAAc,CAAC,CAAA;IAC9C,IAAI,QAAQ,GAAG,iBAAiB,EAAE,CAAA;IAClC,IAAI,UAAU,CAAC,WAAW,CAAC,EAAE,CAAC;QAC7B,IAAI,CAAC;YACJ,QAAQ,GAAG,qBAAqB,CAAC,IAAI,CAAC,KAAK,CAAC,YAAY,CAAC,WAAW,EAAE,OAAO,CAAC,CAAC,CAAC,CAAA;QACjF,CAAC;QAAC,MAAM,CAAC;YACR,kCAAkC;QACnC,CAAC;IACF,CAAC;IAED,iEAAiE;IACjE,sEAAsE;IACtE,MAAM,KAAK,GAAG,IAAI,IAAI,KAAK,CAAC,OAAO,CAAC,IAAI,CAAC,cAAc,CAAC,CAAC,CAAC,CAAC,IAAI,CAAC,cAAc,CAAC,CAAC,CAAC,CAAC,QAAQ,CAAC,CAAA;IAC3F,IAAI,KAAK,CAAC,MAAM,KAAK,CAAC;QAAE,OAAO,QAAQ,CAAA;IAEvC,IAAI,MAAM,GAAG,QAAQ,CAAA;IACrB,KAAK,MAAM,IAAI,IAAI,KAAK,EAAE,CAAC;QAC1B,MAAM,OAAO,GAAG,gBAAgB,CAAC,IAAI,EAAE,IAAI,CAAC,CAAA;QAC5C,KAAK,MAAM,GAAG,IAAI,OAAO,EAAE,CAAC;YAC3B,MAAM,YAAY,GAAG,IAAI,CAAC,GAAG,EAAE,cAAc,CAAC,CAAA;YAC9C,IAAI,CAAC,UAAU,CAAC,YAAY,CAAC;gBAAE,SAAQ;YACvC,IAAI,CAAC;gBACJ,MAAM,SAAS,GAAG,qBAAqB,CAAC,IAAI,CAAC,KAAK,CAAC,YAAY,CAAC,YAAY,EAAE,OAAO,CAAC,CAAC,CAAC,CAAA;gBACxF,MAAM,GAAG,mBAAmB,CAAC,MAAM,EAAE,SAAS,CAAC,CAAA;YAChD,CAAC;YAAC,MAAM,CAAC;gBACR,iCAAiC;YAClC,CAAC;QACF,CAAC;IACF,CAAC;IACD,OAAO,MAAM,CAAA;AACd,CAAC;AAED;;;;;;;;;GASG;AACH,SAAS,gBAAgB,CAAC,IAAI,EAAE,IAAI;IACnC,IAAI,OAAO,IAAI,KAAK,QAAQ,IAAI,CAAC,IAAI,CAAC,QAAQ,CAAC,IAAI,CAAC;QAAE,OAAO,EAAE,CAAA;IAC/D,MAAM,MAAM,GAAG,IAAI,CAAC,KAAK,CAAC,CAAC,EAAE,CAAC,CAAC,CAAC,CAAA;IAChC,IAAI,MAAM,CAAC,MAAM,KAAK,CAAC,IAAI,MAAM,CAAC,QAAQ,CAAC,GAAG,CAAC;QAAE,OAAO,EAAE,CAAA;IAC1D,MAAM,GAAG,GAAG,IAAI,CAAC,IAAI,EAAE,MAAM,CAAC,CAAA;IAC9B,IAAI,CAAC,UAAU,CAAC,GAAG,CAAC;QAAE,OAAO,EAAE,CAAA;IAC/B,IAAI,OAAO,CAAA;IACX,IAAI,CAAC;QACJ,OAAO,GAAG,WAAW,CAAC,GAAG,CAAC,CAAA;IAC3B,CAAC;IAAC,MAAM,CAAC;QACR,OAAO,EAAE,CAAA;IACV,CAAC;IACD,MAAM,OAAO,GAAG,EAAE,CAAA;IAClB,KAAK,MAAM,IAAI,IAAI,OAAO,EAAE,CAAC;QAC5B,MAAM,GAAG,GAAG,IAAI,CAAC,GAAG,EAAE,IAAI,CAAC,CAAA;QAC3B,IAAI,CAAC;YACJ,IAAI,QAAQ,CAAC,GAAG,CAAC,CAAC,WAAW,EAAE;gBAAE,OAAO,CAAC,IAAI,CAAC,GAAG,CAAC,CAAA;QACnD,CAAC;QAAC,MAAM,CAAC;YACR,6BAA6B;QAC9B,CAAC;IACF,CAAC;IACD,OAAO,OAAO,CAAA;AACf,CAAC;AAED;;;;;;;;;;GAUG;AACH,SAAS,mBAAmB,CAAC,CAAC,EAAE,CAAC;IAChC,OAAO;QACN,WAAW,EAAE,CAAC,CAAC,WAAW,IAAI,CAAC,CAAC,WAAW;QAC3C,QAAQ,EAAE,CAAC,CAAC,QAAQ,IAAI,CAAC,CAAC,QAAQ;QAClC,SAAS,EAAE,CAAC,CAAC,SAAS,IAAI,CAAC,CAAC,SAAS;QACrC,OAAO,EAAE,CAAC,CAAC,OAAO,IAAI,CAAC,CAAC,OAAO;QAC/B,eAAe,EAAE,CAAC,CAAC,eAAe,IAAI,CAAC,CAAC,eAAe;QACvD,OAAO,EAAE,CAAC,CAAC,OAAO,IAAI,CAAC,CAAC,OAAO;QAC/B,eAAe,EAAE,CAAC,CAAC,eAAe,IAAI,CAAC,CAAC,eAAe;QACvD,QAAQ,EAAE,CAAC,CAAC,QAAQ,IAAI,CAAC,CAAC,QAAQ;KAClC,CAAA;AACF,CAAC"}
+{"version":3,"file":"runtime-detect.mjs","sourceRoot":"","sources":["../../../src/cli/verify-proof/runtime-detect.mjs"],"names":[],"mappings":"AAAA;;;;;;;;GAQG;AAEH,OAAO,EACN,qBAAqB,EACrB,uBAAuB,GACvB,MAAM,kCAAkC,CAAA;AAEzC;;GAEG"}

package/dist/plugin/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "aperant",
-  "version": "0.9.0",
+  "version": "0.11.0",
   "description": "AI coding framework — composable skills for planning, executing, verifying, and reviewing code with any LLM provider. Works as Claude Code commands, Codex tasks, or programmatically.",
   "author": {
     "name": "Mikalsen AI",
@@ -25,6 +25,7 @@
     "skills/apt",
     "skills/apt-author-skill",
     "skills/apt-bootstrap",
+    "skills/apt-catch-up",
     "skills/apt-caveman",
     "skills/apt-classify",
     "skills/apt-close-task",

package/dist/plugin/agents/apt-verifier.md

@@ -105,9 +105,12 @@ Either shape is accepted:
 
 Gate G8 (`consistency-check`) enforces this on ship via rules R4
 (finding-propagation) and R5 (verdict-consistency):
-- `verdict: "approved"` is incompatible with any unresolved `critical`
-  review finding — use `approved-with-notes` as the escape hatch when you
-  intentionally ship over a flagged finding, and cite it in `findings.notes`.
+- `verdict: "approved"` or `verdict: "approved-with-notes"` is incompatible
+  with any unresolved `critical` or `major` review finding (G42 Phase 1).
+  Neither verdict escapes R5 for blocking-severity findings. The sole bypass
+  is `--force --reason "<why>"` on the gate CLI (audit-logged). For
+  non-blocking findings (suggestion/note/info/nitpick), cite them in
+  `findings.notes` and use `approved-with-notes`.
 - `verdict: "rejected"` requires at least one cited finding (rejected
   without evidence is treated as drift).
 

package/dist/plugin/skills/apt/SKILL.md

@@ -75,6 +75,34 @@ SessionStart hook — zero latency on /apt. If `update_check` is null,
 no chip. Skip the chip entirely once the user has run `/apt:update`
 in the current session (the cache is cleared there).
 
+**Catch-up panel (runtime-agnostic):** if the route envelope includes a
+non-null `catch_up` field, print the combined panel BEFORE the mode handler
+runs, regardless of runtime (Claude Code, Codex, Gemini, Cursor, …). The
+panel has two halves; render `catch_up.welcome_back` first, then
+`catch_up.team_digest`. Omit a half whose field is null.
+
+If `catch_up.welcome_back` is present (your own half-finished work):
+
+```
+Where you left off: {description} — {lifecycle_phase}{current_subtask ? " · subtask " + current_subtask : ""} ({relative_time})
+{next_step ? "  Next: " + next_step : ""}
+{others_count > 0 ? "  (+" + others_count + " others · /apt:resume)" : ""}
+```
+
+If `catch_up.team_digest` is present (what teammates merged while you were away):
+
+```
+While you were away:
+{for each entry in team_digest.entries: "  #" + number + " " + title + " — " + author}
+{team_digest.more_count > 0 ? "  +" + team_digest.more_count + " more on main" : ""}
+```
+
+This is display-only here — the Last-Seen Marker advance happens in route.mjs,
+not in this skill. The panel is computed lazily on interactive (TTY) calls
+only; non-TTY/background/spawned calls carry no `catch_up` field. Do not call
+it an "activity feed", "changelog", or "notifications" — it is the
+Welcome-Back Summary + Team-Change Digest.
+
 Then proceed to the matching mode handler below. Do NOT deviate from the routing decision.
 </mandatory_first_step>
 
@@ -129,6 +157,7 @@ Show available commands table:
 | `apt:scan` | Discover standards + refresh feature registry |
 | `apt:docs` | Generate/update documentation |
 | `apt:resume` | Restore context after session break |
+| `apt:catch-up` | Re-view the catch-up panel (Welcome-Back + Team-Change Digest) — never advances the Last-Seen Marker |
 | `apt:pause` | Human-initiated handoff — save state when YOU need to stop |
 | `apt:ship` | Create PR with traceability |
 | `apt:close-task` | Post-merge closer — confirm PR merged, flip phase, drain narration ledger |

package/dist/plugin/skills/apt-catch-up/SKILL.md

@@ -0,0 +1,79 @@
+---
+name: apt:catch-up
+description: "Re-view the catch-up panel (Welcome-Back + Team-Change Digest) on demand"
+apt-skill-version: {{APT_VERSION}}
+stage: resume
+intent: capture
+when_to_use: "The user dismissed the auto catch-up panel on their last /apt and wants to re-summon it — an idempotent re-view of where they left off plus what teammates merged. Distinct from /apt:resume (full context restore) and never advances the Last-Seen Marker."
+user_invocable: true
+internal: false
+spawns_agent: false
+agent_name: null
+task_context: none
+default_execution_mode: auto
+execution_modes:
+  - auto
+allowed-tools: "Bash, Read"
+argument-hint: "apt:catch-up"
+gates: []
+---
+<objective>
+Recompute and display the combined catch-up panel — the **Welcome-Back
+Summary** (your most-recently-active task, phase, next step) and the
+**Team-Change Digest** (the PRs teammates merged to main since you last
+pulled) — exactly as the auto-on-apt display would show it, but **without
+advancing the Last-Seen Marker**. This is a read-only re-view: a user who
+dismissed the auto panel can re-summon it without disturbing the baseline and
+without invoking the heavier `/apt:resume`.
+</objective>
+
+<your_environment>
+- **Working directory:** The project root (where you were invoked)
+- **apt-tools:** `node packages/framework/bin/apt-tools.mjs` or the installed `apt-tools` binary
+- **Last-Seen Marker:** `.aperant/last-seen/{email-slug}.json` (gitignored, per-machine) — this skill READS it but NEVER writes it.
+</your_environment>
+
+<process>
+
+## 1. Recompute the panel (read-only)
+
+```bash
+node packages/framework/bin/apt-tools.mjs catch-up .
+```
+
+This computes the SAME panel the interactive route call produces, against the
+**current** marker — and deliberately does **NOT** call `advanceLastSeen`
+(recompute-only contract). Parse the JSON `catch_up` field from the envelope.
+
+## 2. Render the panel
+
+Render exactly as the `apt/SKILL.md` "Catch-up panel" block does — Welcome-Back
+half first, then the Team-Change Digest half. Omit a half whose field is null.
+
+If `catch_up` is null, tell the user there is nothing new since their last
+visit (no active stale task and no new merges on main).
+
+```
+Where you left off: {description} — {lifecycle_phase} · subtask {current_subtask} ({relative_time})
+  Next: {next_step}
+  (+{others_count} others · /apt:resume)
+
+While you were away:
+  #{number} {title} — {author}
+  +{more_count} more on main
+```
+
+</process>
+
+<notes>
+- **Never advances the marker.** Unlike the auto-on-apt display (which advances
+  the Last-Seen Marker after the panel is evaluated), this command is purely a
+  re-view. Re-running it is idempotent.
+- **Distinct from `/apt:resume`.** Resume restores full context and routes to
+  the next action; catch-up is a lightweight orientation re-view.
+- **v1 is lazy compute.** The panel is computed on demand here, bounded by the
+  commits since your last pull. A background pre-warm worker (like the
+  update-check worker) is a tracked follow-up (LD-12), not part of v1.
+- **Vocabulary.** This is the Welcome-Back Summary + Team-Change Digest — not an
+  "activity feed", "changelog", or "notifications".
+</notes>

package/dist/plugin/skills/apt-pr-review/SKILL.md

@@ -247,10 +247,11 @@ The command resolves in this precedence order:
 
 1. `config.json:pr_review.authorship_overrides['pr-${PR_NUMBER}']` (per-PR pin)
 2. `config.json:pr_review.authorship_override` (global: `owned` | `external` | `auto`)
-3. `gh pr view` → `authorAssociation` + `headRepository.owner.login` vs. viewer login
-   - `authorAssociation IN (OWNER, MEMBER, COLLABORATOR)` AND same-repo branch → **owned**
-   - Fork OR `authorAssociation IN (NONE, CONTRIBUTOR, FIRST_TIME_CONTRIBUTOR)` → **external**
-4. Offline / gh unavailable / ambiguous payload → **unknown**
+3. `gh pr view` → `gh.author.login` vs. viewer login (G44 — `owned` means a PR you **authored**, not a branch you can push to)
+   - Same-repo branch AND `gh.author.login === viewer login` → **owned**
+   - Any other same-repo PR (a teammate's, or a repo-`OWNER` viewing someone else's PR) → **external** (`authorAssociation` is no longer consulted for the `owned` decision — it is retained only in the human-readable signal)
+   - Fork (head-repo owner ≠ base-repo owner) → **external**
+4. Offline / gh unavailable / ambiguous payload → **unknown** (treated as `external` for safety, see below)
 
 When the result is `unknown`, treat it as `external` for safety and prompt the user:
 
@@ -469,6 +470,55 @@ fi
 
 After this point, the per-round artifact root is `.aperant/pr-reviews/pr-${PR_NUMBER}/rounds/${ROUND}/` (the `${REVIEW_ID}` is still used for the git worktree branch and temporary files). Subsequent `git diff` invocations within the round use `${PINNED_HEAD_SHA}` as the head ref.
 
+### Step 4c: Mergeability Pre-Check (PR reviews only)
+
+**Why this exists.** The review diff is `git diff {BASE}...{HEAD}` (three-dot — from the *merge-base*), so it shows the PR's own changes relative to where it branched. It is **blind to drift on `{BASE}` since then** and therefore says nothing about whether the PR still merges cleanly. A PR can pass a glowing review and be unmergeable. This step closes that gap: it is **informational, never blocking** (the review still runs in full), but a conflicting/stale state MUST be surfaced so the reader doesn't trust a review of a diff that no longer applies.
+
+```bash
+# PR-mode only. Query GitHub's authoritative mergeability + measure drift.
+if [ -n "$PR_NUMBER" ]; then
+  MERGE_JSON=$(gh pr view ${PR_NUMBER} --json mergeable,mergeStateStatus,baseRefName 2>/dev/null)
+  MERGEABLE=$(echo "$MERGE_JSON" | jq -r '.mergeable // "UNKNOWN"')
+  MERGE_STATE=$(echo "$MERGE_JSON" | jq -r '.mergeStateStatus // "UNKNOWN"')
+  BASE_REF=$(echo "$MERGE_JSON" | jq -r '.baseRefName // "main"')
+  git fetch origin "${BASE_REF}" 2>/dev/null
+  BEHIND=$(git rev-list --count ${PINNED_HEAD_SHA}..origin/${BASE_REF} 2>/dev/null || echo "?")
+  AHEAD=$(git rev-list --count origin/${BASE_REF}..${PINNED_HEAD_SHA} 2>/dev/null || echo "?")
+
+  # If GitHub reports a conflict (or hasn't computed yet), enumerate the conflicting
+  # files locally without touching any working tree (git >= 2.38):
+  CONFLICT_FILES=""
+  if [ "$MERGEABLE" = "CONFLICTING" ] || [ "$MERGE_STATE" = "DIRTY" ]; then
+    CONFLICT_FILES=$(git merge-tree --write-tree --name-only origin/${BASE_REF} ${PINNED_HEAD_SHA} 2>/dev/null \
+                     | tail -n +2 | sed '/^$/d' | grep '/' )
+  fi
+fi
+```
+
+Record the result in `metadata.json` under a `mergeability` key:
+
+```json
+{
+  "mergeability": {
+    "mergeable": "CONFLICTING | MERGEABLE | UNKNOWN",
+    "merge_state_status": "DIRTY | CLEAN | BLOCKED | BEHIND | ...",
+    "base_ref": "main",
+    "commits_behind_base": 101,
+    "commits_ahead_base": 91,
+    "conflicting_files": ["apps/.../App.tsx", "..."]
+  }
+}
+```
+
+**How to use the result:**
+
+- `MERGEABLE` ∈ {`CONFLICTING`} OR `MERGE_STATE` = `DIRTY` → the PR has conflicts. Surface a **⚠️ Mergeability** block in the Phase 5 intermediate report AND the Phase 8 final report, listing `commits_behind_base` and the `conflicting_files`. In **external / comment-only** mode, include the same block in the Phase 6b comment. State plainly that the branch needs a rebase/merge from `{BASE}` and that **the reviewed diff may be stale** with respect to current `{BASE}`.
+- `MERGE_STATE` = `BEHIND` (mergeable but behind) → note the drift (`commits_behind_base`) as a softer advisory; no conflict, but the diff predates recent `{BASE}` commits.
+- `MERGEABLE` = `UNKNOWN` (GitHub hasn't finished computing, common right after a push) → record `UNKNOWN`; optionally re-poll once after a few seconds. Do not block.
+- `MERGEABLE` = `MERGEABLE`, `MERGE_STATE` = `CLEAN` → record it and move on silently.
+
+This step never changes the review's findings or assessment — a conflicting PR with zero code findings is still `approve` on its own merits. Mergeability is reported as a **separate** signal so the reader knows whether the approval can actually land.
+
 ### Step 5: Read All Changed Files
 
 For every file in the changed file list, read it in full using the Read tool **from the worktree**:
@@ -1058,6 +1108,10 @@ Review Synthesis (Before Auto-Fix)
 Auto-Checks: {PASS/FAIL}
   lint: {P/F} | typecheck: {P/F} | tests: {P/F}
 
+Mergeability (PR reviews — from Step 4c): {MERGEABLE/CONFLICTING/UNKNOWN}
+  {if CONFLICTING/DIRTY: "⚠️ conflicts with {BASE} — {behind} commits behind — needs rebase — reviewed diff may be stale"}
+  {if conflicting_files: list them}
+
 Validated Findings:
   CRITICAL: {N}
   HIGH: {N}
@@ -1630,6 +1684,7 @@ Output the human-readable summary:
 
   Review ID: {REVIEW_ID}
   Assessment: {APPROVE / REQUEST CHANGES / COMMENT}
+  Mergeability: {MERGEABLE / CONFLICTING (N behind {BASE}, needs rebase) / UNKNOWN}   # PR reviews — from Step 4c / metadata.json.mergeability
 
   Scores:
     Security:      {score}/10

package/dist/plugin/skills/apt-setup/SKILL.md

@@ -205,6 +205,7 @@ AskUserQuestion([
 - "Visibility" → jump to **Step 3e** (Batch 6 only), then skip to **Step 4** and **Step 5**
 - "Task Tracking" → jump to **Step 3g** (Batch 8 only), then skip to **Step 4** and **Step 5**
 - "Changelog & Release Notes" → jump to **Step 3h** (Batch 9 only), then skip to **Step 4** and **Step 5**
+- "Collaboration" → jump to **Step 3i** (Batch 10 only), then skip to **Step 4** and **Step 5**
 - "Everything" → proceed to **Step 2** and run all batches (same as fresh setup). **Legacy-completes-Everything marker write:** if the starting config has no `onboarding` block (legacy unmarked config) and the user completes the full flow, write a full `onboarding` block at Step 5 as `{ completed: true, seeded_from_template: false, seeded_at: <ISO-8601 now> }` to record the explicit onboarding pass.
 - "Done" → display "Settings unchanged." and exit
 
@@ -1180,6 +1181,74 @@ The selective-edit pass through Batch 9 MUST respect the §1b dispatch — it do
 
 ---
 
+## 3i. Present Settings (Batch 10: Collaboration Catch-Up)
+
+The **collaboration catch-up** surfaces show on every interactive (TTY) `/apt`
+call: a **Welcome-Back Summary** (your most-recently-active task + next step,
+always-on, local-only) and a **Team-Change Digest** (the PRs teammates merged
+to main since you last pulled — gated to `share.visibility` `team`/`oss`).
+Written to `.aperant/config.json.collaboration`.
+
+```
+AskUserQuestion([
+  {
+    question: "Show the Welcome-Back Summary when you return after a break?",
+    header: "Welcome-Back",
+    multiSelect: false,
+    options: [
+      { label: "Yes (Recommended)", description: "On your next /apt after the staleness window, surface where you left off — task, phase, next step. Local only." },
+      { label: "No", description: "Never show the welcome-back nudge." }
+    ]
+  },
+  {
+    question: "How many hours away before the Welcome-Back Summary fires?",
+    header: "Threshold (hours)",
+    multiSelect: false,
+    options: [
+      { label: "16 (Recommended)", description: "Roughly 'since yesterday' — fires after an overnight gap." },
+      { label: "8", description: "Fires after a long lunch / half-day gap." },
+      { label: "24", description: "Once-a-day cadence." }
+    ]
+  },
+  {
+    question: "Show the Team-Change Digest (teammates' merged PRs since your last pull)?",
+    header: "Team Digest",
+    multiSelect: false,
+    options: [
+      { label: "Yes (Recommended)", description: "Only computes when share.visibility is team/oss; reads local git history, never fetches." },
+      { label: "No", description: "Never show the digest, even in team/oss mode." }
+    ]
+  },
+  {
+    question: "Maximum PRs to list in the digest before '+N more on main'?",
+    header: "Digest Max Entries",
+    multiSelect: false,
+    options: [
+      { label: "7 (Recommended)", description: "Low-noise ceiling; the rest collapse into a '+N more' tail." },
+      { label: "5", description: "Tighter." },
+      { label: "12", description: "Roomier." }
+    ]
+  }
+])
+```
+
+For hosts without structured prompts, present the same four questions as
+numbered lists (Batch 5 style) and read single-index responses.
+
+### 3i.1 Review-Mode routing entry
+
+The "1b. Review Mode" routing table (§1b) includes "Collaboration" as a
+selectable edit target — jumping directly back into this Batch 10 picker.
+
+### 3i.2 Confirmation row
+
+Add a row to the Step 8 table:
+```
+| Collaboration | welcome-back {on/off} ({N}h) · team-digest {on/off} (max {M}) |
+```
+
+---
+
 ## 4. Map Answers to Config
 
 **AUDIT-001 — file-routing contract for per-device fields (UPDATED 0.8.1 for FRAMEWORK-RFC-001):** the
@@ -1295,6 +1364,12 @@ Note: task ids are slug-first since v0.6.6 — the date-format setting controls
 - "Sub-Agents" → `"sub-agents"`
 - "Sequential" → `"sequential"`
 
+**Collaboration Catch-Up (Batch 10):**
+- Welcome-Back "Yes" → `collaboration.welcome_back.enabled: true`, "No" → `false`
+- Threshold → `collaboration.welcome_back.threshold_hours: <8|16|24>`
+- Team Digest "Yes" → `collaboration.team_digest.enabled: true`, "No" → `false`
+- Digest Max Entries → `collaboration.team_digest.max_entries: <5|7|12>`
+
 ## 5. Write Config
 
 Write merged config to two files per AUDIT-001 routing (see Step 4 block):
@@ -1402,6 +1477,7 @@ Display:
 | Debate Mode          | {Auto / Agent Team / Sub-Agents / Sequential} |
 | Visibility           | {solo / team / oss} (overrides if any)        |
 | Changelog & Release Notes | dev: {Yes/No}; release-notes: {Yes/No} (audience, persona-filter) |
+| Collaboration        | welcome-back {on/off} ({N}h) · team-digest {on/off} (max {M}) |
 | Saved as Defaults    | {Yes/No}                     |
 
 Config saved to: .aperant/config.json

package/dist/plugin/skills/apt-verify/SKILL.md

@@ -60,7 +60,7 @@ Before spawning any verifier subagent or running scoring against acceptance crit
 </locked_decisions>
 ```
 
-Verifiers apply this digest when interpreting "completeness" and "correctness" — if a decision explicitly deferred a behavior, its absence is NOT a verification failure.
+Verifiers apply this digest when interpreting "completeness" and "correctness" — if a decision explicitly deferred a behavior AND the deferred finding has severity below critical or major, its absence is NOT a verification failure. A deferred critical or major finding IS a Completeness gap — score accordingly and note it in the issues list.
 </decision_ledger_inject>
 
 <process>

package/dist/plugin/skills/apt-verify-proof/SKILL.md

@@ -20,6 +20,7 @@ gates: []
 config_keys:
   - verification.open_report
   - verification.report_formats
+  - verification.provision_mcp
 ---
 
 # Proof Verification
@@ -104,13 +105,36 @@ disable the walk entirely (root-only behaviour, backwards compat).
 The `verification.runtimes[]` override stays the final escape hatch
 and is now usually unnecessary because the walk runs by default.
 
-### Bundled drivers (4)
+### Bundled drivers (5)
 
 - **browser** (priority=100, ga) — Next.js / vanilla web frontends.
 - **electron** (priority=90, ga) — Electron desktop apps.
+- **tauri** (priority=85, ga) — Tauri desktop apps.
 - **cli** (priority=60, ga) — headless CI, output-shape assertions.
 - **api** (priority=50, ga) — HTTP / JSON-API regression tests.
 
+### Install-time MCP provisioning (verification.provision_mcp)
+
+`apt-tools init` (and `/apt:update`, which routes through the same path)
+auto-provisions the MCP transport a driver needs into each SELECTED host
+CLI's config, so verify-proof works at the prompt with no manual MCP
+setup. It detects the project runtime and, per host:
+
+- **claude** → JSON-merges the server into the project-root `.mcp.json`
+  (`mcpServers.<id>`).
+- **codex** → upserts a `[mcp_servers.<id>]` table into the project-root
+  `.codex/config.toml`.
+
+Electron and Tauri projects get the matching MCP server; web frontends
+get the browser driver's declared `agent-browser` skill copied into the
+host skill dir (`.claude/skills/` / `.agents/skills/`) — its `agent-browser`
+CLI is a documented one-time prereq, the same class as the
+`electron-mcp-server` / `tauri-plugin-mcp-server` npm packages (see each
+driver's README). All writes are **TOFU/non-clobbering**: a pre-existing
+server id, config table, or skill file is never overwritten. Opt out with
+`verification.provision_mcp: false` (default `true`) — then init/update
+writes no host MCP config and no skill.
+
 ### Driver authors
 
 Third-party driver authors should run `apt-tools driver doctor .` before