@hecer/yoke 1.6.1 → 1.6.2

package/.claude-plugin/plugin.json

@@ -2,7 +2,7 @@
   "$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
   "name": "yoke",
   "displayName": "Yoke",
-  "version": "1.6.1",
+  "version": "1.6.2",
   "description": "Cross-agent coding harness: one curated skill canon (TDD, brainstorming, plans, reviews, shipping, design verification) plus mechanical safety gates and an autonomous loop via the yoke CLI.",
   "author": { "name": "HECer", "url": "https://github.com/HECer" },
   "homepage": "https://github.com/HECer/yoke#readme",

package/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "yoke",
-  "version": "1.6.1",
+  "version": "1.6.2",
   "description": "Cross-agent coding discipline, mechanical gates, and release workflows",
   "skills": "./canon/skills/",
   "hooks": "./hooks/hooks.json"

package/CHANGELOG.md

@@ -2,11 +2,21 @@
 
 ## Unreleased
 
+## 1.6.2 — 2026-09-02
+
+### Added
+- GitHub Releases can now publish `@hecer/yoke` through npm trusted publishing with short-lived OIDC credentials and automatic provenance, without a long-lived npm token.
+
+### Fixed
+- Codex safe-mode invocations now use the supported `workspace-write` sandbox with `--approve-for-me`; the removed `--full-auto` flag no longer blocks current Codex CLI releases.
+- Windows provider cleanup rechecks termination after process close and accepts an already-absent process as successfully cleaned up, avoiding stale ownership records and unnecessary watchdog waits.
+- Successful stale-loop cleanup removes obsolete runtime status, so `yoke loop status` no longer reports a dead run as `RUNNING`.
+
 ## 1.6.1 — 2026-08-21
 
 ### Fixed
-- Release metadata now counts platform-conditional tests consistently on Windows and Ubuntu, so `docs:check` no longer fails after an otherwise green cross-platform test matrix.
-- Provider cleanup now rechecks termination after the child closes, preventing stale ownership records when Windows reports process exit asynchronously.
+- Release metadata counts platform-conditional tests consistently on Windows and Ubuntu.
+- Provider cleanup confirms termination after child close, preventing stale ownership records when Windows reports process exit asynchronously.
 
 ## 1.6.0 — 2026-08-20
 

package/README.md

@@ -2,8 +2,8 @@
 
 # 🐂 Yoke
 
-<!-- yoke:version:start -->1.6.1<!-- yoke:version:end -->
-<!-- yoke:tests:start -->1019<!-- yoke:tests:end -->
+<!-- yoke:version:start -->1.6.2<!-- yoke:version:end -->
+<!-- yoke:tests:start -->1021<!-- yoke:tests:end -->
 <!-- yoke:skills:start -->34<!-- yoke:skills:end -->
 <!-- yoke:agents:start -->Claude | Codex | Gemini<!-- yoke:agents:end -->
 
