@officexapp/vidfarm-devcli 0.21.59 → 0.21.61

package/marketplace.md

@@ -269,7 +269,7 @@ Read `private_note` on its own and you know where you stand:
 
 **Use `not_selected` for a pass on an inbound offer.** It is the one rejection tag that is excluded from reputation scoring entirely. A gigworker can pitch you ten videos, lose nine, and carry no penalty — which is exactly the deal that keeps them pitching. Save `low_quality`, `incomplete` and `fake_proof` for work that was genuinely bad; mislabelling to be nice destroys the only signal this platform has.
 
-**Review promptly. Silence is approval.** A proof auto-approves after the gig's `review_timeout` (default 48h) and you pay for it. If you disappear for a week you will pay for everything that arrived.
+**Review promptly. Silence is NOT approval here.** Both vidfarm vending machines run at `review_timeout: -1`, manual review: no proof auto-approves, and nothing is paid until you approve it. A countdown that pays for you exists on Dollar Platoon generally, but not on these two. The cost of silence is the other one — a gigworker who is never answered is left holding finished work and stops sending it.
 
 In the browser the same job is one swipe deck: `https://vidfarm.cc/marketplace/inbound/swipe`. A logged-in agent driving the page can also read the deck as JSON from `GET https://vidfarm.cc/marketplace/buyer/proofs?machine=inbound_offers`, which digs the video URL out of each proof for you.
 
@@ -374,6 +374,52 @@ vidfarm gigs ring-bell --title "Acme wants 7 short-form ads this week" \
 
 Add `--json` to any of them for a machine-readable answer. `--body <file.json>` sends a whole task payload you built elsewhere. `vidfarm gigs help` lists every flag.
 
+### Let clippers name the price — the bid auction
+
+`add-task` sets your price and the first free gigworker takes it. Sometimes you would rather ask the
+market what a job is worth — especially for a one-off that does not fit the machine's flat rate.
+
+A **bid request** is one task published `view_only`, so nobody can claim it. Clippers post their
+price in its comment thread, you award one, and that **same task** flips to `reserved` for them. One
+record carries the whole lifecycle, so the winner reads the entire negotiation on the job they are
+about to do.
+
+```bash
+vidfarm gigs request-bids --task "30s UGC recaption for a plumbing business" \
+  --opening '$0.10' --reference "template_019fd6b0…" --bell
+# → posts a view_only task at price TBD and prints a share link:
+#   https://dollarplatoon.com/claim/GIG_01N…/TASK_01M…?invite=<token>
+
+vidfarm gigs bids TASK_01M…                       # who bid, and what they asked
+vidfarm gigs award TASK_01M… --bid TCOMMENT_01M…  # reserve it for them, privately
+vidfarm gigs approve PRF_01H… --amount 8.00       # pay what you actually agreed
+```
+
+| Flag | |
+|---|---|
+| `--sealed` | Each clipper reads only their own thread. Default is open, so bidders see each other. |
+| `--bell` | Broadcast it to the vidfarm feed. **Off by default** — the task waits quietly in the queue. |
+| `--opening` | Where the auction starts. Default `$0.10`. |
+| `--reference` | A template id the bidders should match. |
+
+**The share link carries a gig invite, and that is the point.** DollarPlatoon's plain
+`/task/:gig/:id` page is members-only — a clipper who has never joined sees the gig's join link
+*instead of* your task, with no idea what they were invited to. The `/claim/…?invite=<token>` link
+this command prints turns "you have not joined" into "you are invited", and joining returns them to
+your task. A view-only task simply renders without the Accept button, so the page is the brief plus
+the comment thread: **they join and bid on one page.** Once you award it, that same URL grows the
+Accept button for the winner.
+
+⚠️ **A bid task stays priced `TBD` on purpose.** The deal is plain text in the thread, because real
+arrangements ("$5 now $5 on completion", "$12 for three") do not fit a single number. You name the
+agreed amount once, at approval, with `--amount`. **TBD is not $0** — approve a TBD proof without
+`--amount` and it silently pays the machine's base rate, so an $8 bid pays $0.25 and the price locks
+with no way back.
+
+The same flow exists over REST for a logged-in browser session:
+`POST /marketplace/buyer/request-template` (from a template in `/discover`),
+`GET /marketplace/buyer/bids/:gigId/:taskId`, and `POST /marketplace/buyer/award-bid`.
+
 **`add-task` has no flag for `format_harness` or `reference_template_id` — use `--body`.** Those two
 fields are the ones that decide what a weak-model clipper hands back, so do not drop them just
 because there is no flag:
@@ -586,6 +632,26 @@ vidfarm clipper-run mode quick-interactive    # save the answer into CLIPPER/run
 **Quick interactive and full auto + batch review are the two that get used.** Full interactive is the
 rescue mode for a weak model on an unfamiliar buyer; auto-submit is the narrow opt-in.
 
+### Then ask the second question: the clipper dashboard (recommended)
+
+**Three of the four modes stop to make a human WATCH A VIDEO, and a terminal cannot play one.** So
+offer the clipper dashboard in the same breath as the run mode, and expect a yes:
+
+```bash
+vidfarm dashboard                 # a localhost page over the same CLIPPER/ folder — no key, no network
+```
+
+It is the review queue as one page: the cut **playing** and seekable, the buyer's brief rendered
+beside it, the checks as tickable boxes whose unticked items pre-fill the rejection note, the
+shortlist candidates playing side by side (`1`/`2`/`3` to pick), `A`/`C`/`D` to answer, and what is
+submitted and still owed. Every button calls the same `clipper-run` verb, so the page and the
+terminal can never disagree — use both in one session if you like.
+
+Record the answer in `MISSION.md` as `dashboard: yes | no`, and never make it a dependency: a
+gigworker who says no, closes the tab or works over SSH loses nothing. `REVIEW_QUEUE.md`,
+`vidfarm clipper-run review` and the `gate` rail are unchanged. Full section:
+`https://vidfarm.cc/agentic-clipper.md` § 3⅘.
+
 **The template pick is the highest-leverage human moment in the whole loop, which is why three of the
 four modes put a stop there.** A weak model told to author a format from prose hands back something a
 buyer rejects; the same model handed a *decomposed template to adapt* hands back something they keep

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@officexapp/vidfarm-devcli",
-  "version": "0.21.59",
+  "version": "0.21.61",
   "description": "Local bridge for the Vidfarm Trackpad Editor. `vidfarm serve <template_id>` boots the FULL editor on localhost (disk-backed records/storage, free in-process render); edit composition.html on disk (Claude Code, Codex, etc.) and the browser live-morphs it.",
   "type": "module",
   "bin": {
@@ -16,6 +16,7 @@
     "dist/src/devcli/captions.js",
     "dist/src/devcli/clip-store.js",
     "dist/src/devcli/clips.js",
+    "dist/src/devcli/clipper-panel.js",
     "dist/src/devcli/clipper-run.js",
     "dist/src/devcli/composition-edit.js",
     "dist/src/devcli/consult.js",
@@ -116,6 +117,7 @@
     "test:qa": "node --import tsx --test test/qa-check.test.ts",
     "test:engine-globals": "node --import tsx --test test/engine-globals.test.ts",
     "test:clipper-run": "node --import tsx --test test/clipper-run.test.ts",
+    "test:clipper-panel": "node --import tsx --test test/clipper-panel.test.ts",
     "test:proof-verify": "node --import tsx --test test/proof-verify.test.ts",
     "test:gigs-lifecycle": "node --import tsx --test test/gigs-proof-lifecycle.test.ts",
     "test:update-check": "node --import tsx --test test/update-check.test.ts",