fix: update issues after review

Author: ivklgn

.archcore/update/keeping-the-cli-current.prd.md

@@ -1,6 +1,6 @@
 ---
 title: "Keeping the CLI Current"
-status: draft
+status: accepted
 tags:
   - "cli"
   - "integrations"

.archcore/update/who-triggers-a-cli-update.rfc.md

@@ -1,6 +1,6 @@
 ---
 title: "Who Triggers a CLI Update"
-status: draft
+status: accepted
 tags:
   - "cli"
   - "integrations"

CLAUDE.md

@@ -85,8 +85,9 @@ Commands are registered under `cmd/`.
 - `config` reads and updates `.archcore/settings.json`.
 - `hooks` manages lifecycle hooks.
 - `instructions` manages agent instruction files.
+- `plugin` installs, updates, removes, and reports the Archcore plugin on hosts that ship one.
 - `sync` pushes `.archcore/` state to a configured server.
-- `update` updates the CLI.
+- `update` updates the CLI and the plugin. `archcore mcp` runs the same update unattended, under the policy in `internal/update`.
 
 When adding a command:
 
@@ -106,7 +107,10 @@ When adding a command:
 - `internal/wiring/` implements host wiring.
 - `internal/sync/` implements sync state, hashing, and payload construction.
 - `internal/api/` implements the server API client.
-- `internal/update/` implements self-update.
+- `internal/update/` implements self-update and the unattended update policy.
+- `internal/plugin/` plans and executes plugin actions per host.
+- `internal/telemetry/` sends the update events.
+- `internal/xdg/` resolves the shared state directory.
 - `internal/git/` detects repository metadata.
 - `internal/display/` formats terminal output.
 - `templates/` defines document templates and document types.
@@ -124,6 +128,9 @@ Preserve these constraints:
 - Co-located table-driven Go tests.
 - Optional settings omit defaults where defined.
 - Global Archcore sources are read-only.
+- Unattended update refuses without the official-build marker.
+- Telemetry stays inert without an injected key.
+- The plugin surface never changes behavior outside itself.
 
 ## Out-of-scope Directories
 

README.md

