taskchef 7.27.1 → 7.27.2
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/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: taskchef-bootstrap
|
|
3
|
-
description: "Initialize
|
|
3
|
+
description: "Initialize or repair the TaskChef dispatcher workspace and manage its local Codex project index. Use for setup, doctor, import, or reindex requests; not dispatch or executor reporting."
|
|
4
4
|
---
|
|
5
5
|
|
|
6
6
|
# TaskChef Bootstrap
|
|
@@ -50,118 +50,9 @@ all deterministic workspace operations.
|
|
|
50
50
|
End without dispatching unless the user
|
|
51
51
|
separately requested work.
|
|
52
52
|
|
|
53
|
-
##
|
|
53
|
+
## Project index operations
|
|
54
54
|
|
|
55
|
-
|
|
56
|
-
|
|
57
|
-
|
|
58
|
-
|
|
59
|
-
|
|
60
|
-
Index only Codex projects local to the TaskChef workspace's execution host.
|
|
61
|
-
Remote connection projects are outside the v1 contract. Never index the
|
|
62
|
-
TaskChef dispatcher workspace or a directory containing it; the dispatcher is
|
|
63
|
-
the inbox, while indexed Codex projects own delegated work.
|
|
64
|
-
|
|
65
|
-
### Existing Codex project
|
|
66
|
-
|
|
67
|
-
1. List native local Codex projects once. Resolve the requested existing folder
|
|
68
|
-
with `realpath` and require an exact canonical-path match in that list. A
|
|
69
|
-
similar name, a parent or child directory, and a remote connection project
|
|
70
|
-
are not matches.
|
|
71
|
-
2. Index the exact path with the existing `project add <canonical-path> --name
|
|
72
|
-
<curated-name> --description <curated-description> --json` CLI workflow.
|
|
73
|
-
Despite the command's historical `add` name, this writes one TaskChef index
|
|
74
|
-
entry for an existing Codex project. The CLI detects Git status, the exact
|
|
75
|
-
Git root, and a canonical GitHub `origin` when no repository option is
|
|
76
|
-
supplied. Repeated `--github-repo <canonical-url>` arguments replace that
|
|
77
|
-
detection and form the complete advertised repository list, so repeat the
|
|
78
|
-
origin explicitly when it should remain routable. Use `--no-github` when the
|
|
79
|
-
user intentionally wants an empty list.
|
|
80
|
-
3. Run `project list --json` and require one indexed entry with the exact
|
|
81
|
-
canonical path and intended routing metadata. Only then report that the
|
|
82
|
-
Codex project is ready for delegation through TaskChef.
|
|
83
|
-
|
|
84
|
-
### New or not-yet-saved Codex folder
|
|
85
|
-
|
|
86
|
-
1. Create the folder only when the user explicitly asked to create it. Preserve
|
|
87
|
-
unrelated existing contents. Do not initialize Git unless requested or
|
|
88
|
-
clearly required by the user's broader task. Resolve the resulting existing
|
|
89
|
-
folder with `realpath`.
|
|
90
|
-
2. Register or open that exact canonical folder with the supported
|
|
91
|
-
`<validated-codex-cli> app <canonical-path>` mechanism. Reuse a validated CLI
|
|
92
|
-
path supplied by the current Codex Desktop environment when available. Use
|
|
93
|
-
the same resolver contract as `workspace init --register-codex` otherwise:
|
|
94
|
-
an explicit `--codex-cli` path takes precedence over `TASKCHEF_CODEX_CLI`;
|
|
95
|
-
each must resolve to an executable that passes `app --help`. Without an
|
|
96
|
-
override, inspect `codex` executables from `PATH`, prefer a validated
|
|
97
|
-
candidate whose path contains `Contents/Resources`, and otherwise validate
|
|
98
|
-
only the first executable `codex` in PATH order. Never assume an arbitrary
|
|
99
|
-
shell `codex`, invoke `codex add`, or hard-code an application bundle path.
|
|
100
|
-
3. Re-list native local Codex projects and require an exact canonical-path
|
|
101
|
-
match. Opening is a request, not proof that Codex saved the project. If the
|
|
102
|
-
exact match is absent, report that the folder was opened or registration was
|
|
103
|
-
requested but Codex registration remains unverified; do not index it in
|
|
104
|
-
TaskChef or call it delegation-ready.
|
|
105
|
-
4. After Codex verification, index the project as in the existing-project path.
|
|
106
|
-
Run `project list --json` and verify the exact TaskChef index entry. Report
|
|
107
|
-
delegation readiness only after both the native Codex match and TaskChef
|
|
108
|
-
indexing are verified.
|
|
109
|
-
|
|
110
|
-
For a managed `*-workspace` Codex project, advertise every relevant child or
|
|
111
|
-
subrepository with repeated `--github-repo <canonical-github-url>` arguments,
|
|
112
|
-
including the workspace repository itself when it can own issue or pull-request
|
|
113
|
-
links. These explicit values are the complete list; automatic origin detection
|
|
114
|
-
does not supplement them. This lets TaskChef route each canonical GitHub URL to
|
|
115
|
-
the correct workspace rather than guessing from the folder name.
|
|
116
|
-
|
|
117
|
-
### Reindex after Codex changes
|
|
118
|
-
|
|
119
|
-
When the user asks TaskChef to reindex or catch up after saving more projects in
|
|
120
|
-
Codex, list native local Codex projects once and run `project list --json` once
|
|
121
|
-
before mutation. Compare exact canonical paths, then index each requested
|
|
122
|
-
eligible Codex project that is missing from TaskChef by following the
|
|
123
|
-
appropriate path above, sharing the batch verification instead of relisting
|
|
124
|
-
after each write. After all additions, run `project list --json` once more and
|
|
125
|
-
verify every intended canonical path and its routing metadata before reporting
|
|
126
|
-
the index as current.
|
|
127
|
-
|
|
128
|
-
Do not call `project add` for a path already in the TaskChef index; it rejects
|
|
129
|
-
duplicate paths and must not be presented as a metadata refresh. Preserve
|
|
130
|
-
existing curated entries, and do not remove entries merely because they are
|
|
131
|
-
absent from the current Codex list. Refreshing or removing an existing entry
|
|
132
|
-
requires an explicit user request and the project-management workflows below.
|
|
133
|
-
|
|
134
|
-
## Manage the project index
|
|
135
|
-
|
|
136
|
-
1. Bulk import with `project import <file|-> --json`. Input is a JSON array of
|
|
137
|
-
objects containing `path` plus optional `name`, `description`, and
|
|
138
|
-
`githubRepos`, which is always a JSON array of GitHub repository URLs. Before
|
|
139
|
-
importing, list native local Codex projects once, canonicalize every input
|
|
140
|
-
path, and require an exact local-project match for every entry. Reject or
|
|
141
|
-
report every unmatched path instead of indexing it. Import merges by
|
|
142
|
-
canonical path, preserves an existing name or description when omitted, and
|
|
143
|
-
unions existing and imported repository lists without duplicates. Use
|
|
144
|
-
`--replace` only when the user explicitly requests replacement. Run
|
|
145
|
-
`project list --json` afterward and verify every imported entry.
|
|
146
|
-
2. Inspect indexed projects with `project list --json`. Remove by name with
|
|
147
|
-
`project remove`. Existing task entries keep their project snapshots.
|
|
148
|
-
|
|
149
|
-
Example managed-workspace import entry:
|
|
150
|
-
|
|
151
|
-
```json
|
|
152
|
-
{
|
|
153
|
-
"name": "skills-workspace",
|
|
154
|
-
"path": "/workspace/skills-workspace",
|
|
155
|
-
"githubRepos": [
|
|
156
|
-
"https://github.com/example/skill-one",
|
|
157
|
-
"https://github.com/example/skill-two"
|
|
158
|
-
],
|
|
159
|
-
"description": "Manages the listed child skill repositories."
|
|
160
|
-
}
|
|
161
|
-
```
|
|
162
|
-
|
|
163
|
-
TaskChef accepts configuration schema version 2 only. Its optional exact
|
|
164
|
-
`dashboard` object contains boolean `autostart`; absence means enabled and
|
|
165
|
-
`false` opts out of MCP-lifecycle dashboard startup without disabling manual
|
|
166
|
-
`$taskchef-dashboard` recovery. `githubRepos` is always an array; unsupported
|
|
167
|
-
configuration is rejected without being rewritten.
|
|
55
|
+
For adding, importing, removing, listing, or reindexing projects, read
|
|
56
|
+
[project index](references/project-index.md). Preserve exact canonical local
|
|
57
|
+
Codex project identity and existing curated entries; opening a folder is not
|
|
58
|
+
proof of registration. Completion requires verifying the intended index entry.
|
|
@@ -0,0 +1,119 @@
|
|
|
1
|
+
# Project index operations
|
|
2
|
+
|
|
3
|
+
Resolve the plugin root and use its CLI as described in SKILL.md.
|
|
4
|
+
|
|
5
|
+
## Index Codex projects
|
|
6
|
+
|
|
7
|
+
TaskChef's project index is the local list of Codex projects available for
|
|
8
|
+
delegation. It stores canonical paths and routing metadata such as curated
|
|
9
|
+
names, descriptions, Git status, and GitHub repositories. It does not index
|
|
10
|
+
repository contents or create a second kind of project.
|
|
11
|
+
|
|
12
|
+
Index only Codex projects local to the TaskChef workspace's execution host.
|
|
13
|
+
Remote connection projects are outside the v1 contract. Never index the
|
|
14
|
+
TaskChef dispatcher workspace or a directory containing it; the dispatcher is
|
|
15
|
+
the inbox, while indexed Codex projects own delegated work.
|
|
16
|
+
|
|
17
|
+
### Existing Codex project
|
|
18
|
+
|
|
19
|
+
1. List native local Codex projects once. Resolve the requested existing folder
|
|
20
|
+
with `realpath` and require an exact canonical-path match in that list. A
|
|
21
|
+
similar name, a parent or child directory, and a remote connection project
|
|
22
|
+
are not matches.
|
|
23
|
+
2. Index the exact path with the existing `project add <canonical-path> --name
|
|
24
|
+
<curated-name> --description <curated-description> --json` CLI workflow.
|
|
25
|
+
Despite the command's historical `add` name, this writes one TaskChef index
|
|
26
|
+
entry for an existing Codex project. The CLI detects Git status, the exact
|
|
27
|
+
Git root, and a canonical GitHub `origin` when no repository option is
|
|
28
|
+
supplied. Repeated `--github-repo <canonical-url>` arguments replace that
|
|
29
|
+
detection and form the complete advertised repository list, so repeat the
|
|
30
|
+
origin explicitly when it should remain routable. Use `--no-github` when the
|
|
31
|
+
user intentionally wants an empty list.
|
|
32
|
+
3. Run `project list --json` and require one indexed entry with the exact
|
|
33
|
+
canonical path and intended routing metadata. Only then report that the
|
|
34
|
+
Codex project is ready for delegation through TaskChef.
|
|
35
|
+
|
|
36
|
+
### New or not-yet-saved Codex folder
|
|
37
|
+
|
|
38
|
+
1. Create the folder only when the user explicitly asked to create it. Preserve
|
|
39
|
+
unrelated existing contents. Do not initialize Git unless requested or
|
|
40
|
+
clearly required by the user's broader task. Resolve the resulting existing
|
|
41
|
+
folder with `realpath`.
|
|
42
|
+
2. Register or open that exact canonical folder with the supported
|
|
43
|
+
`<validated-codex-cli> app <canonical-path>` mechanism. Reuse a validated CLI
|
|
44
|
+
path supplied by the current Codex Desktop environment when available. Use
|
|
45
|
+
the same resolver contract as `workspace init --register-codex` otherwise:
|
|
46
|
+
an explicit `--codex-cli` path takes precedence over `TASKCHEF_CODEX_CLI`;
|
|
47
|
+
each must resolve to an executable that passes `app --help`. Without an
|
|
48
|
+
override, inspect `codex` executables from `PATH`, prefer a validated
|
|
49
|
+
candidate whose path contains `Contents/Resources`, and otherwise validate
|
|
50
|
+
only the first executable `codex` in PATH order. Never assume an arbitrary
|
|
51
|
+
shell `codex`, invoke `codex add`, or hard-code an application bundle path.
|
|
52
|
+
3. Re-list native local Codex projects and require an exact canonical-path
|
|
53
|
+
match. Opening is a request, not proof that Codex saved the project. If the
|
|
54
|
+
exact match is absent, report that the folder was opened or registration was
|
|
55
|
+
requested but Codex registration remains unverified; do not index it in
|
|
56
|
+
TaskChef or call it delegation-ready.
|
|
57
|
+
4. After Codex verification, index the project as in the existing-project path.
|
|
58
|
+
Run `project list --json` and verify the exact TaskChef index entry. Report
|
|
59
|
+
delegation readiness only after both the native Codex match and TaskChef
|
|
60
|
+
indexing are verified.
|
|
61
|
+
|
|
62
|
+
For a managed `*-workspace` Codex project, advertise every relevant child or
|
|
63
|
+
subrepository with repeated `--github-repo <canonical-github-url>` arguments,
|
|
64
|
+
including the workspace repository itself when it can own issue or pull-request
|
|
65
|
+
links. These explicit values are the complete list; automatic origin detection
|
|
66
|
+
does not supplement them. This lets TaskChef route each canonical GitHub URL to
|
|
67
|
+
the correct workspace rather than guessing from the folder name.
|
|
68
|
+
|
|
69
|
+
### Reindex after Codex changes
|
|
70
|
+
|
|
71
|
+
When the user asks TaskChef to reindex or catch up after saving more projects in
|
|
72
|
+
Codex, list native local Codex projects once and run `project list --json` once
|
|
73
|
+
before mutation. Compare exact canonical paths, then index each requested
|
|
74
|
+
eligible Codex project that is missing from TaskChef by following the
|
|
75
|
+
appropriate path above, sharing the batch verification instead of relisting
|
|
76
|
+
after each write. After all additions, run `project list --json` once more and
|
|
77
|
+
verify every intended canonical path and its routing metadata before reporting
|
|
78
|
+
the index as current.
|
|
79
|
+
|
|
80
|
+
Do not call `project add` for a path already in the TaskChef index; it rejects
|
|
81
|
+
duplicate paths and must not be presented as a metadata refresh. Preserve
|
|
82
|
+
existing curated entries, and do not remove entries merely because they are
|
|
83
|
+
absent from the current Codex list. Refreshing or removing an existing entry
|
|
84
|
+
requires an explicit user request and the project-management workflows below.
|
|
85
|
+
|
|
86
|
+
## Manage the project index
|
|
87
|
+
|
|
88
|
+
1. Bulk import with `project import <file|-> --json`. Input is a JSON array of
|
|
89
|
+
objects containing `path` plus optional `name`, `description`, and
|
|
90
|
+
`githubRepos`, which is always a JSON array of GitHub repository URLs. Before
|
|
91
|
+
importing, list native local Codex projects once, canonicalize every input
|
|
92
|
+
path, and require an exact local-project match for every entry. Reject or
|
|
93
|
+
report every unmatched path instead of indexing it. Import merges by
|
|
94
|
+
canonical path, preserves an existing name or description when omitted, and
|
|
95
|
+
unions existing and imported repository lists without duplicates. Use
|
|
96
|
+
`--replace` only when the user explicitly requests replacement. Run
|
|
97
|
+
`project list --json` afterward and verify every imported entry.
|
|
98
|
+
2. Inspect indexed projects with `project list --json`. Remove by name with
|
|
99
|
+
`project remove`. Existing task entries keep their project snapshots.
|
|
100
|
+
|
|
101
|
+
Example managed-workspace import entry:
|
|
102
|
+
|
|
103
|
+
```json
|
|
104
|
+
{
|
|
105
|
+
"name": "skills-workspace",
|
|
106
|
+
"path": "/workspace/skills-workspace",
|
|
107
|
+
"githubRepos": [
|
|
108
|
+
"https://github.com/example/skill-one",
|
|
109
|
+
"https://github.com/example/skill-two"
|
|
110
|
+
],
|
|
111
|
+
"description": "Manages the listed child skill repositories."
|
|
112
|
+
}
|
|
113
|
+
```
|
|
114
|
+
|
|
115
|
+
TaskChef accepts configuration schema version 2 only. Its optional exact
|
|
116
|
+
`dashboard` object contains boolean `autostart`; absence means enabled and
|
|
117
|
+
`false` opts out of MCP-lifecycle dashboard startup without disabling manual
|
|
118
|
+
`$taskchef-dashboard` recovery. `githubRepos` is always an array; unsupported
|
|
119
|
+
configuration is rejected without being rewritten.
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: taskchef-copilot
|
|
3
|
-
description: "Explain
|
|
3
|
+
description: "Explain TaskChef outcomes from cached briefs or continue an explicitly selected assignment in its existing task. Handles historical $taskchef-report requests; dashboard monitoring is separate."
|
|
4
4
|
---
|
|
5
5
|
|
|
6
6
|
# TaskChef Copilot
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: taskchef-delegate
|
|
3
|
-
description: "Dispatch
|
|
3
|
+
description: "Dispatch work received in the canonical TaskChef workspace into Codex tasks. Elsewhere, use only for explicit delegation of separate work; an existing executor keeps its assignment."
|
|
4
4
|
---
|
|
5
5
|
|
|
6
6
|
# TaskChef Delegate
|