@@ -17,7 +17,7 @@
 [![License: MIT](https://img.shields.io/badge/license-MIT-blue.svg)](#-license)
 ![Node](https://img.shields.io/badge/node-%E2%89%A520-339933?logo=node.js&logoColor=white)
 ![TypeScript](https://img.shields.io/badge/TypeScript-3178C6?logo=typescript&logoColor=white)
-![Tests](https://img.shields.io/badge/tests-1019%20passing-brightgreen.svg)
+![Tests](https://img.shields.io/badge/tests-1021%20passing-brightgreen.svg)
 ![Agents](https://img.shields.io/badge/agents-Claude%20%7C%20Codex%20%7C%20Gemini-8A2BE2)
 ![Built with TDD](https://img.shields.io/badge/built%20with-TDD%20%2B%20review-ff69b4.svg)
 
@@ -81,7 +81,7 @@ $ ls reading-app/.yoke/proof/STORY-2/
 home.png  list.png                            # photographic evidence, labelled per story
 ```
 
-Every claim in that transcript is enforced by code paths with tests behind them — 1019 of them, and this repo was built by its own loop and gates ([how it was built](#-why--how-it-was-built)).
+Every claim in that transcript is enforced by code paths with tests behind them — 1021 of them, and this repo was built by its own loop and gates ([how it was built](#-why--how-it-was-built)).
 
 ## 🚀 Quickstart
 
@@ -856,7 +856,7 @@ release provenance.
 ## 🧪 Development
 
 ```bash
-npm test          # vitest (1019 tests)
+npm test          # vitest (1021 tests)
 npm run build     # tsc, no emit errors
 npm run yoke -- validate canon
 ```

package/canon/manifest.yaml

@@ -1,5 +1,5 @@
 name: yoke-canon
-version: 1.6.1
+version: 1.6.2
 agents: [claude, codex, gemini]
 skills:
   - { id: tdd, path: skills/tdd, kind: methodology, invocation: auto }

package/dist/agents/process.js

@@ -81,6 +81,8 @@ export function startProviderProcess(agent, invocation, options = {}) {
         telemetry: telemetry.finish(),
     });
     const finalize = (exitCode) => {
+        // Windows can emit close before taskkill's process-tree state is observable.
+        // Reconfirm here so successful termination does not leave a stale ownership record.
         if (termination && pid !== undefined && !terminationConfirmed) {
             terminationConfirmed = terminateProcessTree(pid, true);
         }

package/dist/agents/providers.js

@@ -13,7 +13,7 @@ const argsFor = (agent, permissions) => {
             return ['exec', '--dangerously-bypass-approvals-and-sandbox', '--json'];
         if (permissions === 'read-only')
             return ['exec', '--sandbox', 'read-only', '--json'];
-        return ['exec', '--full-auto', '--json'];
+        return ['exec', '--sandbox', 'workspace-write', '--approve-for-me', '--json'];
     }
     if (permissions === 'unsafe')
         return ['--yolo'];

package/dist/loop/cleanup.js

@@ -6,6 +6,7 @@ import { processIncarnation } from '../agents/process-incarnation.js';
 import { acquireTakeoverLease, acquireTakeoverRecoveryLease, lockPath, takeoverLockPath, readLock, isPidAlive, releaseTakeoverLease, releaseTakeoverRecoveryLease, takeoverRecoveryPath, } from './lock.js';
 import { killProcessForCleanup, killProcessTreeForCleanup } from './watchdog.js';
 import { cleanupClaims } from './claims.js';
+import { clearStatus } from './reporter.js';
 // Reap orphaned runners PROJECT-SCOPED: kill only pids recorded in this project's
 // .yoke/runner.pid files (main dir + each worktree). Never by process-name or
 // command-line pattern — that takes down runners belonging to OTHER projects,
@@ -223,6 +224,8 @@ export function runLoopCleanup(targetDir, opts = {}) {
             rmSync(lockFile, { force: true });
             console.log('Removed stale loop lock.');
         }
+        if (failed === 0)
+            clearStatus(targetDir);
         console.log(removed === 0 && failed === 0 ? 'No destructive cleanup performed.' : `Removed ${removed} worktree(s)${failed > 0 ? `, ${failed} failed` : ''}.`);
         return failed === 0 ? 0 : 1;
     }

package/dist/loop/reporter.js

@@ -1,4 +1,4 @@
-import { existsSync, readFileSync, writeFileSync, mkdirSync, renameSync, appendFileSync, statSync } from 'node:fs';
+import { existsSync, readFileSync, writeFileSync, mkdirSync, renameSync, appendFileSync, statSync, rmSync } from 'node:fs';
 import { join } from 'node:path';
 export const LOG_CAP_BYTES = 256 * 1024;
 // Append a line to .yoke/loop.log, keeping the file bounded: once it exceeds
@@ -77,6 +77,9 @@ export function readStatus(dir) {
         return null;
     }
 }
+export function clearStatus(dir) {
+    rmSync(statusPath(dir), { force: true });
+}
 export function makeReporter(dir, opts = {}, now = () => new Date()) {
     const sink = opts.log ?? ((line) => process.stdout.write(line + '\n'));
     const emitConsole = (line) => { if (!opts.quiet)

package/dist/loop/watchdog.js

@@ -62,6 +62,8 @@ export function killProcessTreeForCleanup(pid, platform = process.platform, runT
     }
 }) {
     if (platform === 'win32') {
+        // taskkill reports a non-zero status when the process disappeared between
+        // observation and cleanup; that is already the desired terminal state.
         if (runTaskkill('taskkill', ['/PID', String(pid), '/T', '/F']) !== 0)
             return !isProcessAlive(pid);
         return confirmProcessStopped(pid, isProcessAlive);

package/docs/PUBLISHING.md

@@ -6,7 +6,7 @@ Where Yoke is published, and how each channel gets updated. (Reviewed 2026-08-20
 
 | Channel | How | Update path |
 |---|---|---|
-| **npm** — [`@hecer/yoke`](https://www.npmjs.com/package/@hecer/yoke) | `npm publish` (2FA) | every release |
+| **npm** — [`@hecer/yoke`](https://www.npmjs.com/package/@hecer/yoke) | GitHub OIDC trusted publishing | every release |
 | **GitHub** — [HECer/yoke](https://github.com/HECer/yoke) | push + tag + GitHub Release | every release |
 | **Claude Code plugin (self-marketplace)** | `.claude-plugin/plugin.json` + `marketplace.json` in this repo; users: `/plugin marketplace add HECer/yoke` → `/plugin install yoke@yoke` | bump `version` in `plugin.json` |
 | **Gemini CLI extension** | `gemini-extension.json` + `GEMINI-EXTENSION.md` at repo root; users: `gemini extensions install https://github.com/HECer/yoke` | bump `version` in the manifest |
@@ -33,7 +33,7 @@ release object is created. Use this idempotent check after the version commit re
 
 ```bash
 set -euo pipefail
-VERSION=1.6.1
+VERSION=1.6.2
 TARGET=$(git rev-parse HEAD)
 git fetch --tags origin
 
@@ -62,6 +62,29 @@ gh release view "v$VERSION" >/dev/null 2>&1 || \
 Verify both surfaces before publishing npm: `gh release view "v$VERSION"` and
 `npm view @hecer/yoke version`.
 
+## npm trusted publishing
+
+The `publish-npm.yml` workflow publishes a stable package automatically when a GitHub Release is
+published. It checks out that exact tag, requires the tag to match the version in `package.json`,
+reruns `prepublishOnly` through `npm publish`, and skips a version that already exists. GitHub OIDC
+provides a short-lived publishing identity; no `NPM_TOKEN` repository secret is used. npm adds
+provenance automatically for this public repository.
+
+One package-owner setup step is required on npmjs.com under the `@hecer/yoke` package settings:
+
+- Publisher: GitHub Actions
+- Organization or user: `HECer`
+- Repository: `yoke`
+- Workflow filename: `publish-npm.yml`
+- Environment: leave empty
+- Allowed action: `npm publish`
+
+After the trusted publisher exists, the next GitHub Release publishes automatically. To publish an
+already-created release such as `v1.6.1`, run the **Publish npm** workflow manually and provide that
+existing tag. The workflow refuses tags without a published GitHub Release and refuses tag/version
+mismatches. After the first successful OIDC publish, disable traditional token publishing and revoke
+obsolete automation tokens in npm package settings.
+
 ## Submitted / pending
 
 | Channel | How | Status |

package/gemini-extension.json

@@ -1,6 +1,6 @@
 {
   "name": "yoke",
-  "version": "1.6.1",
+  "version": "1.6.2",
   "description": "Cross-agent coding harness: curated skill canon, mechanical safety gates, autonomous loop with proof artifacts. CLI: npm i -g @hecer/yoke",
   "contextFileName": "GEMINI-EXTENSION.md"
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hecer/yoke",
-  "version": "1.6.1",
+  "version": "1.6.2",
   "description": "One harness, three agents, zero trust in \"done\" — cross-agent coding harness for Claude Code, Codex CLI, and Gemini CLI: one skill canon, mechanical safety gates, an autonomous loop with screenshot/video proofs.",
   "type": "module",
   "bin": {