refactor: overhaul workflow prompts with progressive loading - #197
refactor: overhaul workflow prompts with progressive loading#197parsakhaz wants to merge 2 commits into
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 7df02bb4a3
ℹ️ 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".
| existing task branch only when it belongs to this item. Otherwise create a | ||
| named work branch from the current default, using an isolated worktree if | ||
| unrelated edits or another task's PR need to be preserved. Branch/worktree |
There was a problem hiding this comment.
Preserve loaded artifacts when switching worktrees
When /do starts from a local-only ./tmp/<id>/brief.html on the default branch with unrelated edits, Step 0 loads the item into the current checkout before these lines create an isolated worktree. Because tmp/ is ignored and worktree-local, the new worktree will not contain the brief, its refs, or the plan path required by subsequent stages, and a local-only item cannot be fetched again from a tracker. Select the execution worktree before loading the item, or explicitly transfer the complete scratch bundle into the new worktree.
AGENTS.md reference: AGENTS.md:L75-L78
Useful? React with 👍 / 👎.
The workflow entrypoints bundled every phase, dispatch command, and diagram recipe into the initial skill load. They also required unnecessary setup and branch-creation pauses. This applies Eric Provencher's guidance while preserving Orchestra's execution and evidence contracts.
What changes
Most reference-file additions are moved instructions. Claude/Codex-specific browser and review-budget behavior remains distinct.
Verification
Documentation and diagrams
The default local Chromium renderer could not launch in this environment. Rendering used the same Excalidraw 0.18 export API with its bundled fonts and native SVG rasterization. No renderer or dependency changes are included.
Limits
No live daemon run, production mutation, or consumer rollout was performed. Existing consumers receive these changes through their normal sync PR flow.