thurview 0.18.0 → 0.19.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/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "thurview",
3
- "version": "0.18.0",
3
+ "version": "0.19.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",
@@ -331,6 +331,25 @@ Then publish again (step 7), tell the user what changed since the previous
331
331
  revision in a line or two, and wait again (step 9). A republish requires zero
332
332
  open submitted comment threads; questions do not block.
333
333
 
334
+ ## Sharing a copy that needs no server
335
+
336
+ When the user asks to share, export or publish the rendered page somewhere -
337
+ a file to send, a Pages site, a static host - write it from the published
338
+ revision:
339
+
340
+ ```sh
341
+ thurview export --review <id> --out <file.html | folder> # --no-threads
342
+ ```
343
+
344
+ It writes one self-contained HTML file (a folder gets `index.html`): the same
345
+ page, read only, with every snippet, diagram and diff resolved at the pins,
346
+ fetching nothing, naming no server and no local path. The reader's sent
347
+ threads and decisions appear as static notes; their unsent drafts never do.
348
+ Pass `--no-threads` when the copy goes beyond the people in the conversation.
349
+ It refuses a document with no published revision, and a copy does not update:
350
+ export again after each publish. Committing or uploading the file is the
351
+ user's step - name where it was written and leave it there unless asked.
352
+
334
353
  ## Explaining a codebase rather than a change
335
354
 
336
355
  Do not pin the same commit as base and head to fake it. That leaves a review
@@ -230,6 +230,10 @@ reader sees above the document, and `published.url` is the page.
230
230
  thurview open --review <id>
231
231
  ```
232
232
 
233
+ To share it beyond the browser, `thurview export --review <id> --out <path>`
234
+ writes a static, read-only copy - see the `thurview` skill's **Sharing a copy
235
+ that needs no server**.
236
+
233
237
  ### 7. Hand over
234
238
 
235
239
  In a few lines, and nothing more: the `url`; the commit and scope it argues
@@ -219,6 +219,9 @@ the code" - not a finding.
219
219
  7. `thurview open --review <id>`, then `thurview wait --review <id>`. The loop,
220
220
  the statuses and the thread rules are identical to a review; see
221
221
  **Lifecycle**.
222
+ 8. To share it beyond the browser, `thurview export --review <id> --out <path>`
223
+ writes a static, read-only copy - see the `thurview` skill's **Sharing a
224
+ copy that needs no server**.
222
225
 
223
226
  ## Hand over
224
227