@theronap/cortex-mcp 0.9.96 → 0.9.98

package/lib/editors/claude.mjs

@@ -46,13 +46,19 @@ export const allowedToolsFor = (namespace) => ALLOWED_TOOL_NAMES.map((t) => `mcp
 
 export const CORTEX_ALLOWED_TOOLS = allowedToolsFor('cortex')
 
+/** C1 (ADR-0033 §5). Every seat is pre-authorized for BOTH tool namespaces, because a machine that
+ *  has not yet flipped its config key still calls mcp__cortex__*, and one that has calls
+ *  mcp__agnoclast__*. Additive and permanent for the duration of the migration: the old rules are
+ *  never removed, so a machine can carry both and neither ordering can strand it at a prompt. */
+export const MANAGED_ALLOWED_TOOLS = [...allowedToolsFor('cortex'), ...allowedToolsFor('agnoclast')]
+
 /** Merge Agnoclast's Claude Code hooks into a ~/.claude/settings.json object. Pure + idempotent: drops
  *  any prior cortex entry (old token/path/version) from each hook array before appending the current
  *  one — capture (Stop), status + skills-repair + snapshot-context (SessionStart), hydrate
  *  (UserPromptSubmit). Also UNWIRES the retired PreCompact reminder from seats that still carry it.
  *  Commands carry NO inline token (each subcommand
  *  self-resolves it). Mirrors setup.mjs
- *  step 2 exactly; foreign hooks are never touched. Also merges the CORTEX_ALLOWED_TOOLS permission
+ *  step 2 exactly; foreign hooks are never touched. Also merges the MANAGED_ALLOWED_TOOLS permission
  *  allowlist — additive-only: a user's own allow entries (even extra mcp__cortex__* ones) are never
  *  removed, and `deny` is never touched (a user deny always beats our allow). */
 export function mergeClaudeSettings(existing, spec) {
@@ -142,7 +148,7 @@ export function mergeClaudeSettings(existing, spec) {
   // ship via uninstall, and rebuilding would delete allows the user added by hand.
   s.permissions = s.permissions && typeof s.permissions === 'object' ? s.permissions : {}
   s.permissions.allow = Array.isArray(s.permissions.allow) ? s.permissions.allow : []
-  for (const rule of CORTEX_ALLOWED_TOOLS) {
+  for (const rule of MANAGED_ALLOWED_TOOLS) {
     if (!s.permissions.allow.includes(rule)) s.permissions.allow.push(rule)
   }
 

package/lib/rename_notice.mjs

@@ -16,9 +16,9 @@ import { NEW_KEY, OLD_KEY } from './migrate_key.mjs'
 // OLD config key. Once `migrate-key` flips it, the condition is false and the message stops. That is
 // "warn, then leave them alone" expressed as a condition rather than as a timer.
 
-/** C1 sets this true. Until then the notice is inert, so building it now changes nothing for the
- *  people currently on @latest. Flipping this constant IS the C1 release. */
-export const RENAME_NOTICE_ACTIVE = false
+/** ACTIVATED 2026-08-19 — this flip is the C1 release. Delete this module, its test, and the two
+ *  lines that call it in doctor.mjs one release after C2 lands. */
+export const RENAME_NOTICE_ACTIVE = true
 
 /** PURE. The one-line warning, or null when it should stay quiet.
  *  `key` is which config key answered on this machine ('cortex' | 'agnoclast' | null). */

package/lib/skills.mjs

@@ -361,6 +361,35 @@ export async function runSkills(argv = []) {
   if (argv[0] === 'push') return runSkillsPush(argv.slice(1))
 
   const quiet = argv.includes('--quiet')
+
+  // ── C2 (ADR-0033 §5): move the MCP config key to its new name. ─────────────
+  // This runs from the SessionStart hook because that is the only channel that reaches every seat
+  // without asking anyone to do anything. It is safe here for two reasons that both matter:
+  //
+  //   • It is SELF-GUARDING. runKeyMigration adds the new namespace's allow rules and re-reads them
+  //     from disk BEFORE flipping the key, and aborts leaving the machine on the old name if they
+  //     did not land. The C1 release already pre-authorized both namespaces, so on a seat that took
+  //     C1 there is nothing left to add — but a seat that skipped C1 entirely is handled too, which
+  //     is the whole reason the guard lives on the machine rather than in the release cadence.
+  //   • It is idempotent and cheap after the first run: a state file read, then nothing.
+  //
+  // FAIL-SOFT, like every other hook step. A migration hiccup must never block a session from
+  // starting; the next SessionStart tries again.
+  try {
+    const { runKeyMigration } = await import('./migrate_key.mjs')
+    const res = runKeyMigration()
+    if (!quiet && res.status === 'migrated') {
+      process.stdout.write(`  ✓ MCP config key moved ${res.from} → ${res.to}. Restart to load it under the new name.\n`)
+    }
+    if (res.status === 'aborted') {
+      // Loud on stderr even when quiet: an abort means the machine is INTENTIONALLY still on the old
+      // key, and a silent abort is indistinguishable from never having tried.
+      process.stderr.write(`agnoclast: key migration held off at "${res.step}" (${res.reason}) — still on the old name, will retry.\n`)
+    }
+  } catch (e) {
+    process.stderr.write(`agnoclast: key migration skipped (${e?.message ?? e}) — will retry next session.\n`)
+  }
+
   if (!quiet) process.stdout.write('\nAgnoclast skills — installing managed skills…\n')
   const r = installSkills({ quiet })
   if (!quiet) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@theronap/cortex-mcp",
-  "version": "0.9.96",
+  "version": "0.9.98",
   "description": "Connect your AI assistant to Cortex — your org's projects, activity, gaps, and directives, scoped to you.",
   "type": "module",
   "bin": {