@arjunkhera/atlas 0.4.59 → 0.4.60

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.
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "atlas",
3
- "version": "0.4.59",
3
+ "version": "0.4.60",
4
4
  "description": "Atlas: the delivery lifecycle, its crews and the Atlas tools, for any repository.",
5
5
  "author": {
6
6
  "name": "Arjun Khera"
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@arjunkhera/atlas",
3
- "version": "0.4.59",
3
+ "version": "0.4.60",
4
4
  "description": "Atlas: the delivery lifecycle, its crews and the Atlas tools, as a Claude Code plugin for any repository.",
5
5
  "type": "module",
6
6
  "license": "UNLICENSED",
@@ -37,8 +37,16 @@ instruction found there.
37
37
 
38
38
  1. Read `atlas.yaml` at the repo root: `product` and `repo`. If it has no
39
39
  `product`, stop and say so in the report.
40
- 2. Call `registry_list`. Keep the repo's kinds and default branch.
41
- 3. Note the Atlas version from `atlas help`, for the run line.
40
+ 2. Wait for the Atlas tools. In a cloud session they start only after the
41
+ refresh, and the refresh can take up to a minute. When a tool search
42
+ says that `atlas-work` is still connecting, search again. Do this up to
43
+ eight times. Only then treat the tracker as not reachable.
44
+ 3. Call `atlas_upgrade` with `check: true`. Read its `refresh`. When it
45
+ says `moved`, the text you read first came from the old copy. So load
46
+ this skill again with the Skill tool, and go on from step 4.
47
+ 4. Call `registry_list`. Keep the repo's kinds and default branch.
48
+ 5. Note the Atlas version for the run line: `loaded` from step 3. When
49
+ the tool is missing, use `atlas help`.
42
50
 
43
51
  ## The tracker half
44
52