dsh-artel 0.1.0 → 0.2.0

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.
@@ -36,11 +36,11 @@ id changed too, so an already open Forge tab will not restore.
36
36
  ## Build a release tarball
37
37
 
38
38
  ```sh
39
- pnpm version patch # or minor / major
39
+ pnpm version minor # patch / minor / major, then commit the bump
40
40
  pnpm pack --pack-destination dist
41
41
  ```
42
42
 
43
- That produces `dist/<name>-<version>.tgz` (~63 KB) containing:
43
+ That produces `dist/<name>-<version>.tgz` containing:
44
44
 
45
45
  ```text
46
46
  package.json cordis.patch.yml icon.svg LICENSE README.md
@@ -68,9 +68,18 @@ node -e "const s = require('fs').readFileSync('/tmp/artel-check/package/lib/clie
68
68
  pnpm publish --access public
69
69
  ```
70
70
 
71
- Then tag the release and attach the same `.tgz` to the GitHub release — dsh-market can install from
72
- either an npm version or a pinned release asset, and an archive install is only ever updated through
73
- its own source.
71
+ If the CLI has no TTY (agent shells, CI-less sessions), the same publish goes through
72
+ `.tmp/publish-webauth.cjs`: it publishes the packed tarball with `libnpmpublish`, answers npm's
73
+ web-OTP challenge by opening the `authUrl` in the browser, polls `doneUrl` for the token and retries.
74
+ It reads the account token from `.tmp/npmrc` (`//registry.npmjs.org/:_authToken=…`), so run
75
+ `npm login --auth-type=web --userconfig .tmp/npmrc` once before it.
76
+
77
+ Then tag the release and attach the same `.tgz` to the GitHub release **twice**: as
78
+ `dsh-artel-<version>.tgz` (pinned, for anyone who wants an exact version) and as a version-free
79
+ `dsh-artel.tgz`. The alias keeps `releases/latest/download/dsh-artel.tgz` working across releases —
80
+ a pinned-version asset under `latest/download/` 404s the moment the next release ships, and the
81
+ catalog entry uses that stable URL. dsh-market can install from either an npm version or a pinned
82
+ release asset, and an archive install is only ever updated through its own source.
74
83
 
75
84
  ## Get listed in dsh-market
76
85
 
