arkaos 4.3.2 → 4.3.4

package/core/sync/features/spec-gate.yaml

@@ -2,9 +2,10 @@ name: spec-driven-gate
 added_in: "2.13.0"
 mandatory: true
 section_title: "Spec-Driven Development"
-detection_pattern: "arka-spec"
+detection_pattern: "arka:feature:spec-driven-gate|## Spec-Driven Development|arka-spec"
 deprecated_in: null
 content: |
+  <!-- arka:feature:spec-driven-gate:start -->
   ## Spec-Driven Development
 
   Phase 0 of all workflows. No implementation begins without a validated spec.
@@ -13,3 +14,4 @@ content: |
   - Gate: spec must be approved before planning phase starts
   - Storage: `docs/superpowers/specs/YYYY-MM-DD-<topic>-design.md`
   - Review: user approval required on written spec
+  <!-- arka:feature:spec-driven-gate:end -->

package/core/sync/features/workflow-tiers.yaml

@@ -2,9 +2,10 @@ name: workflow-tiers
 added_in: "2.12.0"
 mandatory: true
 section_title: "Workflow Tiers"
-detection_pattern: "Enterprise.*phase|Focused.*phase|Specialist.*phase"
+detection_pattern: "arka:feature:workflow-tiers|## Workflow Tiers"
 deprecated_in: null
 content: |
+  <!-- arka:feature:workflow-tiers:start -->
   ## Workflow Tiers
 
   Three workflow tiers based on task complexity:
@@ -17,3 +18,4 @@ content: |
 
   Tier selection is automatic based on complexity assessment.
   Quality Gate phase is mandatory on ALL tiers.
+  <!-- arka:feature:workflow-tiers:end -->

package/departments/ops/skills/update/references/sync-engine.md

@@ -74,9 +74,11 @@ Returns JSON report for downstream consumption.
 ## Feature Registry
 
 YAML files under `core/sync/features/*.yaml` (or `~/.arkaos/config/sync/features/*.yaml`). Each feature has:
-- `detection_pattern` — regex/string searched in ecosystem SKILL.md to decide if the feature is already present
-- `content` — the section to inject if missing
-- `deprecated_in` — if set, the matching section is removed
+- `detection_pattern` — regex searched in ecosystem SKILL.md to decide if the feature is already present. Matches any of: the `arka:feature:<name>` marker, the bare `## <section_title>` heading (legacy/customized sections), or — only where a token is unique enough to never appear in unrelated prose (e.g. `arka-forge`) — a historical keyword
+- `content` — the section to inject if missing, wrapped in `<!-- arka:feature:<name>:start -->` / `<!-- arka:feature:<name>:end -->` markers so future runs detect it and deprecation can remove it precisely
+- `deprecated_in` — if set, the matching section is removed (marker pair preferred; fall back to the `## <section_title>` heading block)
+
+The registry is self-detecting by contract: `detection_pattern` MUST match the feature's own `content` (locked by `tests/python/test_sync_features_registry.py`), otherwise every naive sync re-injects a duplicate section.
 
 ## Key Paths
 

package/departments/ops/skills/update/references/workflows.md

@@ -47,10 +47,10 @@ After the Python engine completes, dispatch ONE subagent.
 **Subagent task — for each `~/.claude/skills/arka-{ecosystem}/SKILL.md`:**
 1. Read the SKILL.md.
 2. For each feature YAML where `deprecated_in` is null:
-   - Search SKILL.md for `detection_pattern`.
-   - If NOT found: inject `content` after the last existing feature section, or after the "Commands" table if no feature sections exist (before "Orchestration Workflows").
+   - Apply the `detection_pattern` regex to the SKILL.md text. It matches the `arka:feature:<name>` marker, the bare `## <section_title>` heading, or a unique historical keyword — a customized section without markers still counts as present and MUST NOT be duplicated.
+   - If NOT found: inject `content` (already marker-wrapped) after the last existing feature section, or after the "Commands" table if no feature sections exist (before "Orchestration Workflows").
 3. For each feature where `deprecated_in` is set:
-   - Locate and remove the matching section.
+   - Remove the `<!-- arka:feature:<name>:start -->` … `:end -->` block when markers exist; otherwise remove the `## <section_title>` section.
 4. PRESERVE all custom content: commands, architecture, tech stack, business descriptions, ecosystem-specific workflow details.
 
 ### Report

package/installer/hook-lib.js

