Repository navigation
Releases
v0.27.2
0.27.2
Patch Changes
- d6755b9: Show up to 30 child rows in the board's children popover (previously 6) before truncating. The truncation line is now a keyboard-reachable "+N more" button that opens the task's detail panel scrolled to the full children list, instead of passive text. At 30 rows the popover clamps to its 50vh budget and the row list scrolls internally while the header and the affordance stay pinned.
- 0f48137: Serve the kanban board's Inter from vendored woff2 files instead of Google Fonts. The UI package now ships the font files plus the
@font-faceblock and the singleKANBAN_FONT_STACKcontract; the CLI serves the same bytes same-origin at/__vibeflow__/fonts/and the board HTML no longer references any CDN. Offline or restricted networks previously fell back to a serif face on local boards; both surfaces now resolve the same vendored face with the same stack.
v0.27.1
0.27.1
Patch Changes
- da6f964:
verify --pixelsnow settles the page before capturing: it waits fordocument.fonts.readyand two animation frames after the storage injection.animations: "disabled"freezes animation state but cannot wait for a webfont or the post-injection re-render, so under CPU load an "unchanged" page could diff 24/255 against itself and fail any--min-pixel-deltademand. Equal code now means equal pixels.
v0.27.0
0.27.0
Minor Changes
- 41b198e: Agent hooks Stage 1.5: module-adapter
.hook.mjsmode plus public authoring types. A hook may now beafter-<event>.hook.mjsexporting default a function (async OK) that receives the full envelope as its argument; a packaged loader runs it in a child process with the same 2s deadline, trust, and fail-open{instructions}/{}policy as the stdio.mjsmode. Mode is chosen by filename only — both files at one level is a configuration error with no fallback. Authoring types ship as a types-only@vibeflow-tools/cli/hookssubpath (after-only envelope union, no runtime API, no TypeScript execution). - fefd3d7: Agent hooks Stage 1: operation-owned after-hook pipeline. Every mutating command (
tasks --add/--edit/--delete/--next,verify,push,pull, plus the matching MCP tools) emits one typed after-event after its confirmed durable effect; a project, global, or shipped-default.mjshook can appendinstructionsto the result (--jsonpayloads and MCP responses carry them; human mode prints them dim on stderr). Hooks are child processes with a 2s per-invocation deadline (after = fail open), direnv-style trust for project hooks, and replace-not-merge precedence. No pre-hooks or blocking yet. - 41bf1e6: Agent hooks Stage 2: fail-closed pre-hook gates with bypass audit. Every gated invocation (
tasks --add/--edit/--delete/--next/--comment,verify,push,pull, plus the matching operation-layer paths) runs itspre-<event>.mjs(or.hook.mjsmodule) before the write with an intent payload — fields known before effects, never generated ids. The full task snapshot is immutable and agent instructions are the only replaceable surface. Timeout, non-zero exit, non-JSON output, malformed decisions, and explicit{allow:false,reason}all block with the existing refusal shape and a non-zero exit.--no-verifyskips the gate loudly (HOOK_BYPASSED notice plus a local append-only audit record; after-hooks still run), and an untrusted project pre-hook blocks while an untrusted after-hook only skips. Public authoring types gain the pre envelope/handler/result (@vibeflow-tools/cli/hooks). - f308ccf: Agent hooks Stage 4: TypeScript hook execution (
.hook.ts/.hook.mts, opt-in). A hook may now bepre/after-<event>.hook.ts(or.hook.mts) — same deterministic filename contract as.hook.mjs(no auto-detection), same project>global>defaults precedence with replace-not-merge and no-fallback conflict rules (two or more executables at one level isHOOK_CONFIG_CONFLICT). The packaged loader type-strips on import: erasable syntax only (no JSX, no tsconfig paths, no transpilation),import typefrom@vibeflow-tools/cli/hooksis erased before resolution. Node >= 22 is not a capability guarantee, so the runner probes the actual runtime (process.features.typescript): unsupported runtimes refuse loudly with the phase policy unchanged (afterHOOK_TS_UNSUPPORTEDfail-open, preHOOK_PRE_TS_UNSUPPORTEDfail-closed). Trust hashes the TypeScript source file — edits re-prompt; the hash still covers the entry file only, not its imports. Adds a verbatimdocs/hooks-examples/after/after-task.update.hook.tsexample plus editor guidance. No envelope, wire, or result-schema changes. - aac2ec6: Agent hooks v2: one hook file per TOOL instead of per internal event —
tasks.after.mjs,kanban.after.mjs,create_task.before.mjs, … covering every CLI command and all 13 MCP tools; the hook envelope isschemaVersion: 2withtool/surfaceandphase: before|after(theprevocabulary is gone), and an invocation with no durable effect narrates once withactivity: null. Shipped defaults are now read in place from the installed package (dist/hooks/defaults/, trusted, upgraded bynpm update) instead of being copied into~/.vibeflow/hooks/defaults/— that directory is obsolete. Policies are unchanged: 2 s per invocation, before fail-closed, after fail-open, stdout purity, PATH/HOME-only child env, project-hook trust,--no-verifyaudit. - ef82ca8:
vibeflow verify --pixelscaptures the task selector region as baseline/after PNG evidence (verify-baseline-pixels.png,verify-after-pixels.png) and diffs them per channel: the output carries a greppablePIXEL_DELTA=<max>/255 (<pct>% of pixels changed)line and--jsoncarriespixelDelta: {max, pct, sameSize}. Size drift is reported (sameSize: false), never diffed.--min-pixel-delta <n>(0-255, default 0 = report only) demands a visible change and failsokwhen unmet. First run bootstraps the baseline; pixel PNGs stay raw (true.png, decoded with the repo's dependency-free PNG codec — no transcode, no new deps).
Patch Changes
-
0864886: Pre-push is now affected-only: the hook derives the changed paths from the push range and runs only the suites those paths can break via an explicit path→suite map (
scripts/affected-suites.mjs), instead of unit+e2e+integration+playwright unconditionally. Unmapped paths, a shallow/unavailable base, or a force push run everything (fail closed); docs/changeset-only pushes run nothing.node scripts/affected-suites.mjs --dry-run --range <base>..<head>prints the chosen suites for review without pushing. Tickets 6fc455a3. -
ddbb6f8: After-hook envelopes now carry the confirmed task snapshot and activity object. Previously every after-hook received
task: nulland had to re-read the task store; hooks now get the written record directly (run-level events such as push, pull, and verify still carry no single task). -
37f5bd3: Agent hooks Stage 3: document the hook contract and ship two copy-in examples.
docs/agent-hooks.mddescribes the envelope both phases receive, the fail-closed pre-gate versus fail-open after-hooks,--no-verifybypass audit, stdio versus module authoring modes, replace-not-merge precedence, invocation bounds, and the trust model — each statement checkable against the hook sources.docs/hooks-examples/adds a verify-verdict webhook notifier (reads its URL from a hook-owned config file, since the hook environment carries no credentials) and a review-move instruction nudge; both were exercised verbatim through the packaged CLI. No behaviour change. -
b6ebe82: Needs-attention bell breathes a glow instead of flickering. The
attention-breatheanimation moved from the.attention-indicatorwrapper (which dimmed the whole bell to 0.45 opacity) to the bell svg itself: the amber drop-shadow swells to ~5px/0.5 alpha and fades over a slow ~3s ease-in-out cycle while the glyph stays fully opaque. Static underprefers-reduced-motion. -
eb30dfe: Needs-attention: the bell breath is now visible and the amber tint is link-exact only.
- Breath. The
attention-breatheglow was technically animating (the
computedfiltervaried) but painted a ~5% channel delta around an 11px
glyph, so owners reported "the breathing animation is still not there" for
three rounds. The peak now stacks a tight full-alpha amber ring, a wide
halo and a hotter glyph (brightness(1.35)— luminance only, no hue shift),
measured at 57% of the bell region changing / 48 max channel delta instead
of 23% / 13. Reduced motion keeps the bell static but now leaves a visible
amber glow (filter: nonemade the flag indistinguishable from a plain
glyph). - Highlight. The derived attention row used to guess its reason from the
newest surviving comment, so the amber flag row (and, before the tint fix,
the amber card) read as attached to whichever message arrived last — the
owner's "now it is random". Placement and attribution now come from the
storedattentionReasonIdalone; a record with no link is sorted at the
task's own update time and attributed to the task owner, and tints nothing.
Pinned in the browser on both surfaces: the CLI board Playwright spec
(kanban-attention-icon.test.ts) and the hosted e2e spec
(needs-attention.spec.ts) screenshot the bell at the breath's peak and
trough and require a real painted difference, then assert exactly one amber
comment — the linked agent message — with newer plain notes untinted and a
cleared link tinting nothing. - Breath. The
-
4d878c0: Cold-load needs-attention parity. A task flagged BEFORE the board opened showed a plain reason comment and no attention row — the diff-event path only records the row on live transitions. The Activity tab now derives ONE amber attention row from the current
needsAttentionstate at render (a live transition row still wins, never two rows) and marks the reason comment the flag is linked to with the same amber wash, in card detail and navigated-child contexts. -
f516a97: Flaky-test reporting: failures in
@flaky-marked specs now land in a separate bucket — printed asFLAKY (not failing the gate): …and appended to a machine-readable flake log (path + spec + worker count + timestamp) — instead of hiding inside suite output, while genuine reds still fail the gate. The spec still runs; nothing is skipped and no new@flakytags were added. Ticket f3b5058e. -
6d705f7: Hook authoring ergonomics: shipped default texts are generated as readable line-arrays (delivered bytes unchanged);
console.log/info/warn/debugis safe in all three hook modes (child-side stderr redirect — stdio preloadshook-console-guard.mjsvianode --import, module/TS get the loader-top patch) so chatter can never become an instruction; and a shipped runtime utility (readEnvelope()/reply()/log(), resolved via the runner-injectedVIBEFLOW_HOOK_RUNTIMEenv var or the@vibeflow-tools/cli/hooks/runtimesubpath) drops the hand-rolled stdin boilerplate. -
adc604d: Shrink shipped agent instruction texts (T1–T4 AFTER pass, −48% unique words, 269w shipped ×2 = 538w): claim block folds the
--nextparenthetical inline and routes blocked tasks through--set-attention --comment(flag + reason in one call); safety/comment blocks merge restated lines with em-dashes; verify ...
v0.26.0
0.26.0
Minor Changes
-
5bb9d16:
tasks --search "..."fuzzy-searches the board over title, description, comments and tags (case-insensitive, typo-tolerant; every word must match). A search returns matching children like the other filters and ranks by relevance (score, then id). In remote mode the search narrows with?q=and ranks the same way, and the MCPlist_taskstool accepts the samesearchfield — one query returns the same ids in the same order on every surface.Highlights
- Fuzzy task search via
tasks --searchand the MCP search tool (title, description, comments and tags; children included, local and online).
- Fuzzy task search via
v0.25.0
0.25.0
Minor Changes
- 4fab972: Add
get_filedownload path (mirror ofattach_file): MCPvibeflow_get_file(id, filename|fileId)returns{filename, mimeType, size, contentB64}, andvibeflow tasks --get-file <id> <name> [--out path]writes the bytes to disk. Local reads come from the task's files dir; remote mode downloads through the board's file endpoints, so agents can read attachment bytes the stripped file list never carries.
Patch Changes
- 1fc8a46: Kanban: dropping a child row onto another lane's card edge now moves it there as a root item (parent link unlinked plus status/sortKey moved), matching the column-background drop. Previously the reorder path persisted only status/sortKey, so the card appeared in the new lane while staying attached to the old parent's tree. List-view section drops use the same drag-out path.
- eddbb37: Fix CLI board
uploadFileswallowing rejected uploads: check the upload POST response status and throw with the server error detail (parity with the web adapter), so the detail panel shows the upload-error box instead of a success chip. - 87b4e97: Done lane/group now sorts most-recently-modified first: the board done column and the list-view done group order by
updatedAtdesc (falling back tocreatedAt), ignoring manual dragsortKeyorder. Other lanes keep their existing order; no pagination or cap change. - 06810fa: First-run kanban onboarding: opening a board with no tasks auto-opens settings once (localStorage
vibeflow.kanban.onboarded, never re-opens), and the review-gate defaults are now ON — a verification verdict and a comment are required on review unless explicitly opted out (requireVerifyBeforeReview: false/autoComment: falsestill win). Comment-on-review was already unconditional; the verify default is the behavior change, surfaced visibly by the auto-opened settings modal. - 1f1033b: Fix overlay paste
uploadTaskFileswallowing rejected uploads: check the upload POST response status and throw with the server error detail (parity with the boarduploadFilefix), so a failed overlay paste lands in the visible paste-error UI viapasteFailureMessageinstead of resolving as success. - 9cf68a8: MCP tool docs are now generated from code (single source of truth):
packages/cli/tool-catalog.jsonis projected frompackages/cli/src/mcp/manifest.ts(13 tools, includingget_fileandpull), the root README tool table lists all 13, andpnpm check:docsfails when docs and catalog disagree.
v0.24.2
0.24.2
Patch Changes
- deb07f7: Default narrow public kanban views to the mobile list without replacing the saved desktop view, and order mobile status groups for phone workflows.
- 132e6af: Theme the mobile list view's status dropdown so it follows the board's dark/light colors instead of the browser's default white control.
- 481663c: Preserve attachment-added timestamps when listing task files, with a filesystem timestamp fallback for legacy refs.
v0.24.1
v0.24.0
0.24.0
Minor Changes
- d4d68db: Auth is now project-scoped:
vibeflow loginstores the credential user-scoped (keyed by API host) and links the board to the current project instead of the whole machine, and every command resolves that project's own pointer. No data migration — local stores are untouched; runvibeflow loginonce per project to link it (a leftover machine-global token is ignored with a one-line notice).
Patch Changes
- 04d0009: Fixed delta push failing with
400 BATCH_TOO_LARGEon any push of more than 100 changed tasks: the delta chunker allowed 200 tasks per archive request while the server'sPOST /api/v0/tasks/import/archivecaps atV0_IMPORT_MAX_TASKS(= 100).DELTA_CHUNK_MAX_TASKSis now 100, so a 123-task push travels as 100+23 instead of one refused request. - 9fde4fe: Fixed
vibeflow auth loginfailing with "Device code expired" when this machine already has a token: the CLI now answers the login server's reuse signal — adopting the existing stored token when one is present, or rotating to a fresh token when none is — and fails loudly on unknown login responses instead of hanging until expiry. - 6f953e2: Fixed auth resolution falsely unlinking a valid project when one account has boards in two projects:
resolveProjectAuthtreated the credential store's singleworkspaceIdper host as a hard match, so a second login (naming the other board) flipped the first project to "Not logged in" even though the account-scoped token was valid for both boards. The project pointer now picks the board and the credential only proves identity — aworkspaceIdmismatch still resolves online on the pointer's board. The device-login adopt path likewise keeps an existing project pointer as-is instead of silently re-pointing it to whatever board last won the shared credential store (only a pointer-less project adopts the credential's board). - 608633b: Fix
tasks --tagmatching nothing on a shared board though the board sends tags. The CLI's server->task mapping dropped thetagsevery board row already carries, so the filter read an absent field for shared boards while local boards read the record — the same command answered differently depending on where the board lives. The mapping now carries tags exactly where the local path puts them (same verbatim rule: every non-empty string, no trim/lowercase/dedupe), and the existing filter keeps doing its one job in both cases — no second tag-specific path. - f0f0f9f: Fixed task records with a leaked
projectDirroot key quarantining on every pull whiletasks --normalizeclaimed "already normalized: 0 changes". The writer wascreateSaasTask: it sentprojectDir(request-scoping metadata, headers-only) inside the POST body the server mirrors verbatim as the stored record. The body no longer carries it; pull strips the key on both the merge and brand-new-task paths so a legacy poisoned server row cannot re-poison the store; andtasks --normalize --applynow heals unknown-root-key records with an explicit reportedstrip-unknown-root-keyrepair instead of leaving them quarantined forever. Strict parsing is unchanged — malformed JSON, nested unknown keys, future versions and every other defect still quarantine — and the empty-normalize message now names any remaining quarantined records instead of claiming a clean store.
v0.23.0
0.23.0
Minor Changes
-
ba2e776: Include your device name and a stable, salted machine identifier during login so supported servers can associate API tokens with your machine. The identifier survives logout and is not a credential; servers that ignore this metadata continue to work unchanged.
-
2623818: Add bulk tag Remove to the kanban board's Tags filter: each tag row offers a confirm-then-remove action that strips the tag from every matching task and refreshes on success.
Highlights
- Bulk-remove a tag from every matching task in the board's Tags filter, with a confirmation step before anything is removed.
The core operation stages all replacements under deterministic per-task lock order with byte-exact backups, rolls every file back on failure, and broadcasts once; crash-window semantics are all-or-nothing against an exception and best-effort against a kill, same as the single-task path.
Patch Changes
- 301dd17: Fix
tasks --commitfailing withTask file not foundwhile--getresolved the same ticket. The commit path re-derived a concrete file path with a second directory scan after the shared id resolution, so any concurrent store rewrite (every task operation rewrites files via tmp-file + atomic rename) in between lost a race the read path never ran. Both commit helpers now resolve through the same single lookup as reads (resolveLocalTask), retry once on a transient miss, and fail loudly naming the resolved id and the tasks directory tried; the commit-record link is written against the resolved snapshot and a lost link is reported instead of silently dropped. - b6784e8: Add a blob fallback to the overlay console and bookmarklet loaders, show a clear Content-Security-Policy diagnostic when loading fails, and clarify strict-policy limitations in the integration guide.
- bd4b9d0: Refuse commits with test author or committer identities, with resolved identities and Git configuration instructions in the error. Check outgoing commits before push and recent history in the unit suite as additional safeguards. The five existing diagnostic-identity commits are permanent exceptions by owner decision, keyed only by their full commit SHAs; a new commit cannot inherit an exception. Local hooks can be bypassed with
HUSKY=0,--no-verifyorcore.hooksPath; the history test still checks when the unit suite runs.
v0.22.0
0.22.0
Minor Changes
-
e97c041:
vibeflow pushnow uses the batched import when the server offers it, falling back to the one-by-one path on older servers. Tasks go up in chunks of at most 100 with per-chunk timeout and retry, quota is checked before the first chunk, each chunk is checkpointed to disk so a killed push resumes, and file uploads skip files the server already holds. Progress, refusals, and--jsonoutput are unchanged. -
d1594b7:
vibeflow tasks --attach <path> --task <id>attaches a file (e.g. an implementation plan) to a ticket without changing any field, on any task type, locally and online. It supports--move(delete the source after a successful attach),--dry-run, and--json(answering{ ok, taskId, fileId, name, size }). The target is the explicit--taskvalue (full id or unique prefix); the same file is never uploaded twice (E_FILE_EXISTSnames the file). Directories, empty files, executable types, and files over the size limit are refused with the limit printed. -
Include your hostname and operating system when logging in so supported servers can give your API token a recognizable device name.
-
Send a stable, salted machine identifier during login so supported servers can associate API tokens with your machine without using its hostname as an identifier. The identifier survives logout and is not a credential.
-
c821fdf: New kanban dev mode:
--dev(orVIBEFLOW_DEV=1) serves the board script as a separate asset and the dev board full-page reloads whenever the bundle rebuilds, so editing the kanban client refreshes the browser with no server restart. Production is unchanged (single-file inlined bundle). Full-page reload only — no state preservation. -
6bf7997: The CLI kanban server now serves a read-only board overview page at
/overview, linked from the board header ("Overview") and back. It renders board-level aggregates — counts by status, tasks done today and in the last 7 days, the oldest todo and in-progress tasks with age and board deep-links, and an assignee breakdown — computed client-side from the sameGET /api/taskspayload the columns use, so no new API or data layer was added. Both routes serve the same inlined single-file shell (production npx packaging unchanged), the page uses only shared theme tokens and real table semantics, and it never mutates: no drag, no writes, card references link back to/kanban#task-<id>. -
250112e:
limit: 0is no longer an unbounded mode onvibeflow tasks/list_tasks: an explicit 0 (or any non-positive value) now resolves to the default page size (20) exactly like omitting the parameter, and the fallback is named loudly in the--jsonenvelope and the human listing. Newtasks --allflag pages through everything when you really want it all; cursor paging (nextCursor) remains the MCP path.remainingcounts now agree withhint, and projected rows (--fields/fields) always carrycommentCount/fileCountso a projection never silently hides discussion or attachments. -
64c2629: In local mode, marking a parent task
donenow cascadesdoneto all descendants in the same edit. Already-done descendants are left untouched, cycles terminate, and marking a childdonenever touches its parent. -
13f208f: Push now sends the complete local record, and a server that supports it mirrors it verbatim instead of reconstructing a subset — so comments, commits,
openedBy/expandedBy, and non-parent links survive the round trip. Record normalization preserves unknown keys instead of silently dropping them.vibeflow authors link [--dry-run]resolves each commit to its original git author email, filling only missing values and reporting conflicts without overwriting. CLI-created comments capturegit config user.emailasauthorEmail(absent when unavailable, with one warning per process). -
ff85737: Add
vibeflow pull(board → local additive sync, the inverse ofpush): fetchesPOST /api/v0/tasks/export/archive?boardId=…with the stored bearer token, stages the gzipped tar under.vibeflow/.pull-tmp-*/, verifies it (manifest version, entry counts, per-task hashes, per-file sha256) and only then merges into the local store — any verification failure writes nothing. The merge is additive and local-wins by default (--prefer-remoteflips conflicting fields); nothing is ever deleted. Refusals map to non-retryable messages (403 EXPORT_NOT_ALLOWED→E_PLAN_REQUIREDupgrade hint,413→ size-cap message); retries fire only for transient failures. Flags:--board,--out,--prefer-remote,--dry-run,--json. Ships with apullMCP tool (cliRef.command: "pull",dryRundefaultfalse) wired through the manifest like every other tool. -
8d1c99c: Push now rides out rate limits instead of abandoning the remaining tasks: when the server answers 429, the push waits for the advertised
Retry-After(capped at 120 seconds) and resumes where it stopped, up to 3 waits per push — on both the batch path and the one-by-one fallback. The login-time push also uses the batch import when the server offers it, with the same one-by-one fallback and quota preflight aspush. -
8de4ac5: Push now reports true grouped counts (e.g. "60 created, 1319 refused: 402 plan-limit ×1319") with each refusal's HTTP status and server error code, instead of a false "already existed" line. The loop stops early on 402 plan-limit and 429 quota and prints the server's message loudly with the retry delay. Skipped links summarize by type with the full list behind
--verbose/--json. -
abc34bc: Push output stays minimal on huge runs: a TTY shows one updating line (counter, bar, percent, ETA) and piped output logs sparsely instead of one line per task. The final summary merges created/refused and stop/not-attempted counts into two lines, all on stderr with
--verbose/--jsondetail unchanged. -
d979a34:
vibeflow pushno longer deletes anything locally.Push used to remove every pushed task's JSON, its asset directory and its
screenshots by default, so a routine command consumed the local store. That
delete is unrecoverable by push, and measured in production one run removed
2416 files — including six attachments whose upload had just failed, taking the
last reference to those files with it.Keeping local files is now the default. Deletion requires an explicit
--prune-local, and even then the whole prune is refused whenever any file
upload failed, so a partial push can never destroy local-only data.
--keep-local-filesstill parses (now a no-op) for existing scripts. -
735bf34: Pushing many unsynced tasks no longer runs silent: the push loop reports
Pushing done/totalafter every task, with a visual bar on a TTY and counter-only updates when piped, all on stderr so stdout and--jsonstay clean. -
20c49b9: Make a re-push a repair, and refuse destructive pruning.
pushnow probes the import capability BEFORE filtering the diff and sends
tasks that are already on the board when the server advertiseslossless. A
re-push is therefore the only thing that can restore comments, commits, links
andopenedByan older lossy import dropped — previously "Everything is
already pushed" returned first and the repair never ran.- Quota preflight counts only tasks that will be CREATED.
--prune-localrefuses to delete anything unless the server proved a
lossless import; on a lossy server the local store is the only complete copy.authors linkonly asks git about hex-shaped shas:--allused to be read as
an option and "resolved" to a real author email that was then written into a
task file. It also exits 1 when git is unavailable instead of succeeding.push --jsonreports the number of tasks pushed, not the number pruned.
-
c2f4608: Online
tasks --addno longer also writes the local.vibeflowrecord: online writes stay online, andpull/pushare the only things that materialise the local store. A local copy that silently lags behind the board was worse than none. -
ac668a9: BREAKING: removed the
export_promptMCP tool. Its single-task read is covered byget_taskand its human render byvibeflow tasks --get; callers needing the old multi-task dump can loopget_taskover the ids fromlist_tasks. The remaining 11 tool descriptions now name sibling routing, disclose behavior annotations cannot express (claim null contract, attach overwrite-in-place, verify codes, dryRun previews), and the input schemas document previously undocumented fields. -
7c1edd1: New
vibeflow tasks --delete <id> [--yes]: resolves full ids and unique prefixes (refusing ambiguity), prints what would be deleted and exits non-zero without--yes. A local parent with children is refused even with--yes— delete the children first, deepest first. The remote delete cascades, so a parent delete warns naming every descendant and drops the matching local records so a later push cannot recreate them.--jsoncarries{ ok, deleted, id, deletedIds }, and--yes --dry-runpreviews with zero mutations.Every id-taking link flag (
--parent,--set-parent,--relates,--blocks,--unrelates,--unblocks) now resolves prefixes against the remote board before the request — exact id wins, a unique prefix resolves, an ambiguous prefix is refused naming the candidates — instead of failing with a not-found error for values--getdisplays. -
43798f6: Push now carries a whole subtree — tasks with parent links and files — in one request per chunk (up to 100 tasks / 50 files / 25 MB), instead of one write per task, link, and file. Parent links resolve in-manifest first, else against tasks already on the board, so children can never be orphaned by a failed follow-up phase. Old servers without the endpoint fall back to the legacy phases automatically.
-
65d08e5: Two new v0 batch-import operations:
POST /api/v0/tasks/batchcreates up to 100 tasks per chunk with per-item resul...