@@ -233,9 +233,28 @@ Documents link with directed relations: `related` (general association), `implem
 | `archcore hooks install` | Install hooks for detected AI agents             |
 | `archcore mcp`           | Run the MCP stdio server                         |
 | `archcore mcp install`   | Install MCP config for detected agents           |
+| `archcore instructions`  | Manage the Archcore hint in instruction files    |
+| `archcore plugin`        | Install, update, or report the Archcore plugin   |
 | `archcore update`        | Update Archcore to the latest version            |
 
-`archcore update` checks GitHub Releases, downloads the newer version, verifies the SHA-256 checksum, and atomically replaces the binary.
+`archcore update` checks GitHub Releases, downloads the newer version, verifies the SHA-256 checksum, and atomically replaces the binary. It then updates the Archcore plugin on each host that already has it installed, and prints the command to run for a host whose CLI it cannot reach.
+
+`archcore plugin` manages that plugin directly on Claude Code, Cursor, Codex CLI, and GitHub Copilot. `archcore init` installs it for the hosts you select there.
+
+</details>
+
+<details>
+<summary><strong>Updating &amp; telemetry</strong></summary>
+
+### Unattended update
+
+From v0.8.0 the CLI also updates itself with nobody watching. `archcore mcp` — the server your agent starts — runs the same check in the background, at most once every 24 hours per machine, and replaces the binary only with a release published by this project, after running the downloaded binary once to prove it starts. The running process is never restarted or interrupted; a new version takes effect the next time the binary launches. Builds you compile yourself, forks, and CI runners never self-update.
+
+No variable and no `.archcore/settings.json` key disables this. If a machine must not update itself, install the binary into a directory its user cannot write — a root-owned location — and every attempt stops before it downloads anything.
+
+### Update analytics
+
+A release build sends one event per update attempt: the versions it moved between, your OS and CPU architecture, whether the run looked like CI, whether you typed the command or the background check ran it, and which step failed when one did. It never sends an error message, a path, a user name, a hostname, or anything about your repository. Set `DO_NOT_TRACK=1` or `ARCHCORE_TELEMETRY_OPTOUT=1` to send nothing at all. Both variables govern analytics only — neither stops the CLI from updating itself. Full detail: [archcore.ai/privacy](https://archcore.ai/privacy).
 
 </details>
 

test/.archcore/settings.json

@@ -0,0 +1,3 @@
+{
+  "sync": "none"
+}

test/.claude/settings.json

@@ -0,0 +1,37 @@
+{
+  "hooks": {
+    "SessionStart": [
+      {
+        "matcher": "",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "archcore hooks claude-code session-start"
+          }
+        ]
+      }
+    ],
+    "PreToolUse": [
+      {
+        "matcher": "Write|Edit",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "archcore hooks claude-code pre-tool-use"
+          }
+        ]
+      }
+    ],
+    "PostToolUse": [
+      {
+        "matcher": "mcp__archcore__(create_document|update_document|remove_document|add_relation|remove_relation)|mcp__plugin_archcore_archcore__(create_document|update_document|remove_document|add_relation|remove_relation)|mcp_archcore_(create_document|update_document|remove_document|add_relation|remove_relation)|archcore-(create_document|update_document|remove_document|add_relation|remove_relation)",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "archcore hooks claude-code post-tool-use"
+          }
+        ]
+      }
+    ]
+  }
+}

test/.mcp.json

@@ -0,0 +1,10 @@
+{
+  "mcpServers": {
+    "archcore": {
+      "command": "archcore",
+      "args": [
+        "mcp"
+      ]
+    }
+  }
+}

test/AGENTS.md

@@ -0,0 +1,20 @@
+<!-- archcore:start --> managed by `archcore init` — edit outside these markers
+## Archcore — project context for this repo
+
+This repo's architecture, decisions, rules, specs and patterns live in `.archcore/`,
+reachable through the Archcore MCP tools. Consult them even on code you think you
+know — a decision or rule may already constrain it.
+
+- Touching this repo's real code or behavior → search first; read only what matches.
+- A decision was made ("we'll use X", "from now on Y") → record it.
+- A module / API / system has no doc — or a search comes back empty → capture it.
+- Planning a feature or refactor → scope it against what's already decided.
+
+A `.archcore/` may also mount read-only **global sources** — shared, org-wide
+context not shown in the session-start list. `list_documents` / `search_documents`
+surface them alongside local docs, tagged `source_kind: "global"`. When present,
+treat them as defaults a local doc can override — never edit or relate to one.
+
+The search is cheap — lean on it. Skip it only for turns this repo would have no
+opinion on: syntax trivia, throwaway snippets, pure mechanics.
+<!-- archcore:end -->

test/CLAUDE.md

@@ -0,0 +1,20 @@
+<!-- archcore:start --> managed by `archcore init` — edit outside these markers
+## Archcore — project context for this repo
+
+This repo's architecture, decisions, rules, specs and patterns live in `.archcore/`,
+reachable through the Archcore MCP tools. Consult them even on code you think you
+know — a decision or rule may already constrain it.
+
+- Touching this repo's real code or behavior → search first; read only what matches.
+- A decision was made ("we'll use X", "from now on Y") → record it.
+- A module / API / system has no doc — or a search comes back empty → capture it.
+- Planning a feature or refactor → scope it against what's already decided.
+
+A `.archcore/` may also mount read-only **global sources** — shared, org-wide
+context not shown in the session-start list. `list_documents` / `search_documents`
+surface them alongside local docs, tagged `source_kind: "global"`. When present,
+treat them as defaults a local doc can override — never edit or relate to one.
+
+The search is cheap — lean on it. Skip it only for turns this repo would have no
+opinion on: syntax trivia, throwaway snippets, pure mechanics.
+<!-- archcore:end -->