@@ -0,0 +1,25 @@
+import { existsSync, cpSync, chmodSync, readdirSync, mkdirSync } from "node:fs";
+import { join } from "node:path";
+
+// Deploys config/hooks/_lib/ (shared hook libraries — the Python
+// interpreter resolver lives here) into an install's hooks directory.
+// Single implementation shared by the fresh-install path
+// (index.js::installHooks) and the update path (update.js): the v4.3.2
+// regression existed precisely because the two deploy loops drifted.
+// Returns true when the lib dir was copied, false when the source has
+// no _lib/ to deploy.
+export function copyHookLib(srcHooksDir, destHooksDir) {
+  const srcLibDir = join(srcHooksDir, "_lib");
+  if (!existsSync(srcLibDir)) return false;
+  const destLibDir = join(destHooksDir, "_lib");
+  mkdirSync(destLibDir, { recursive: true });
+  cpSync(srcLibDir, destLibDir, { recursive: true });
+  // chmod is a no-op on Windows (NTFS ACLs aren't POSIX); the try/catch
+  // keeps the copy result authoritative even if it throws.
+  try {
+    for (const f of readdirSync(destLibDir)) {
+      if (f.endsWith(".sh")) chmodSync(join(destLibDir, f), 0o755);
+    }
+  } catch {}
+  return true;
+}

package/installer/index.js

@@ -6,6 +6,7 @@ import { fileURLToPath } from "node:url";
 import { getRuntimeConfig } from "./detect-runtime.js";
 import { findSystemPython, ensureVenv, getArkaosPython, getArkaosPip, pipInstall } from "./python-resolver.js";
 import { IS_WINDOWS, HOOK_EXT } from "./platform.js";
+import { copyHookLib } from "./hook-lib.js";
 
 const __filename = fileURLToPath(import.meta.url);
 const __dirname = dirname(__filename);
@@ -665,16 +666,7 @@ function installHooks(installDir) {
     }
   }
 
-  const srcLibDir = join(srcHooksDir, "_lib");
-  if (existsSync(srcLibDir)) {
-    const destLibDir = join(hooksDir, "_lib");
-    ensureDir(destLibDir);
-    cpSync(srcLibDir, destLibDir, { recursive: true });
-    try {
-      for (const f of readdirSync(destLibDir)) {
-        if (f.endsWith(".sh")) chmodSync(join(destLibDir, f), 0o755);
-      }
-    } catch {}
+  if (copyHookLib(srcHooksDir, hooksDir)) {
     ok("Hook lib: _lib/");
   }
 }

package/installer/update.js

@@ -3,6 +3,7 @@ import { join, dirname, resolve } from "node:path";
 import { homedir } from "node:os";
 import { execSync } from "node:child_process";
 import { ensureVenv, ensureVenvHealthy, getArkaosPython, pipInstall } from "./python-resolver.js";
+import { copyHookLib } from "./hook-lib.js";
 import { getRuntimeConfig } from "./detect-runtime.js";
 import { loadAdapter } from "./index.js";
 import { migrateUserData, printMigrationReport } from "./migrate-user-data.js";
@@ -217,6 +218,14 @@ export async function update() {
   }
   console.log("         ✓ Hook scripts updated");
 
+  // Shared hook libraries (config/hooks/_lib/ — the Python interpreter
+  // resolver lives here). The hooks deployed above source
+  // _lib/arka_python.sh from the install dir, so skipping this copy
+  // leaves them falling back to a bare `python3` without ArkaOS deps.
+  if (copyHookLib(srcHooksDir, destHooksDir)) {
+    console.log("         ✓ Hook lib updated (_lib/)");
+  }
+
   // Re-register hooks in the runtime's settings file.
   // Without this, updating from an older version leaves settings.json
   // frozen at the previous hook spec (missing new hooks, stale timeouts).

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "arkaos",
-  "version": "4.3.2",
+  "version": "4.3.4",
   "description": "The Operating System for AI Agent Teams",
   "type": "module",
   "bin": {
@@ -45,7 +45,7 @@
     "departments/",
     "scripts/",
     "config/",
-    "bin/arkaos",
+    "bin/",
     "arka/",
     "knowledge/",
     "dashboard/app/",

package/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "arkaos-core"
-version = "4.3.2"
+version = "4.3.4"
 description = "Core engine for ArkaOS — The Operating System for AI Agent Teams"
 readme = "README.md"
 license = {text = "MIT"}