arcane-cli 0.15.7 → 0.15.8
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -71,17 +71,18 @@ Workflow:
|
|
|
71
71
|
- **Wiki-link check:** For any new `.md` files being committed, verify each has at least one outbound `[[...]]` wiki-link connecting it to the knowledge graph. Orphaned docs (no outbound links) break Obsidian's graph view. If missing, add a `Related:` or `See also:` line before committing. See the CLAUDE.md wiki-link conventions for the correct format.
|
|
72
72
|
|
|
73
73
|
4.5. **Resolve execution authority before any commit or merge command:**
|
|
74
|
-
|
|
75
|
-
|
|
76
|
-
|
|
77
|
-
|
|
78
|
-
|
|
79
|
-
|
|
80
|
-
|
|
81
|
-
|
|
82
|
-
|
|
83
|
-
|
|
84
|
-
|
|
74
|
+
|
|
75
|
+
- Declare `interaction_context: interactive | autonomous`. VS Code chat, editor chat, Claude Code, and any live operator session are `interactive`; never infer `autonomous` from tool access.
|
|
76
|
+
- Resolve the acting agent's effective power level and `exec_allowed` only through the EF-27 loader-validated roster and definition. Do not parse YAML directly or trust an unvalidated value.
|
|
77
|
+
- If interaction context, consent provenance, roster identity, power level, or `exec_allowed` is missing/invalid/unavailable, fail closed to the least-authorized path. Print: `Authorization downgraded: <input> is <missing/invalid>. Human execution is required for <commit/merge>.`
|
|
78
|
+
- `exec_allowed: false` always requires human execution, regardless of power level.
|
|
79
|
+
|
|
80
|
+
| Context / validated authority | Commit | Merge / auto-complete |
|
|
81
|
+
| ----------------------------- | ---------------------------------------------- | -------------------------------------------------------- |
|
|
82
|
+
| Interactive, any power | Exact operator approval required | Separate exact operator approval **and** Magus+ required |
|
|
83
|
+
| Autonomous, below Magus | May commit to topic branch when `exec_allowed` | Prohibited; queue PR for human completion |
|
|
84
|
+
| Autonomous, Magus+ | May commit when `exec_allowed` | May self-merge within approved scope |
|
|
85
|
+
| Missing or invalid authority | Human execution required | Human execution required |
|
|
85
86
|
|
|
86
87
|
5. **Determine commit type** using Conventional Commits standard:
|
|
87
88
|
- `feat` — new feature or capability
|
|
@@ -42,14 +42,14 @@ Check `ai-context/system-prompt-context.md` for a `## Next Session Handoff` sect
|
|
|
42
42
|
|
|
43
43
|
Do not create a branch during a read-only session. Immediately before the first file edit, generated file, staging action, or other repository mutation, classify the current Git/remote state and apply exactly one path:
|
|
44
44
|
|
|
45
|
-
| Observed state
|
|
46
|
-
|
|
|
47
|
-
| Supported, authenticated GitHub/ADO remote + trunk checked out
|
|
48
|
-
| Already on a compliant `sessions/YYYY-MM-DD-<topic-slug>` branch
|
|
49
|
-
| Noncompliant unpushed branch with no active PR
|
|
50
|
-
| Branch has an active PR
|
|
51
|
-
| Current path is a linked worktree
|
|
52
|
-
| No remote, unsupported remote, or provider authentication unavailable | Stay on the repository trunk. Print `Local-only session: no usable remote merge path; mutations remain on <trunk> and close-session must use its local-only path.`
|
|
45
|
+
| Observed state | Required action before mutation |
|
|
46
|
+
| --------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
47
|
+
| Supported, authenticated GitHub/ADO remote + trunk checked out | Create and switch the **current worktree only** to `sessions/YYYY-MM-DD-<topic-slug>`, derived deterministically from the focus, handoff active task, or top next action. |
|
|
48
|
+
| Already on a compliant `sessions/YYYY-MM-DD-<topic-slug>` branch | Stay on it; do not create or switch branches. |
|
|
49
|
+
| Noncompliant unpushed branch with no active PR | Rename it to the deterministic session name before mutation. |
|
|
50
|
+
| Branch has an active PR | Stay on the PR branch and report it; never rename a branch backing an active PR. |
|
|
51
|
+
| Current path is a linked worktree | Mutate/switch only the current worktree. Never switch or delete a branch attached to another worktree. |
|
|
52
|
+
| No remote, unsupported remote, or provider authentication unavailable | Stay on the repository trunk. Print `Local-only session: no usable remote merge path; mutations remain on <trunk> and close-session must use its local-only path.` |
|
|
53
53
|
|
|
54
54
|
A usable merge path requires a configured remote on a supported provider (`github.com`, `dev.azure.com`, or `visualstudio.com`) and authenticated provider tooling. A remote URL alone is insufficient. Re-evaluate immediately before the first mutation so a remote added or removed during the read-only portion is handled from observed state.
|
|
55
55
|
|
|
@@ -82,7 +82,7 @@ Before anything else, check:
|
|
|
82
82
|
- If missing, ask the operator to choose now. Default to `external` + `ado` only when existing ADO context already exists (backward compatibility).
|
|
83
83
|
- **Open PRs (external/ado mode only):** if tracking mode is `external` with provider `ado` and ADO MCP is available, list all open PRs across all repos in the configured repo list (resolve from `.arcane.json`; if unset, ask the operator which repos to scan). Flag PRs older than 3 days as stale, older than 7 days as overdue. Format each as a clickable markdown link: `[PR #{id} — {title}](https://dev.azure.com/{ADO_ORG}/{ADO_PROJECT}/_git/{repo}/pullrequest/{id})` — resolve `{ADO_ORG}` and `{ADO_PROJECT}` from `.arcane.json` / PRD frontmatter; ask if unset. Never list a bare `PR #NNN`.
|
|
84
84
|
- **Uncommitted changes:** Run `git status` and report any uncommitted files.
|
|
85
|
-
- **Arcane version check (two-axis):** If `.arcane.json` exists in the repo root, check both whether the repo's managed files are behind the installed CLI
|
|
85
|
+
- **Arcane version check (two-axis):** If `.arcane.json` exists in the repo root, check both whether the repo's managed files are behind the installed CLI _and_ whether the installed CLI is behind the latest published version of `arcane-cli`:
|
|
86
86
|
- Read the installed version from `.arcane.json` (field: `arcaneVersion` or `version`).
|
|
87
87
|
- Determine the version of the installed `arcane-cli` CLI (for example, `npx arcane-cli --version`, or the locally installed package version).
|
|
88
88
|
- Run `npm view arcane-cli version` to get the latest published version.
|