halfcycle 0.4.17 → 0.5.0

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "halfcycle",
-  "version": "0.4.17",
+  "version": "0.5.0",
   "description": "Halfcycle Method bundle — resolution-stub slash commands, remote method-delivery registration, and governance-hook wiring for a Halfcycle engagement repo. It ships NO worker role files: a project's roles are authored from that project's own recorded decisions at orchestration kickoff (FX-2, W3-F-27).",
   "commands": [
     {

package/README.md

@@ -16,7 +16,7 @@ That is the whole install. One command, in the repo you want to work in.
 
 Good software gets built by several people doing different jobs. Somebody decides what is being built. Somebody decides how it fits together. Somebody cuts it into pieces small enough to finish. Somebody else checks the work, because whoever did it is the worst judge of it. And somebody writes the code.
 
-AI gave everybody that last one. Halfcycle is the other four, running inside your own Claude Code.
+AI gave everybody that last one. Halfcycle is the other four, running inside your own Claude Code or Codex.
 
 | | |
 |---|---|
@@ -144,7 +144,7 @@ Underneath all five: one authoritative copy of every document, rules referenced
 
 This matters enough to be specific about.
 
-**Halfcycle never holds or proxies your Claude credential.** Inference runs on your own Claude Code, on your own subscription or seats. We are not a hosted runtime reselling you inference.
+**Halfcycle never holds or proxies your Claude or OpenAI credential.** Inference runs on your own Claude Code or Codex, on your own subscription or seats. We are not a hosted runtime reselling you inference.
 
 **Your own Halfcycle credential lives outside this repository, in a file named `env` under your home directory — never in anything you'd commit.** Installing writes it. Opening or closing a phase rewrites it, to record which phase is open, and the credential in it is also renewed there automatically to keep your connection current. Uninstalling with `--remove-credential` deletes it. Nothing else changes it.
 
@@ -164,9 +164,10 @@ Nothing you already had is changed. Existing settings are preserved, and a name
 
 ## Requirements
 
-- Claude Code **2.1.118+**
+- Claude Code **2.1.118+**, or Codex **0.166.0+**
 - Node 18+
 - A git repository
+- On Windows, Git for Windows
 - On Windows, in PowerShell, use `npx.cmd` instead of `npx` (PowerShell's default settings block the `npx` script; `npx.cmd` always works, with nothing to change).
 
 ## Getting started
@@ -191,6 +192,8 @@ Then open the folder in Claude Code and run `/halfcycle-setup`, and answer the q
 
 **A second prompt follows — it is not the trust prompt again.** After you accept the trust prompt, Claude Code asks whether to use a new MCP server. If halfcycle is the only one listed, the cursor starts on *Continue without using this MCP server*; choose to use the server instead, or Halfcycle will not connect. If several new servers are listed together, halfcycle is already checked — leave it that way.
 
+**Using Codex?** Open the folder in Codex and trust it when asked. Then type `/hooks` and approve each Halfcycle entry — until you do, Codex works without Halfcycle checking its edits. Then type `$halfcycle-setup` and answer what it asks about your project. One difference today: Codex cannot stop to ask you before a risky step, so Halfcycle holds that step instead and says why.
+
 You will get a board link on install. That is where the work becomes visible to anyone who is not you.
 
 ---