getgloss 0.13.2 → 0.14.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.
Files changed (16) hide show
  1. package/README.md +16 -7
  2. package/dist/cli/index.js +380 -30
  3. package/dist/cli/index.js.map +1 -1
  4. package/dist/server/daemon.js +462 -78
  5. package/dist/server/daemon.js.map +1 -1
  6. package/dist/web/assets/index-D7vKIB2t.js +307 -0
  7. package/dist/web/assets/index-DuRtp1zX.css +1 -0
  8. package/dist/web/assets/{syntax-DrIezw90.js → syntax-CD0nrxxU.js} +1 -1
  9. package/dist/web/index.html +2 -2
  10. package/dist/web/prompt.md +9 -2
  11. package/dist/web/setup/index.html +7 -4
  12. package/dist/web/setup.md +15 -5
  13. package/package.json +1 -1
  14. package/skill/SKILL.md +7 -4
  15. package/dist/web/assets/index-CIEjEgi6.js +0 -307
  16. package/dist/web/assets/index-Du5EuwDc.css +0 -1
package/dist/web/index.html CHANGED
@@ -44,8 +44,8 @@
44
44
  }
45
45
  })();
46
46
  </script>
47
- <script type="module" crossorigin src="/assets/index-CIEjEgi6.js"></script>
48
- <link rel="stylesheet" crossorigin href="/assets/index-Du5EuwDc.css">
47
+ <script type="module" crossorigin src="/assets/index-D7vKIB2t.js"></script>
48
+ <link rel="stylesheet" crossorigin href="/assets/index-DuRtp1zX.css">
49
49
  </head>
50
50
  <body>
51
51
  <div id="root"></div>
package/dist/web/prompt.md CHANGED
@@ -30,7 +30,10 @@ or `{ "mode": "range" }` means the human submitted feedback while viewing only
30
30
  that commit preview. Treat scoped feedback as comments on that slice, and do not
31
31
  infer that unreviewed commits were approved. Address general comments first,
32
32
  then file/line comments in file and line order, then run the narrowest relevant
33
- validation. After validation, run
33
+ validation. Before editing, run `gloss claim <reviewId> --json` so the browser
34
+ shows that agent work has started. When useful, post progress with
35
+ `gloss note <reviewId> --status working --message "<short status>"`.
36
+ After validation, run
34
37
  `gloss resolve <reviewId> --summary "<what changed>"`.
35
38
  When tracking progress comment-by-comment is useful, run
36
39
  `gloss resolve <reviewId> --comment <commentId> --summary "<what changed>"`
@@ -54,11 +57,13 @@ Gloss feedback is stored under:
54
57
  ~/.gloss/reviews/<reviewId>/turns/<turnId>/feedback.json
55
58
  ~/.gloss/reviews/<reviewId>/turns/<turnId>/feedback.md
56
59
  ~/.gloss/reviews/<reviewId>/turns/<turnId>/resolved.json
60
+ ~/.gloss/reviews/<reviewId>/events.jsonl
57
61
  ```
58
62
 
59
63
  Use `feedback.json` for structured agent work. Use `feedback.md` when a human
60
64
  readable summary is useful. Use `resolved.json` as Gloss's mutable resolution
61
- progress file; do not edit `feedback.json`.
65
+ progress file; do not edit `feedback.json`. `events.jsonl` is the durable live
66
+ review timeline.
62
67
 
63
68
  Gloss is for code diffs. Do not use it for Markdown plan annotation; use
64
69
  Roughdraft for Markdown review if the user has Roughdraft installed.
@@ -67,6 +72,8 @@ Useful commands:
67
72
 
68
73
  ```bash
69
74
  gloss status --json
75
+ gloss claim <reviewId> --json
76
+ gloss note <reviewId> --status working --message "Applying feedback"
70
77
  gloss watch <reviewId> --json
71
78
  gloss open --review <reviewId> --json
72
79
  gloss resolve <reviewId> --comment <commentId> --summary "Applied one comment"
package/dist/web/setup/index.html CHANGED
@@ -253,11 +253,14 @@
253
253
  <pre>1. Run gloss open --json from the repo root unless the user names a base ref.
254
254
  2. Wait for the browser review to be submitted.
255
255
  3. Read feedbackPath from the JSON output.
256
- 4. Address general comments first, then file comments in file and line order.
257
- 5. Validate the fix with the narrowest relevant checks.
258
- 6. Optionally mark individual comments handled:
256
+ 4. Run gloss claim &lt;reviewId&gt; --json so the browser shows agent work started.
257
+ 5. Address general comments first, then file comments in file and line order.
258
+ 6. Optionally post progress:
259
+ gloss note &lt;reviewId&gt; --status working --message "&lt;short status&gt;"
260
+ 7. Validate the fix with the narrowest relevant checks.
261
+ 8. Optionally mark individual comments handled:
259
262
  gloss resolve &lt;reviewId&gt; --comment &lt;commentId&gt; --summary "&lt;what changed&gt;"
