thurview 0.15.0 → 0.16.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.
- package/README.md +117 -88
- package/dist/cli.js +9 -0
- package/dist/cli.js.map +1 -1
- package/dist/queue.js +123 -0
- package/dist/queue.js.map +1 -0
- package/dist/server/server.js +3 -9
- package/dist/server/server.js.map +1 -1
- package/dist/store.js +10 -0
- package/dist/store.js.map +1 -1
- package/dist/ui/app.css +25 -0
- package/dist/ui/app.js +65 -12
- package/dist/ui/app.js.map +2 -2
- package/package.json +1 -1
- package/skills/thurview/references/lifecycle.md +21 -0
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "thurview",
|
|
3
|
-
"version": "0.
|
|
3
|
+
"version": "0.16.0",
|
|
4
4
|
"description": "Guided, evidence-anchored reviews of agent-written code. A coding agent authors the review; you read, ask, comment and decide in the browser.",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"type": "module",
|
|
@@ -131,6 +131,7 @@ ${THURVIEW_HOME:-~/.thurview}/
|
|
|
131
131
|
├── THURVIEW.md user guidance (optional)
|
|
132
132
|
├── server.json running server, if any
|
|
133
133
|
├── agents/<id>.json heartbeat of a running `wait`, removed when it ends
|
|
134
|
+
├── forge/<id>.json what the forge last said of the change request: head, state, CI, last pass posted
|
|
134
135
|
├── passes/<id>.json the submission `forge pass` wrote, for `forge submit`
|
|
135
136
|
└── reviews/<id>/
|
|
136
137
|
├── review.md you edit
|
|
@@ -145,6 +146,26 @@ ${THURVIEW_HOME:-~/.thurview}/
|
|
|
145
146
|
A failed publish leaves the last sealed revision in place. The reader can
|
|
146
147
|
switch between revisions in the browser.
|
|
147
148
|
|
|
149
|
+
## The queue
|
|
150
|
+
|
|
151
|
+
The home page lists every document, grouped by repository and ordered by whose
|
|
152
|
+
turn it is. It is read from the store on every load and never published, so it
|
|
153
|
+
cannot go stale. Whose turn, most urgent first:
|
|
154
|
+
|
|
155
|
+
| Turn | When |
|
|
156
|
+
| ------ | ------------------------------------------------------------------------- |
|
|
157
|
+
| you | a decision on a change request that no `forge submit` has posted yet |
|
|
158
|
+
| you | `awaiting-review`, pinned at the change request's head, no thread waiting |
|
|
159
|
+
| agent | the change request's head moved past the pin: `scaffold --update` |
|
|
160
|
+
| agent | a thread `needsAgent`, or `awaiting-agent-updates` |
|
|
161
|
+
| agent | `draft`: nothing published yet |
|
|
162
|
+
| nobody | `accepted`, `closed`, dismissed, or the change request merged or closed |
|
|
163
|
+
|
|
164
|
+
The forge columns come from `forge/<id>.json`, which `scaffold --pr`, `forge
|
|
165
|
+
status` and `forge submit` write for the document bound to that change request.
|
|
166
|
+
Run `thurview forge status --review <id>` to refresh a row; until something
|
|
167
|
+
has, the row says the forge was not read.
|
|
168
|
+
|
|
148
169
|
## wait
|
|
149
170
|
|
|
150
171
|
`thurview wait --review <id> [--timeout <s>]` polls the review and returns
|