@colony2/c2j 0.0.84 → 0.0.85

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.
Files changed (2) hide show
  1. package/README.md +15 -9
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -106,7 +106,11 @@ its installation checks. After changing Go dependencies, update `vendorHash` in
106
106
 
107
107
  ### 1. Check current-cell resolution
108
108
 
109
- `submit` targets the current cell by default. That usually comes from `.c2j/config.yaml`, but supported project types can also be auto-detected.
109
+ `submit` targets the current cell by default. That usually comes from `.c2/config.yaml`, but supported project types can also be auto-detected.
110
+
111
+ Configuration now lives in `.c2/config.yaml`; the old `.c2j` directory is not
112
+ searched or migrated automatically. Move existing configuration and recipes to
113
+ `.c2` before running this version.
110
114
 
111
115
  Inspect the resolved config:
112
116
 
@@ -128,7 +132,7 @@ c2j init --stdout
128
132
 
129
133
  If the current directory does not resolve as a cell, either:
130
134
 
131
- - create `.c2j/config.yaml`, or
135
+ - create `.c2/config.yaml`, or
132
136
  - pass `--cell <repo-or-path>` explicitly to `submit` or `list`
133
137
 
134
138
  ### 2. Submit and run a build job
@@ -166,7 +170,7 @@ c2j run --job-id <job-id> --embed
166
170
 
167
171
  ### `c2j self`
168
172
 
169
- Shows how `c2j` resolves the current cell from `.c2j/config.yaml` or supported auto-detection.
173
+ Shows how `c2j` resolves the current cell from `.c2/config.yaml` or supported auto-detection.
170
174
 
171
175
  ```bash
172
176
  c2j self
@@ -195,7 +199,7 @@ This is mainly useful when you want to target another cell by short name and nee
195
199
 
196
200
  ### `c2j init`
197
201
 
198
- Writes a commented `.c2j/config.yaml` template and installs bundled c2j skills for Codex-compatible agents.
202
+ Writes a commented `.c2/config.yaml` template and installs bundled c2j skills for Codex-compatible agents.
199
203
 
200
204
  ```bash
201
205
  c2j init
@@ -216,7 +220,7 @@ c2j init --skills-scope user
216
220
  c2j init --skills-force
217
221
  ```
218
222
 
219
- `auto` currently installs to the project-local `.agents/skills` directory. `user` installs to `${CODEX_HOME:-$HOME/.codex}/skills`. Install metadata is recorded in `.c2j/skills-lock.yaml`.
223
+ `auto` currently installs to the project-local `.agents/skills` directory. `user` installs to `${CODEX_HOME:-$HOME/.codex}/skills`. Install metadata is recorded in `.c2/skills-lock.yaml`.
220
224
 
221
225
  You can also install the repo skills directly with the public `skills` tool:
222
226
 
@@ -234,7 +238,7 @@ Submit a build job:
234
238
  c2j submit "Implement the new endpoint" --embed
235
239
  ```
236
240
 
237
- Submissions use the name `build` through the existing recipe resolution system. At execution time, c2j first looks for `.c2j/recipes/build.yaml` in the **target cell's repository**, at its configured ref. This also applies to `--cell`; the submitting project's recipes do not override another target cell's recipes. As with other named recipes, uncommitted files are not used.
241
+ Submissions use the name `build` through the existing recipe resolution system. At execution time, c2j first looks for `.c2/recipes/build.yaml` in the **target cell's repository**, at its configured ref. This also applies to `--cell`; the submitting project's recipes do not override another target cell's recipes. As with other named recipes, uncommitted files are not used.
238
242
 
239
243
  If that recipe file is absent, c2j resolves the shared recipe instead:
240
244
 
@@ -387,7 +391,7 @@ c2j submit "Improve retry behavior" \
387
391
  - a canonical repo string
388
392
  - a clone URL
389
393
  - a local repository path
390
- - a configured short name when `.c2j/config.yaml` defines a pattern
394
+ - a configured short name when `.c2/config.yaml` defines a pattern
391
395
 
392
396
  Rules:
393
397
 
@@ -471,7 +475,7 @@ Useful flags:
471
475
  - `--recipe-file <path>` uses a local inline recipe file
472
476
  - `--case <id>` filters suite mode to selected cases
473
477
  - `--parallelism <n>` controls local case concurrency
474
- - `--out-dir <dir>` defaults to `.c2j/test-results/<timestamp>/`
478
+ - `--out-dir <dir>` defaults to `.c2/test-results/<timestamp>/`
475
479
  - passthrough cases use a disposable embedded runtime automatically
476
480
 
477
481
  ## Running Jobs
@@ -704,7 +708,7 @@ Behavior:
704
708
  Defaults:
705
709
 
706
710
  - runtime URL: `embed:///`
707
- - runtime root: `~/.c2j/embed/default`
711
+ - runtime root: `~/.c2/embed/default`
708
712
 
709
713
  Notes:
710
714
 
@@ -788,6 +792,8 @@ c2j submit "Run the requested task" \
788
792
 
789
793
  ## Related Files
790
794
 
795
+ - separate Git operations: [squash, rebase, and fast-forward-only merge](GUIDE-Git-Ops.md)
796
+
791
797
  - command entrypoint: [main.go](main.go)
792
798
  - embedded runtime notes: [embed-swf-mode-spec.md](embed-swf-mode-spec.md)
793
799
  - recipe authoring docs: [RECIPE_AUTHORING_GUIDE.md](../../recipes/guides/RECIPE_AUTHORING_GUIDE.md)
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@colony2/c2j",
3
- "version": "0.0.84",
3
+ "version": "0.0.85",
4
4
  "description": "c2j job system",
5
5
  "license": "Apache-2.0",
6
6
  "homepage": "https://github.com/colony-2/c2j",