jules-orchestrator-kit 0.73.1 → 0.75.0

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.
package/CHANGELOG.md CHANGED
@@ -7,6 +7,29 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
7
7
 
8
8
  ## [Unreleased]
9
9
 
10
+ ## [0.75.0] - 2026-09-28
11
+
12
+ ### Added
13
+ - **Interactive Terminal Navigation Hub (`src/ops/tui-menu.mjs`)**: Added zero-external-dependency terminal UI hub accessible via `agentctl menu`, `tui`, `ui`, or `-i`, using Node.js ESM built-ins (`readline`, ANSI cursor escape sequences). Supports arrow-key navigation, hotkey selection, command preview, contextual execution, and direct handoff to interactive wizards.
14
+ - **Fuzzy Typo Correction & Suggestions (`bin/agentctl.mjs`)**: Implemented Levenshtein-distance suggestion engine for unrecognized CLI commands, surfacing closest matches (e.g. `agentctl dsipatch` suggests `dispatch`).
15
+ - **Actionable Scope Diagnostics & Protected Scope Flag (`src/wizard-task.mjs`)**: Added `--allow-protected` flag to `agentctl task create` alongside detailed diagnostic breakdowns of which paths are protected (e.g. `package.json`, `.agent/protected-paths.json`) when task objectives touch sensitive repository infrastructure.
16
+ - **Task Payload Preview on Dry-Run (`bin/agentctl.mjs`, `src/engine.mjs`)**: `agentctl dispatch --dry-run` now prints formatted task payloads, verification commands, and risk tier assignments before execution.
17
+ - **Maintainer Approval Path for Test Changes (`.github/workflows/agent-scope-guard.yml`, `scripts/ci-scope-guard.mjs`)**: Established narrow maintainer approval protocol (`allow-p:<HEAD_SHA>`, `allow-e:<HEAD_SHA>`) allowing verified modifications to test expectations or protected paths under explicit commit-bound review.
18
+
19
+ ### Fixed
20
+ - **Goal Evidence Enforcement (`src/engine.mjs`)**: Disallowed silent early termination on goal tasks lacking explicit verification evidence.
21
+ - **Test Environment Variable Bleed (`src/engine.mjs`)**: Sanitized test execution environment to prevent PR label bypass tokens from leaking into child test runs during gate evaluation.
22
+
23
+ ## [0.74.0] - 2026-09-19
24
+
25
+ ### Added
26
+ - **Native `agentctl.task/v1` Frontmatter Specification & Zero-Dependency Parser (`src/envelope.mjs`, `scripts/validate-envelope.mjs`)**: Added canonical YAML frontmatter envelope support for task files (`.md`) without third-party dependencies. Reconciles `scope.allow`, `scope.deny`, `verification.commands`, `invariants`, `mcp_directives`, and `flags` with 100% backward compatibility for legacy HTML comments (`<!-- JULES_TASK_ENVELOPE: ... -->`).
27
+ - **Taxonomy Delegation Lanes (Green / Amber / Orange / Red) (`src/envelope.mjs`, `src/wizard-task.mjs`)**: Formulated formal risk lane delegation. Red tasks are rejected at validation; Orange tasks warn for external execution only; Amber tasks allow protected path changes (e.g. dependency upgrades in `package.json`, migrations, auth) under explicit plan approval (`requirePlanApproval: true`). Green tasks prevent unapproved protected scope mutations.
28
+ - **Circuit Breaker & Verification Contract in Envelope (`src/envelope.mjs`)**: Added frontmatter declarations for `circuitBreaker` (`max_attempts`, `max_diff_lines`, `stop_if_same_failure_repeats`) and `verification` metadata (`require_nonzero_test_count`, `trusted_base`), alongside `constraints` alias support.
29
+ - **Stack Invariant & MCP Directive Ingestion (`src/wizard-task.mjs`)**: Automatically infers runtime constraints (Zero-JS for Astro, workerd edge runtime constraints for Cloudflare Wrangler) and injects mandatory pre-execution documentation lookup directives into task instructions.
30
+ - **Dependency Upgrade Scope Harmonization (`src/wizard-task.mjs`)**: Updated `buildGuardrailFooter` to exclude explicitly authorized paths (`opts.allowedPaths`) from forbidden path warnings, eliminating conflicting instructions for dependency upgrade workloads.
31
+ - **Diff Payload Governor Branch Base Comparison (`src/wizard-task.mjs`)**: Calculated diff payload sizes against `git diff origin/${baseBranch}...HEAD | wc -c` instead of local uncommitted diffs.
32
+
10
33
  ## [0.73.1] - 2026-09-17
11
34
 
12
35
  ### Changed
package/README.md CHANGED
@@ -12,11 +12,12 @@ Use the kit to describe a scoped coding task, send it to Google Jules or an
12
12
  installed Claude Code, Codex or Gemini CLI, and verify the resulting changes.
13
13
  You can also run local checks without connecting an agent provider.
14
14
 
