docs: simplify workflow documentation - #103
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 8d0ba36494
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| Reasoning values: `none`, `low`, `medium`, `high`, `xhigh`, `max`. | ||
|
|
||
| Fast and reasoning are independent settings, retained only for the same child role; neither affects the primary nor another role. Run `npx codex-model-router@latest status [--global]` to view configured and effective values. Codex currently exposes no per-agent Fast runtime control, so `configured=true` explicitly reports `effective=not-supported`; the installer never enables global `fast_mode` or maps Fast to reasoning. | ||
| Fast and reasoning are independent and retained only for the same child role. Use `status [--global]` to view them; Codex currently has no per-child Fast runtime control, so `configured=true` reports `effective=not-supported`. |
There was a problem hiding this comment.
For users who installed the router through the documented npx invocation, status is not a standalone executable—the package exposes codex-model-router, and install does not install that binary globally. Following this shortened instruction therefore produces a shell command-not-found error; retain the runnable form npx codex-model-router@latest status [--global].
Useful? React with 👍 / 👎.
| ## Plan-artifact lifecycle | ||
| | Stage | Flow | PLAN.md owner | | ||
| | --- | --- | --- | | ||
| | `INITIAL` | Primary confirms → Luna reads/executes → Terra plans/reviews | Current writable executor | |
There was a problem hiding this comment.
When readers use this table to understand the workflow order, the arrows now say that Luna executes before Terra plans. The installed workflow instead collects Luna's evidence, has Terra produce the plan, then has the same Luna persist/reread and implement it before Terra verifies; present those as separate ordered steps rather than grouping reads/executes ahead of plans/reviews.
Useful? React with 👍 / 👎.
1 participant
Summary
Images and workflow implementation are unchanged.
Validation
npm test— 94/94 passednpm run check— passedgit diff --check— passed