@@ -78,20 +87,23 @@ dsh-market is the market app, not the catalog. Its plugin list is fetched live f
78
87
  registry **[awesome-dsh-plugin](https://github.com/awesome-dsh-plugin/awesome-dsh-plugin)**, and
79
88
  installs are restricted to sources listed there.
80
89
 
81
- 1. Make the repository public, with the tarball (or npm package) installable as it stands.
82
- 2. Open a PR against `awesome-dsh-plugin/awesome-dsh-plugin` that adds **one bullet** to the
83
- category that fits — `Development & Runtime` or `Workflow & Automation` fits Artel:
84
-
85
- ```markdown
86
- - [your-name/dsh-artel](https://github.com/your-name/dsh-artel) - Runs a development task in an
87
- isolated copy of the project — one agent in Solo, three sharing one copy in Swarm — shows the
88
- diff line by line and applies only the files you approve.
89
- ```
90
-
91
- Keep it to one sentence that is literally true of the plugin: submissions are checked against the
92
- source, and the description is compared with what the code does.
93
- 3. Their CI refreshes `https://awesome-dsh-plugin.com/plugins.json` and the npm-served
94
- `dsh-plugin-catalog` index; dsh-market picks the entry up on its next open (usually within a day).
90
+ Artel is listed: its entry is `data/plugins/ksolodev__dsh-artel.yml` (category `dev`), and the
91
+ storefront reads the plugin's own `screenshots.json` from this repository.
92
+
93
+ 1. The list stores one YAML file per plugin — `data/plugins/<owner>__<repo>.yml`. The READMEs are
94
+ generated from those files, so never edit them by hand: change only your own file.
95
+ 2. Keep the description literally true — maintainers compare it with the code:
96
+ `url`, `name`, `category`, a one-sentence `description.en` (+ `description.zh`, optional), and
97
+ optionally `tarball:` (an https `.tgz` on GitHub Releases) and `icon:` (a GitHub-hosted **raster**
98
+ image; SVG is refused).
99
+ 3. Point `tarball:` at the version-free asset, so it never rots:
100
+ `https://github.com/ksolodev/dsh-artel/releases/latest/download/dsh-artel.tgz`.
101
+ 4. Open a PR that touches only that file, and state what changed in the release — a version bump, the
102
+ new tarball and a corrected description go in the same PR.
103
+ 5. Their CI refreshes `https://awesome-dsh-plugin.com/index.json` (and the npm-served
104
+ `dsh-plugin-catalog` index), and dsh-market picks the entry up on its next open (usually within a
105
+ day). The npm ↔ repo link is derived from the package's `repository` field — do not hand-write an
106
+ `npm:` key.
95
107
 
96
108
  Listing criteria the plugin already meets: it installs with `dsh plugin add`, it declares a
97
109
  `dsh.bundle` manifest, and it works without side channels (the Host API is loopback-only and every
@@ -114,17 +126,24 @@ the client boot graph).
114
126
  ## Release checklist
115
127
 
116
128
  - [ ] `node --test test/*.test.js` — all tests green.
117
- - [ ] `pnpm pack` and extract the tarball; `lib/index.js` and `lib/client.js` parse from the package.
118
- - [ ] Install that tarball into a scratch profile, restart the host, open a chat, click **Artel** in
119
- the session header: the page renders, the **Начало/Start** guide lists an Artel tile.
120
- - [ ] Solo run on a scratch project: feed streams, diff renders, Apply writes exactly the reviewed
121
- files, Discard deletes the copy.
129
+ - [ ] Version bumped in `package.json`, `lib/index.js` and the `CLIENT_VERSION` in `lib/client.js`;
130
+ `CHANGELOG.md` has a dated section for the new version.
131
+ - [ ] `pnpm pack` and extract the tarball; `lib/index.js` and `lib/client.js` parse from the package
132
+ and `import()` of `lib/index.js` exposes `apply`.
133
+ - [ ] Install that tarball into a scratch profile, restart the host, open a chat and click **Artel**
134
+ in the composer tool row (next to **+**): the panel opens over the chat, the **Sessions** rail
135
+ lists the previous runs and **+ New Artel** shows the new-run form.
136
+ - [ ] Solo run on a scratch project: full agent replies stream into the feed, the changes card lists
137
+ the files, the per-file diff renders, **Apply** writes exactly those files and deletes the copy.
122
138
  - [ ] Swarm run on a scratch project: the plan turn lists owners, agents that message each other show
123
139
  up in the feed as `Agent <name> sent a message:`, all agents edit their own files, and the
124
140
  combined diff applies in one go.
125
- - [ ] Apply conflict check: edit a file in the project while a run waits, then Apply — Artel reports
126
- that file as skipped and leaves your edit alone.
127
- - [ ] UI language switch (en / ru) and the plugin card title/description/icon in the plugin manager.
141
+ - [ ] Apply conflict check: edit a file in the project while a run waits, then Apply — Artel rejects
142
+ the apply and reports the conflicting file, leaving your edit alone.
143
+ - [ ] UI language switch (en / ru / zh) and the plugin card title/description/icon in the plugin
144
+ manager.
145
+ - [ ] `npm publish` (or the web-OTP driver), GitHub release with both tarball assets, and the
146
+ awesome-dsh-plugin entry updated (`tarball:` + `description`).
128
147
  - [ ] `README.md` and `docs/guide*.md` describe the current behavior, including the limitations
129
148
  (Swarm messaging needs the lead session to stay live, interrupted runs after a restart, and the
130
149
  fallback for profiles without the subagent stack).