taskchef 2.0.0 → 3.0.1
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/.codex-plugin/plugin.json +3 -3
- package/BACKLOG.md +35 -82
- package/README.md +211 -108
- package/SPEC.md +114 -246
- package/assets/taskchef-dispatcher-instructions.md +3 -2
- package/index.js +2 -5
- package/package.json +6 -2
- package/skills/taskchef-bootstrap/SKILL.md +11 -11
- package/skills/taskchef-delegate/SKILL.md +16 -18
- package/skills/taskchef-report/SKILL.md +38 -0
- package/skills/taskchef-report/agents/openai.yaml +4 -0
- package/src/cli.js +26 -70
- package/src/workspace.js +315 -251
- package/skills/taskchef-reconcile/SKILL.md +0 -35
- package/skills/taskchef-reconcile/agents/openai.yaml +0 -4
|
@@ -1,35 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
name: taskchef-reconcile
|
|
3
|
-
description: "Reconcile active TaskChef task records with their visible Codex executor threads. Use only when the user asks to refresh, fix, or repair outdated TaskChef task states. Performs one bounded snapshot pass and never polls or waits for future activity."
|
|
4
|
-
---
|
|
5
|
-
|
|
6
|
-
# TaskChef Reconcile
|
|
7
|
-
|
|
8
|
-
Refresh TaskChef's recorded task state from native Codex threads exactly once.
|
|
9
|
-
|
|
10
|
-
Resolve this skill directory with `realpath`. The TaskChef plugin root is two
|
|
11
|
-
parents above the skill directory. Invoke `<plugin-root>/bin/taskchef.js` for
|
|
12
|
-
all deterministic record operations.
|
|
13
|
-
|
|
14
|
-
## Reconcile
|
|
15
|
-
|
|
16
|
-
1. Run `task reconcile-candidates --json` once. It returns only `running` and
|
|
17
|
-
`blocked` tasks with thread IDs. Do not scan pending or finished records.
|
|
18
|
-
2. Query every returned thread exactly once using immediate native snapshots,
|
|
19
|
-
with no more than eight targets per call.
|
|
20
|
-
3. Do not wait for future activity and do not poll.
|
|
21
|
-
4. Map an active attempt to `running`, a user-input or external dependency to
|
|
22
|
-
`blocked`, and any concluded attempt to `finished`, including failed or
|
|
23
|
-
partial attempts.
|
|
24
|
-
5. Preserve an existing result unless the thread provides a meaningful newer
|
|
25
|
-
report. Results contain exactly `message`, `githubPRs`, and `githubIssues`.
|
|
26
|
-
6. Update each changed record once with `task update`.
|
|
27
|
-
7. Report a concise snapshot and continue with the user's request. If there
|
|
28
|
-
were no candidates or changes, say so briefly.
|
|
29
|
-
|
|
30
|
-
Use `task reconcile-candidates --include-finished --json` only when the user
|
|
31
|
-
explicitly requests a full refresh or says a finished executor received new
|
|
32
|
-
work. A finished task with a new active attempt becomes `running` again.
|
|
33
|
-
|
|
34
|
-
The native thread is authoritative between reconciliations. Executor reports
|
|
35
|
-
are evidence, not independently verified completion guarantees.
|