15
- **Dispatch and verification are separate.** Dispatch sends the task; `gate` runs
16
- configured checks on changes. `gate --fix` can request automated repairs. Provider
17
- output and passing checks still need review before merging.
15
+ **Dispatch, verification and repair are explicit.** Dispatch sends the task;
16
+ `gate` runs configured checks without mutating the working tree. Use
17
+ `agentctl repair` explicitly for repair workflows. Provider output and passing
18
+ checks still need review before merging.
18
19
 
19
- The current release is **v0.73.1**, a pre-1.0 release. A long-term stability policy is a
20
+ The current release is **v0.75.0**, a pre-1.0 release. A long-term stability policy is a
20
21
  [v1.0 goal](https://github.com/FullThrottle83/jules-orchestrator-kit/blob/main/ROADMAP_V1.md).
21
22
 
22
23
  ## Quickstart
@@ -32,9 +33,16 @@ npx jules-orchestrator-kit init
32
33
  ```
33
34
 
34
35
  The wizard detects the project and asks about provider and verification settings.
35
- Use `init --yes` to accept defaults. It creates `.agent/config.yml`, agent
36
- instructions, role prompts and project contract files. Inspect the generated
37
- configuration and diff, especially the test command and protected paths.
36
+ Use `init --yes` to accept defaults. By default it writes only the canonical
37
+ `.agent/config.yml` plus runtime-state entries in `.gitignore` when they are
38
+ missing. Inspect the generated configuration and diff, especially the test
39
+ command and protected paths. Use `init --dry-run` to preview the exact writes
40
+ without changing the repository.
41
+
42
+ The historical full scaffold (AGENTS.md, specialist prompts, rules, workflows and
43
+ contract templates) remains available through `agentctl init --force` and the
44
+ legacy `jules-init` entry point during the 0.x migration window; it is no longer
45
+ default-owned by `agentctl init`.
38
46
 
39
47
  ```bash
40
48
  git diff
@@ -43,9 +51,9 @@ git status --short
43
51
 
44
52
  Stage the generated files you reviewed, then commit them. The committed
45
53
  configuration establishes the trusted base policy used by verification. On an
46
- already initialized repository, back up and review `.agent/config.yml` and
47
- `.agent/jules.yml` before rerunning `init`; the wizard can regenerate those
48
- manifests. Avoid `--force` unless replacement of generated files is intended.
54
+ already initialized repository, back up and review `.agent/config.yml` before
55
+ rerunning `init`. Existing legacy `.agent/jules.yml` files are left untouched
56
+ by the default path. `--force` deliberately opts back into the legacy full scaffold.
49
57
 
50
58
  ### 2. Check provider readiness
51
59
 
@@ -107,7 +115,7 @@ For direct `agentctl` commands, install globally with
107
115
  | Create a scoped task | `agentctl task create` |
108
116
  | Preview queued work | `agentctl queue --dry-run` |
109
117
  | Check changes locally | `agentctl gate` |
110
- | Verify and request repairs | `agentctl gate --fix` |
118
+ | Start an explicit repair workflow | `agentctl repair --input "<failure>" --task` |
111
119
  | Diagnose setup | `agentctl doctor` |
112
120
  | Inspect a command's flags | `agentctl help <command>` |
113
121
 
@@ -166,7 +174,7 @@ npm run package-integrity
166
174
  npm run guard-reach
167
175
  ```
168
176
 
169
- The recorded baseline is **1530 unit tests across 204 suites**. Doc-sync compares
177
+ The recorded baseline is **1650 unit tests across 210 suites**. Doc-sync compares
170
178
  that count with an actual run. Counts do not establish correctness for every
171
179
  provider or project. See
172
180
  [contributing](https://github.com/FullThrottle83/jules-orchestrator-kit/blob/main/CONTRIBUTING.md)
@@ -186,19 +194,12 @@ for the review process.
186
194
  First identify which files setup created and which files already belonged to your
187
195
  project. For shared files, remove only the kit's additions using Git history.
188
196
 
189
- For a repository where **all listed paths belong exclusively to the kit**, remove
190
- the tracked scaffold and runtime state as follows. Adapt this list first if any
191
- path contains your own instructions, configuration or queued work:
192
-
193
- ```bash
194
- git rm -rf --ignore-unmatch .agent AGENTS.md SPEC.md CONSTRAINTS.md DESIGN.md \
195
- .github/workflows/agent-gate.yml .gitlab-ci.agent-gate.yml .cursor/rules/jules.mdc
196
- rm -rf .agent .agentctl
197
- npm uninstall -g jules-orchestrator-kit
198
- ```
197
+ For the default minimal setup, remove `.agent/config.yml` and the kit's
198
+ runtime-state block from `.gitignore`. Repositories that previously used the
199
+ legacy full scaffold may also contain AGENTS.md, prompts, rules, workflows and
200
+ contract files; remove those only after confirming ownership.
199
201
 
200
- Remove the kit's appended `.gitignore` block while preserving other entries.
201
- See the uninstall guide for the complete inventory.
202
+ See the uninstall guide for the complete inventory and legacy cleanup steps.
202
203
 
203
204
  ## Limitations and attribution
204
205