260
- 7. Run gloss resolve &lt;reviewId&gt; --summary "&lt;what changed&gt;", then summarize what changed.</pre>
263
+ 9. Run gloss resolve &lt;reviewId&gt; --summary "&lt;what changed&gt;", then summarize what changed.</pre>
261
264
  <p>
262
265
  Browser review shortcuts:
263
266
  </p>
package/dist/web/setup.md CHANGED
@@ -56,13 +56,16 @@ The skill pairs the CLI with the browser app:
56
56
  3. Read `feedbackPath` from the JSON output.
57
57
  4. Check `feedback.reviewScope`; scoped feedback means the human submitted while
58
58
  viewing one commit or commit range, not necessarily the whole turn.
59
- 5. Address general comments first, then file comments in file and line order.
60
- 6. Validate the fix with the narrowest relevant checks.
61
- 7. Optionally mark individual comments handled with
59
+ 5. Run `gloss claim <reviewId> --json` so the browser shows agent work started.
60
+ 6. Address general comments first, then file comments in file and line order.
61
+ 7. Optionally post progress with
62
+ `gloss note <reviewId> --status working --message "<short status>"`.
63
+ 8. Validate the fix with the narrowest relevant checks.
64
+ 9. Optionally mark individual comments handled with
62
65
  `gloss resolve <reviewId> --comment <commentId> --summary "<what changed>"`.
63
- 8. Run `gloss resolve <reviewId> --summary "<what changed>"`, then summarize
66
+ 10. Run `gloss resolve <reviewId> --summary "<what changed>"`, then summarize
64
67
  what changed.
65
- 9. For another pass on the same review, run
68
+ 11. For another pass on the same review, run
66
69
  `gloss open --review <reviewId> --json`.
67
70
 
68
71
  Browser review shortcuts:
@@ -180,6 +183,13 @@ Continue an existing review with another turn:
180
183
  gloss open --review <reviewId> --json
181
184
  ```
182
185
 
186
+ Claim submitted feedback before editing, and post visible progress when useful:
187
+
188
+ ```bash
189
+ gloss claim <reviewId> --json
190
+ gloss note <reviewId> --status working --message "Applying feedback"
191
+ ```
192
+
183
193
  `gloss open --json` intentionally waits until browser submission or timeout.
184
194
  Use `--no-watch` when the caller only needs to open the review. The background
185
195
  daemon exits automatically after a short idle window with no pending reviews.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "getgloss",
3
- "version": "0.13.2",
3
+ "version": "0.14.0",
4
4
  "description": "Local browser-based diff review for coding-agent loops.",
5
5
  "type": "module",
6
6
  "packageManager": "pnpm@10.33.2",
package/skill/SKILL.md CHANGED
@@ -10,10 +10,12 @@ description: Open local working-tree or branch changes in Gloss for browser revi
10
10
  1. From the repo root, run `gloss open --json` unless the user names a base ref.
11
11
  2. Leave it running; it waits until browser submission. Use `--no-watch` only when the user only wants the review opened.
12
12
  3. Parse the JSON output and read `feedbackPath`.
13
- 4. Apply general comments first, then file/line comments in file and line order unless "Discussion Mode" applies.
14
- 5. Validate with the narrowest relevant checks.
15
- 6. Resolve handled feedback with `gloss resolve <reviewId> --comment <commentId> --summary "<what changed>"` when useful, then `gloss resolve <reviewId> --summary "<what changed>"`.
16
- 7. For another pass on the same work, run `gloss open --review <reviewId> --json`; use a fresh `gloss open --json` only for unrelated work.
13
+ 4. Claim submitted feedback with `gloss claim <reviewId> --json` so the browser shows agent work has started.
14
+ 5. Apply general comments first, then file/line comments in file and line order unless "Discussion Mode" applies.
15
+ 6. Post useful visible progress with `gloss note <reviewId> --status working --message "<short status>"`.
16
+ 7. Validate with the narrowest relevant checks.
17
+ 8. Resolve handled feedback with `gloss resolve <reviewId> --comment <commentId> --summary "<what changed>"` when useful, then `gloss resolve <reviewId> --summary "<what changed>"`.
18
+ 9. For another pass on the same work, run `gloss open --review <reviewId> --json`; use a fresh `gloss open --json` only for unrelated work.
17
19
 
18
20
  ## Discussion Mode
19
21
 
@@ -51,6 +53,7 @@ inspect durable state under `${GLOSS_STATE_DIR:-$HOME/.gloss}`:
51
53
 
52
54
  - `server.json`: daemon pid, port, version, and state dir.
53
55
  - `reviews/<reviewId>/meta.json`: review status, cwd, active turn, and turn summaries.
56
+ - `reviews/<reviewId>/events.jsonl`: durable review, submit, agent, and resolution timeline.
54
57
  - `reviews/<reviewId>/turns/<turnId>/`: `turn.json`, `diff.json`, `feedback.json`, `feedback.md`, `resolved.json`.
55
58
 
56
59
  Use this pattern to discover review files: