@ainova-systems/intelligence 0.11.0-rc.7 → 0.11.0-rc.8

package/engine/adapters/_template.sh

@@ -1,22 +1,21 @@
 #!/bin/bash
-# intelligence-sync: Adapter template
-# Copy this file to create a new IDE adapter.
+# Intelligence CLI: project adapter template
+# Scaffold this file with: intelligence adapter create <name>
 #
 # This file is NOT executable as-is — `<name>` placeholders below would be
 # parsed by bash as input redirection (`<` operator). Replace every
 # occurrence with your adapter name before sourcing.
 #
 # Required:
-#   1. Name the file: <ide-name>.sh (e.g., myide.sh)
-#   2. Replace every `<name>` placeholder with your adapter name
-#   3. Implement sync_to_<name>() function
-#   4. Add target to config.yaml:
+#   1. Implement sync_to_<name>() and its three content transforms
+#   2. Enable it after implementation: intelligence adapter enable <name>
+#      This adds the target to intelligence.yaml when it is absent:
 #      targets:
 #        <name>: { enabled: true, output: ".<name>" }
 #
 # The sync_to_<name>() function receives:
 #   $1 = repo_root     — absolute path to the project root
-#   $2 = config_file   — absolute path to config.yaml
+#   $2 = config_file   — absolute path to intelligence.yaml
 #   $3 = output_dir    — absolute path to the output directory (e.g., .myide/)
 #
 # Available library functions (from lib/common.sh):
@@ -29,10 +28,12 @@
 #   get_model_default(ide, tier)        — hardcoded default for ide:tier
 #   map_access_to_claude_tools(access)  — full->"" (no tools list; inherits all), readonly->restricted
 #   map_access_to_claude_disallowed(access) — readonly->"Write, Edit", full->""
-#   read_yaml_list(config, section)     — read list from config.yaml
+#   read_yaml_list(manifest, section)   — read a source list from intelligence.yaml
 #   get_target_field(config, target, field) — read a target's config field
 
-source "$(dirname "${BASH_SOURCE[0]}")/../lib/common.sh"
+# Project adapters are sourced by engine/sync.sh after the shared library is
+# loaded. Keep this template position-independent: after scaffolding it lives
+# under the project's content directory, not beside engine/lib/.
 
 # Sync rules for <agent-name>
 # Typical transformations:

package/engine/adapters/agents.sh

@@ -21,8 +21,8 @@ source "$(dirname "${BASH_SOURCE[0]}")/../lib/common.sh"
 # one document Cursor, Copilot and Codex all read as canonical.
 # The defaults only cover an adapter driven directly (tests); sync.sh always
 # exports both.
-agents_md_umbrella_rel() {
-    printf '%s' "${IS_UMBRELLA_REL:-intelligence}"
+agents_md_content_rel() {
+    printf '%s' "${IS_CONTENT_REL:-intelligence}"
 }
 
 agents_md_module_rel() {
@@ -196,14 +196,14 @@ agents_md_append_rules_list() {
     # Path-scoped rules stay in tool-specific channels (.cursor/rules/,
     # .github/instructions/) so monorepo scoping is preserved.
     if [ "${#global_rule_files[@]}" -gt 0 ]; then
-        local umbrella_rel
-        umbrella_rel="$(agents_md_umbrella_rel "$repo_root")"
+        local content_rel
+        content_rel="$(agents_md_content_rel "$repo_root")"
         {
             echo "---"
             echo ""
             echo "## Project Context"
             echo ""
-            echo "<!-- Inlined from always-on rules in $umbrella_rel/rules/ -->"
+            echo "<!-- Inlined from always-on rules in $content_rel/rules/ -->"
             echo ""
         } >> "$output"
         local rf
@@ -240,17 +240,17 @@ sync_to_agents() {
 
     mkdir -p "$(dirname "$output_file")"
 
-    local umbrella_rel module_rel
-    umbrella_rel="$(agents_md_umbrella_rel "$repo_root")"
+    local content_rel module_rel
+    content_rel="$(agents_md_content_rel "$repo_root")"
     module_rel="$(agents_md_module_rel "$repo_root")"
 
     # These two strings are written into a COMMITTED file. An absolute path here
     # means the derivation failed, and a machine-specific path in AGENTS.md is
     # worse than a failed sync — fail loudly instead.
-    case "$umbrella_rel$module_rel" in
+    case "$content_rel$module_rel" in
         /*|*:[\\/]*)
             echo "  ERROR: AGENTS.md paths did not resolve relative to the repo root:" >&2
-            echo "         umbrella='$umbrella_rel' module='$module_rel' repo_root='$repo_root'" >&2
+            echo "         content='$content_rel' module='$module_rel' repo_root='$repo_root'" >&2
             return 1
             ;;
     esac
@@ -261,7 +261,7 @@ sync_to_agents() {
 
     {
         echo "<!-- Generated by intelligence-sync. Do not edit manually. -->"
-        echo "<!-- Source: $umbrella_rel/ | Sync: $sync_cmd -->"
+        echo "<!-- Source: $content_rel/ | Sync: $sync_cmd -->"
         echo ""
     } > "$output_file"
 
@@ -270,7 +270,7 @@ sync_to_agents() {
     {
         echo "## Intelligence"
         echo ""
-        echo "Source of truth: \`$umbrella_rel/\` | Sync: \`$sync_cmd\`"
+        echo "Source of truth: \`$content_rel/\` | Sync: \`$sync_cmd\`"
         echo ""
     } >> "$output_file"
 

package/engine/adapters/opencode.sh

@@ -29,7 +29,7 @@ source "$(dirname "${BASH_SOURCE[0]}")/../lib/common.sh"
 # Strip frontmatter, return body only.
 # Direct call to the shared `strip_frontmatter` helper in lib/common.sh —
 # duplicating the awk block here would violate the "all parsing in common.sh"
-# convention (see CLAUDE.md / docs/CONVENTIONS.md).
+# convention (see CLAUDE.md / packages/sync/references/conventions.md).
 
 sync_opencode_skills() {
     local repo_root="$1"

package/engine/lib/common.sh

@@ -16,16 +16,14 @@ normalize_file_to_lf() {
 
 # --- Layout tokens -----------------------------------------------------------
 #
-# The umbrella folder is named by the project (`intelligence/`, `Intelligence/`,
-# a codename) — so an artifact SHIPPED BY THE ENGINE cannot write that name
-# down. A rule that scopes itself to the intelligence layer needs `paths:` to
-# say "the umbrella", and an agent body needs to name the sync command. Both are
-# spelled with tokens, expanded here at output time:
+# The content directory is named by the project (`intelligence/`,
+# `Intelligence/`, a codename), so package-shipped artifacts cannot hardcode
+# it. Layout-sensitive paths and commands use tokens expanded at output time:
 #
-#   <umbrella>  ->  the repo-relative umbrella dir   (e.g. `Intelligence`)
-#   <module>    ->  the repo-relative engine module  (e.g. `Intelligence/sync`)
+#   <content-dir> -> the repo-relative project content dir (e.g. `Intelligence`)
+#   <module>      -> the repo-relative sync package store path
 #
-# Values come from IS_UMBRELLA_REL / IS_MODULE_REL, which sync.sh derives from
+# Values come from IS_CONTENT_REL / IS_MODULE_REL, which the CLI derives from
 # the detected layout (never hardcoded) and exports before any adapter runs.
 # Expansion happens in EVERY generated file, frontmatter and body alike, so a
 # scoped rule reaches Claude's `paths:`, Cursor's `globs:` and Copilot's
@@ -34,24 +32,18 @@ normalize_file_to_lf() {
 # finalize_output_file <file>
 # The single exit gate for every file an adapter writes: expand layout tokens,
 # then normalize CRLF -> LF. Adapters MUST call this (not normalize_file_to_lf)
-# on each output — a missed call ships a literal `<umbrella>` into an IDE.
+# on each output — a missed call ships a literal `<content-dir>` into an IDE.
 finalize_output_file() {
     local target="$1"
-    local umb="${IS_UMBRELLA_REL:-intelligence}"
-    local mod="${IS_MODULE_REL:-intelligence/sync}"
-    # `<sync-cmd>` is how engine content says "run a sync": vendored setups
-    # expand it to the script invocation (built from $mod, so it reproduces the
-    # exact pre-token string), the CLI overrides it via IS_SYNC_CMD
-    # (`intelligence sync`). `<manifest>` names the project's config file the
-    # same way: `config.yaml` vendored, `intelligence.yaml` under the CLI
-    # (IS_MANIFEST_NAME).
-    local sc="${IS_SYNC_CMD:-bash $mod/scripts/sync.sh}"
-    local mf="${IS_MANIFEST_NAME:-config.yaml}"
+    local content="${IS_CONTENT_REL:-intelligence}"
+    local mod="${IS_MODULE_REL:-.intelligence/packages/@ainova-systems/sync}"
+    local sc="${IS_SYNC_CMD:-intelligence sync}"
+    local mf="${IS_MANIFEST_NAME:-intelligence.yaml}"
     local tmp_file="$target.tmp"
     # Literal (index-based) substitution, not gsub: a regex replacement would
     # give `&` in a path its special meaning, and POSIX awk has no way to pass a
     # replacement string verbatim.
-    awk -v umb="$umb" -v mod="$mod" -v sc="$sc" -v mf="$mf" '
+    awk -v content="$content" -v mod="$mod" -v sc="$sc" -v mf="$mf" '
         function repl(s, from, to,   out, i) {
             out = ""
             while ((i = index(s, from)) > 0) {
@@ -65,7 +57,7 @@ finalize_output_file() {
             $0 = repl($0, "<sync-cmd>", sc)
             $0 = repl($0, "<manifest>", mf)
             $0 = repl($0, "<module>", mod)
-            $0 = repl($0, "<umbrella>", umb)
+            $0 = repl($0, "<content-dir>", content)
             print
         }
     ' "$target" > "$tmp_file"
@@ -798,7 +790,7 @@ warn_unsynced() {
     # from its location — it comes from the env contract the CLI exports.
     local intel_basename
     if [ "${IS_CLI:-0}" = "1" ]; then
-        intel_basename="$(basename "${IS_UMBRELLA_REL:-intelligence}")"
+        intel_basename="$(basename "${IS_CONTENT_REL:-intelligence}")"
     else
         intel_basename="$(basename "$(dirname "$config_file")")"
     fi

package/engine/lib/contract.sh

@@ -1,16 +1,16 @@
 #!/bin/bash
-# shellcheck disable=SC2034  # IS_RC_*/IS_VERSION_KEY are the public bash<->CLI contract, consumed by the scripts that source this lib
+# shellcheck disable=SC2034  # IS_RC_*/IS_SCHEMA_VERSION_KEY are the public bash<->CLI contract, consumed by the scripts that source this lib
 # intelligence-sync: the version and status contract.
 # Source this file — never execute directly.
 #
 # Two things live here, and both are contracts other programs depend on:
-#   * the applied-schema stamp (`sync_version` in the manifest) with its
+#   * the applied-schema stamp (`schema_version` in the manifest) with its
 #     read / write / compare helpers, and
 #   * the IS_STATUS / IS_RC_* codes every engine flow reports.
 #
-# Schema migrations themselves are NOT here: the CLI owns them (v2 migrations
-# live in `intelligence upgrade`), and a v1 project is brought forward by the
-# archived v1 engine before `intelligence migrate` converts it.
+# Schema migrations themselves are NOT here: the CLI owns them behind
+# `intelligence init`, and a v1 project is brought forward by the archived v1
+# engine before `intelligence init` converts it.
 
 # The applied-schema version is a managed key in the manifest.
 #
@@ -18,13 +18,13 @@
 # Anything else in the manifest may be reshaped; the name, location and shape of
 # this key never are - so any engine, however old or new, can always read "what
 # schema is this?" before parsing the rest.
-IS_VERSION_KEY="sync_version"
+IS_SCHEMA_VERSION_KEY="schema_version"
 
-# read_engine_stamp <config_file> → applied version, or "" if absent.
-read_engine_stamp() {
+# read_schema_version <config_file> → applied version, or "" if absent.
+read_schema_version() {
     local cf="$1"
     [ -f "$cf" ] || return 0
-    awk -v k="$IS_VERSION_KEY" '
+    awk -v k="$IS_SCHEMA_VERSION_KEY" '
         { sub(/\r$/, "") }
         $0 ~ "^" k ":" {
             v = $0; sub(/^[^:]*:[[:space:]]*/, "", v)
@@ -35,14 +35,14 @@ read_engine_stamp() {
     ' "$cf"
 }
 
-# stamp_version <config_file> <version> — idempotent, transactional upsert of
+# stamp_schema_version <config_file> <version> — idempotent, transactional upsert of
 # the contract key (replace in place if present, else append at top level).
 # No-op if config.yaml does not exist yet (pre-bootstrap).
-stamp_version() {
+stamp_schema_version() {
     local cf="$1" ver="$2"
     [ -f "$cf" ] || return 0
     local tmp="$cf.ver.tmp"
-    awk -v k="$IS_VERSION_KEY" -v val="$ver" '
+    awk -v k="$IS_SCHEMA_VERSION_KEY" -v val="$ver" '
         { sub(/\r$/, "") }
         $0 ~ "^" k ":" { print k ": \"" val "\""; found=1; next }
         { print }
@@ -62,7 +62,7 @@ IS_RC_CONFIG_MISSING=2      # no manifest found
 IS_RC_AMBIGUOUS=3           # conflicting state; agent/human-only — bash never emits this itself
 IS_RC_AHEAD=4               # project stamped newer than this engine understands
 IS_RC_ABORTED_INCOMPLETE=5  # staged state incomplete; the project was left untouched
-IS_RC_NEEDS_UPDATE=6        # pending schema changes (stamp < engine) — run `intelligence upgrade` first
+IS_RC_NEEDS_UPDATE=6        # pending schema changes (stamp < engine) — run `intelligence init --apply`
 
 # is_status <code-name> [detail] — emit one parseable line for the skill.
 is_status() {
@@ -106,7 +106,7 @@ _ver_gt() {
 # conflict, else 0.
 check_version_compat() {
     local cf="$1" stamp eng
-    stamp="$(read_engine_stamp "$cf")"
+    stamp="$(read_schema_version "$cf")"
     [ -n "$stamp" ] || return 0
     eng="$(engine_version)"
     [ -n "$eng" ] || return 0

package/engine/sync.sh

@@ -7,7 +7,7 @@
 #
 #   CONFIG_FILE        the project's manifest (intelligence.yaml at the root)
 #   REPO_ROOT          the project root
-#   IS_UMBRELLA_REL    the project's content dir, repo-relative
+#   IS_CONTENT_REL     the project's content dir, repo-relative
 #   IS_MODULE_REL      the installed sync package, repo-relative
 #   IS_PROTECTED_DIRS  dirs an adapter output may never overlap
 #
@@ -35,21 +35,21 @@ _vc_rc=0
 check_version_compat "$_cf" || _vc_rc=$?
 if [ "$_vc_rc" -ne 0 ]; then exit "$_vc_rc"; fi
 
-# Schema gap → refuse. sync is a PURE synchronizer: it never migrates, so a
-# project behind this engine must be brought forward by `intelligence upgrade`
-# first. An ABSENT stamp means the same thing — a manifest with no
-# `sync_version` must not silently sync past a schema change.
-_stamp="$(read_engine_stamp "$_cf")"
+# Schema gap → refuse. sync is a PURE synchronizer: it never changes schemas,
+# so the CLI lifecycle preflight must align the project first. An ABSENT stamp
+# means the same thing — a manifest with no
+# `schema_version` must not silently sync past a schema change.
+_stamp="$(read_schema_version "$_cf")"
 _eng="$(engine_version)"
 if [ -z "$_stamp" ]; then
-    is_status needs-update "stamped= engine=$_eng (no sync_version)"
-    echo "ERROR: the manifest has no sync_version — schema un-applied." >&2
-    echo "       Run: intelligence upgrade" >&2
+    is_status needs-update "stamped= engine=$_eng (no schema_version)"
+    echo "ERROR: the manifest has no schema_version — schema un-applied." >&2
+    echo "       Run: intelligence init --apply" >&2
     exit "$IS_RC_NEEDS_UPDATE"
 elif [ -n "$_eng" ] && _ver_gt "$_eng" "$_stamp"; then
     is_status needs-update "stamped=$_stamp engine=$_eng"
     echo "ERROR: project at $_stamp but engine is $_eng — pending schema changes." >&2
-    echo "       Run: intelligence upgrade" >&2
+    echo "       Run: intelligence init --apply" >&2
     exit "$IS_RC_NEEDS_UPDATE"
 fi
 
@@ -64,19 +64,19 @@ CONFIG_FILE="$(cd "$(dirname "$CONFIG_FILE")" && pwd)/$(basename "$CONFIG_FILE")
 
 # Layout tokens for generated output (see finalize_output_file in common.sh).
 # Package-shipped rules/agents cannot hardcode the content dir's name — the
-# project chooses it — so they write `<umbrella>` / `<module>` and every adapter
+# project chooses it — so they write `<content-dir>` / `<module>` and every adapter
 # expands them on the way out.
-IS_UMBRELLA_REL="${IS_UMBRELLA_REL:-intelligence}"
+IS_CONTENT_REL="${IS_CONTENT_REL:-intelligence}"
 # No vendor default: the CLI always exports the package path (derived from its
 # distribution data), so a bare invocation must say so rather than guess.
 if [ -z "${IS_MODULE_REL:-}" ]; then
     echo "ERROR: the engine needs IS_MODULE_REL (exported by the intelligence CLI)." >&2
     exit 1
 fi
-export IS_UMBRELLA_REL IS_MODULE_REL
+export IS_CONTENT_REL IS_MODULE_REL
 
-# Project-owned adapters live in the content dir: <umbrella>/adapters/.
-INTELLIGENCE_DIR="$REPO_ROOT/$IS_UMBRELLA_REL"
+# Project-owned adapters live in the content dir: <content-dir>/adapters/.
+INTELLIGENCE_DIR="$REPO_ROOT/$IS_CONTENT_REL"
 
 TARGET_FILTER="${1:-}"
 
@@ -132,8 +132,8 @@ done
 # Adapters come from two places, discovered by filename (minus `.sh`,
 # `_template` excluded):
 #
-#   1. Built-in   — shipped inside the CLI, replaced wholesale on every upgrade
-#   2. Project    — <umbrella>/adapters/, owned by the project and never touched
+#   1. Built-in   — shipped inside the CLI, replaced with each CLI installation
+#   2. Project    — <content-dir>/adapters/, owned by the project and never touched
 #
 # A custom adapter therefore belongs in the content dir's `adapters/`; the
 # built-in directory lives inside the installed CLI and is not the project's to
@@ -183,7 +183,12 @@ while [ "$adapter_idx" -lt "$adapter_count" ]; do
 
     # Check if target is enabled in config
     enabled=$(is_target_enabled "$CONFIG_FILE" "$adapter")
-    if [ "$enabled" != "1" ] && [ -z "$TARGET_FILTER" ]; then
+    if [ "$enabled" != "1" ]; then
+        if [ -n "$TARGET_FILTER" ]; then
+            echo "ERROR: Adapter '$TARGET_FILTER' is disabled in $CONFIG_FILE." >&2
+            echo "       Enable it first: intelligence adapter enable $TARGET_FILTER" >&2
+            exit 1
+        fi
         continue
     fi
 
@@ -227,7 +232,7 @@ warn_unsynced "$REPO_ROOT" "$CONFIG_FILE"
 report_model_drift "$CONFIG_FILE"
 
 echo ""
-# sync.sh never migrates (`intelligence upgrade` owns that), so success is
-# always ok.
+# sync.sh never changes project schemas (the CLI preflight owns that), so
+# success is always ok.
 is_status ok "synced=$synced"
 echo "=== Done: $synced target(s) synced ==="

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ainova-systems/intelligence",
-  "version": "0.11.0-rc.7",
+  "version": "0.11.0-rc.8",
   "description": "Build, version and distribute AI agent intelligence across your organization — one CLI, versioned Intelligence Packages, and a sync engine for Claude Code, Cursor, Copilot, Codex, Pi and OpenCode.",
   "bin": {
     "intelligence": "bin/intelligence.js"

package/packages/sync/agents/intelligence-architect.md

@@ -9,12 +9,13 @@ skills:
   - intelligence-add-skill
   - intelligence-extract-skill
   - intelligence-review-skills
+  - intelligence-learn-from-repository
   - intelligence-learn-from-context
 ---
 
 # Intelligence architect
 
-Owns `<umbrella>/` itself: what the layer is made of, and what it is allowed to grow into. Not the project's code — the instructions that shape how everyone else writes it.
+Owns `<content-dir>/` itself: what the layer is made of, and what it is allowed to grow into. Not the project's code — the instructions that shape how everyone else writes it.
 
 ## Expertise
 
@@ -45,9 +46,10 @@ The per-artifact checks are procedure, so they live in the meta-skills rather th
 | `intelligence-add-rule` / `intelligence-add-agent` / `intelligence-add-skill` | author one artifact |
 | `intelligence-extract-skill` | turn an observed workflow into a skill |
 | `intelligence-review-skills` | audit the layer for duplication, drift, size, hardcoded paths |
+| `intelligence-learn-from-repository` | propose the initial project-owned layer from repository evidence |
 | `intelligence-learn-from-context` | fold a session's lessons back into the layer |
 | `intelligence-sync` | project the source to every tool channel |
-| `intelligence-update` | update or migrate the engine |
-| `intelligence-install-adapter` / `intelligence-uninstall-adapter` | turn a tool channel on or off |
+| `intelligence-update` | interpret and apply the CLI's unified update plan |
+| `intelligence-install-adapter` / `intelligence-uninstall-adapter` | research and manage a tool adapter |
 
 A change is done when the sync is green and the skill you invoked reports clean. Size is a separate judgement: the caps are ceilings, not quotas, and a short artifact is not a defect.

package/packages/sync/agents/intelligence-operator.md

@@ -1,6 +1,6 @@
 ---
 name: intelligence-operator
-description: "Run the engine's mechanical flows - sync, update, adapter install and removal"
+description: "Interpret CLI plans and operate sync, update, and adapter flows"
 tier: standard
 access: full
 skills:
@@ -12,20 +12,17 @@ skills:
 
 # Intelligence operator
 
-Operates the engine: projects the source tree to every enabled tool channel, updates or migrates the
-engine, turns tool channels on and off. What the layer contains - which rules, agents and skills
+Operates the CLI: projects the source tree to every enabled tool channel, interprets and applies update
+plans, and manages adapters. What the layer contains - which rules, agents and skills
 exist and what they say - is `intelligence-architect`'s judgement; this agent runs the machinery
 that ships it.
 
 ## Expertise
 
-The status contract (`<module>/docs/CONVENTIONS.md`, Migration & Module Contract). Every flow
-here is deterministic and fail-closed: the sync is a pure synchronizer that refuses across an
-un-applied schema, the update flow stages, verifies and only then commits, and every flow
-reports `IS_STATUS`. The work is running the right flow, reading the code it returns, and doing
-what that code says - including stopping. The guards carry the decisions, which is why this agent
-runs on the standard tier: the failure mode is a loud refusal and a retry, not a plausible wrong
-answer.
+The CLI and engine status contract. Mechanical flows are deterministic and
+fail-closed; the agent reads their result, selects the next supported command,
+checks changelog post-conditions, and stops on a refusal instead of recreating
+the operation in prose.
 
 ## Boundaries
 
@@ -35,7 +32,7 @@ answer.
 - **Operating is not authoring.** A change to what an artifact says - a rule body, an agent persona,
   a skill's steps - belongs to `intelligence-architect` and the authoring meta-skills. This agent
   ships what exists and never decides what should exist.
-- **A state the engine refuses to resolve goes to a human.** `ambiguous` and every other non-ok
+- **A state the CLI refuses to resolve goes to a human.** `ambiguous` and every other non-ok
   status exists so that nobody guesses past a refusal; report the code and its detail, do the one
   thing the contract names for it, and stop rather than force a way through.
 
@@ -45,5 +42,5 @@ answer.
 <sync-cmd>          # expect IS_STATUS=ok
 ```
 
-Done is the invoked skill reporting its own success criteria met: `IS_STATUS=ok` (`migrated` counts,
-for an update), per-target counts matching the sources, and no warning left unhandled.
+Done is the invoked skill reporting its own success criteria met: `IS_STATUS=ok`,
+per-target counts matching the sources, and no warning left unhandled.