Skip to content

feat: issue-tracking boards — kanban, table and roadmap views with fields, iterations and saved views - #611

Merged
PastaPastaPasta merged 26 commits into
masterfrom
feat/boards
Oct 28, 2026
Merged

PastaPastaPasta merged 26 commits into
masterfrom
feat/boards

Conversation

@PastaPastaPasta

Copy link
Copy Markdown
Owner

Issue tracking on Forge stopped at a flat list with labels and milestones. There was no way to lay work out in stages, prioritise it, plan sprints or see a team's progress: the things people use GitHub Projects, Trello or Jira for. This adds boards: kanban, table and roadmap views over a repository's issues and pull requests, with custom fields, iterations, saved views and WIP limits, in the web app and in dg.

The design is in docs/design/boards.md. It starts from the user stories the three products share (§1), then makes its own choices where Forge's constraints point elsewhere:

  • No draft cards. Quick add creates a real issue, which costs about the same as a card and already has comments, labels, a number and history. There's only one kind of item, so nothing ever needs converting.
  • Automation is derived, not run. Forge hosts nothing, so no server can react to events. Instead the board's definition holds rules that every reader applies when it draws the board: sources (new issues and PRs appear by themselves), a Done column (closed or merged items move there), and auto-archive after N days. These rules cost nothing, take effect immediately, and the web and CLI agree on them through shared test vectors.
  • One mutable document per member. Each member has their own card per item and their own board revision, and readers take the newest. After a member's first write, a move is a replace, about 0.00004 DASH instead of about 0.0005. Documents are never deleted (state 2 marks a deletion), so a deleted newest document can never bring an older one back.
  • Ordering uses fractional base-62 ranks. Items from sources have an implicit rank, so a card can be dropped between two of them without writing either.
  • Write access is enforced by consensus. Card writes need a maintainer, writer or triage member of the board's home repository; board definitions need a maintainer or writer. A board can hold items from any repository, which is how organisation-wide boards work. Private repositories' boards are sealed with the repository key.

What's in it

  • Contract (UPDATE-3): board and card in forge-meta. Testnet is already updated: forge-meta 6arQJW8y… went v2→v3 (10,913 B, 0.4612 tDASH, C1 44/44), after a rehearsal on the scratch set. The evidence is in forge-contracts/evidence/testnet/.
  • Shared rules in TypeScript and Rust (lib/rules/boards.ts, forge-core::rules::boards) with board_* vectors: the spec format, ranks, the placement fold, the query language, iterations, grouping, sorting and totals. 49 sealed_board__* vectors pin the private format (private-repos.md §4.6).
  • Web:
    • a Boards tab and list with four templates;
    • the board page with kanban (pointer, touch and keyboard drag), table (editing in place) and roadmap layouts;
    • filters and saved views, swimlanes, WIP limits, column totals and an iteration progress bar;
    • an item side panel, quick add, and a settings editor;
    • a Boards section in the issue and PR sidebar.
  • CLI: dg board list|view|create|move|set|add|archive|remove|next-iteration|close|delete, with --json schemas.
  • Docs: docs/guides/boards.md, plus forge-v2.md, limits.md, costs.md and economics.md (with measured fees).
Kanban Item panel
kanban panel
Table, grouped by status Roadmap
table roadmap
Settings Issue sidebar
settings sidebar
Phone Dark
mobile dark

How it was proved

  • Live test against live testnet (boards.live.test.ts): it creates boards and writes, moves and archives cards. Consensus refused every write it should: a stranger's board and card, a triage member's board, a removed member's replace, and a card naming something that isn't an issue or PR. The fees it measured are the ones in cost.ts and the docs.
  • Browser QA on testnet: a headless Chromium session went through stories U1–U15 as owner, triage member, stranger and signed-out reader, on desktop, a phone viewport and in dark mode. It found 25 defects, all fixed. The required "playwright (read-only, testnet)" suite passes locally (225 passed, 0 failed), and pb-1's page budget is unchanged.
  • Offline tests:
    • vitest across the board areas, tsc, lint and copy-lint;
    • cargo test for forge-core and dg, including both conformance harnesses, plus clippy -D warnings;
    • build.py --check, vectors.py --check, contract-validate (ALLOWED as an update), and the deploy-v2 tests.

Every slice had a code-review-validator pass; Fable reviewed the design and the schema before anything was registered; one review of the whole branch at the end found 12 issues: 10 are fixed, and the two optional ones are left (closed-item cutoffs that differ at the margins between web and CLI, and the CLI reading a full snapshot before each write). lib/merge/xdiff.parity.test.ts fails on the build box with git 2.53, the same as on master.

🤖 Generated with Claude Code

PastaPastaPasta and others added 26 commits October 27, 2026 22:46
Adds `board` (a board's definition) and `card` (a member's placement of one
issue or PR on a board) behind a new UPDATE-3 flag `boards` in build.py, as
docs/design/boards.md §3 specifies. Like UPDATE-2's vaultEntry they are defined
in forge-community, moved to forge-meta by META_TYPES and built with the
four-contract layout only.

Both are mutable, never deleted (state 2 is the delete) and gated like label:
a forge-core maintainer of the home repo, or a writer whose role is the
claimed r, re-checked on every replace. board: r = 1, unique byKey (repoId,
key, $ownerId), noPlain/hasName, enc 29-5120. card: r 1-2, item refersTo a
forge-collab issue or patch, unique onItem (item, repoId, board, $ownerId) and
recent (repoId, board, $updatedAt), noPlain, enc 29-2560. With
mainnet_pinned_gates the role claims are rules (rClaim).

forge-meta grows 7,684 -> 10,842 B (create transition 10,948 B, 9,532 B of
room). contract-validate accepts it as an update of the registered testnet
forge-meta and of testnet's version 2; testnet's registration lists `boards`
under `since`. The vectors (U3), the update guards, an offline-chain test of
the gate and an `--update meta` deploy test cover it; deploy-v2 already
substituted forge-collab's id on an update, and its self-test now checks a
forge-meta with cards names it. The clients' layout maps learn both types
(META_ONLY_TYPES: no three-contract home). Nothing is broadcast.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The pure board rules of docs/design/boards.md, in forge-web
lib/rules/boards.ts and forge-core rules::boards, held together by 66
shared board_*__*.json vectors (board_spec, board_rank, board_fold,
board_query, board_iteration, board_view) that both suites run:

- spec: strict parse of the v1 definition with every §8 limit, canonical
  serialization (round-trips, <= 4096 B), the new-board template, card
  field values (unknown fields/options and wrong types dropped, <= 2048 B)
- rank: rankBetween (strictly between incl. implicit bounds ending in 0
  and prefix pairs; re-rank when nothing fits), implicit, top, bottom,
  rerank; property-tested in both languages with one splitmix64 PRNG
- fold: placement per item (Done rule incl. columns after Done, default,
  removed, auto-archive with explicit now), newest card and newest board
  revision by ($updatedAt, $id)
- query: board qualifiers (status, fields with comparisons and ranges,
  iterations, dates, repo, is:archived, negation), source queries
- iterations, grouping, sorting, column totals, WIP, iteration progress

forge-core reads JSON with serde_json float_roundtrip so card numbers
read exactly as JSON.parse reads them; the web refuses what serde_json
refuses (lone surrogates, 1e400, nesting past 127). The search tokenizer
moves to lib/rules/search-terms.ts so the rules stay SDK-free. Design
§2.7 records the encoding decisions.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The forge-web layer the board pages build on (docs/design/boards.md):

- reads (lib/repo/boards.ts): a repo's boards (newest revision per key,
  deleted dropped), one board with every card (card.recent), the 20 s
  poll (>= and merged by $id), an item's boards for its sidebar
  (card.onItem, same-owner homes only) and its placement there
- items (lib/repo/board-items.ts): the fold's BoardItem facts from the
  Issues/PRs list indexes: open items, closed ones from the transition
  feed newest first (exact resume, ties past a page, auto-archive window
  or 200 most recent per source repo, loadOlderClosed), card-named items
  in any repo, placeholders for private items
- writes (lib/repo/board-writes.ts): create/save/close/delete boards,
  card writes over a fresh read of the definition and the item's newest
  card, own document found among raw rows; move (rank before an item,
  re-rank refusal), re-rank, add/archive/remove, next iteration, quick
  add; role-gated (board r=1, card r 1-2 in rules/roles.ts)
- private repos: board/card sealed into enc v0x01 (lib/private/board.ts,
  TLV tags 32-36, private-repos.md §4.6) with 49 sealed_board vectors from
  an independent Python reference (tools/private-repos-vectors/boards.py);
  the Rust rules harness skips the case until forge-core reads it
- costs: estimated board/card entries and priceBoardWrites
- hooks/use-board.ts: useBoards, useBoard (polling while visible,
  definition re-read on focus, optimistic cards with rollback),
  useItemBoards

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
BoardTable and BoardRoadmap exports for the board shell to import; the
layout props gain an optional onViewChange (additive) for sort/group
changes that the shell writes into the URL.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The table layout (boards.md §4.2): view columns with Title first,
header sort through onViewChange, sections by view.group with counts,
WIP and the first number field's sum, Status and custom fields edited in
place (one card write each), a roving-tabindex keyboard grid, private,
archived and pending rows.

The roadmap layout (§4.3): bars across an iteration or between two date
fields, weeks/months/quarters zoom, today's line and iteration bands,
unscheduled items beside, a list for screen readers, and drag to move or
stretch a date bar (one card write on release).

board-fields.tsx holds the value editors and labels the table, settings
and issue sidebar share. layout-props gains the shell's home/addr/labels
(additive).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- /repo/boards: open and closed boards (name, description, column
  count, last change) and New board for maintainers and writers, with
  four templates (Kanban, Sprint board, Bug triage, Empty) priced
  before signing; the new board opens
- /repo/board/settings: the definition as a draft saved in one priced
  write: columns (colour, WIP, drag or up/down reorder, delete, Default
  and Done), fields (select options with colours, iteration cadence with
  a preview), sources (owner's repos or any owner/name, filter checked
  as typed), auto-archive, views, close/reopen/delete; precise name
  problems and a 4096-byte size meter; deleting a field cleans the
  views that point at it; read-only for others
- issue and PR sidebar Boards section (boards.md 5.6): status and
  fields per board, Add to board; reads only once scrolled into view
- a top-level Boards tab beside Pull requests on networks with
  forge-meta, as GitHub places Projects; page titles

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- /repo/board?owner=&name=&b=: the board shell. Header (name,
  description, Closed, refresh, Settings), saved views as tabs with the
  URL's unsaved changes (q, group, lane, sort, layout, cols, date) and
  Save view / Reset, the board query with unresolved qualifiers listed
  under the box and @me as the signed-in identity, Columns / Swimlanes /
  Sort pickers, Show archived, the current iteration's progress with a
  priced "Move open items to the next iteration", the refusal banner
  with its re-rank, "Load older closed items"; renders the kanban, table
  or roadmap layout
- kanban: status or select/iteration columns, collapsible swimlanes,
  cards with repo, number, state, labels, assignees and the view's
  fields; WIP "n / limit" (red when over) and the first number field's
  sum; native pointer drag and drop (touch by the grip) with a drop
  line and auto-scroll, cross-swimlane moves for select/iteration lanes;
  keyboard moves with live announcements; quick add (a title makes an
  issue, #12 / owner/name#12 / a link adds one); column menu re-rank
  and archive-all, priced; one column at a time on phones
- item panel (&item=): body, labels and assignees (the issue's own
  pickers and events), Status and every custom field, archive, restore
  and remove
- every card write passes the write guard, and on a private board an
  item of another repo is confirmed once (boards.md 3.3)
- design: the extra URL params, the item deep link, the touch grip

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
From review of the boards UI:
- gate every board surface (Boards tab, list, board, settings, issue
  sidebar) on forge-meta declaring board and card (boardsDeployed: the
  SDK's cached contract, kept per network), not on forge-meta existing:
  testnet's forge-meta v2 has no boards
- new columns, fields and options never take an id a card still names
  (settings reads the board's cards; ids go past the highest ever used,
  refused past 255), so a deleted entry's items never come back
- one queue per item in useBoard and useItemBoards: a second edit waits
  for the first and applies over its card (writeCard opts.over), so a
  member's back-to-back edits no longer undo each other
- table: edit and focus keyed by (section, item, column), refocus only
  after Enter/Escape/a pick, a refused value is put back on leaving
- selects write a pointer pick at once, a keyboard step on Enter or
  blur; a closed item's Status disables columns before Done
- sidebar keeps its list while re-reading after a write
- settings: refuse a save over another member's newer revision, number
  fields clamp on blur, stable source rows, Firefox drag, copy fixes
- roadmap: private items do not drag, swapped start/target ends, no
  shift before a drag counts, touch scrolls from a bar
- rules export their view-key checks (groupKeyOk, sortKeyOk, colKeyOk,
  viewDatesOk, fieldOfKey, DAY_MS...) and settings, view-state and the
  layouts use them; layouts get rows from the shell

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
forge-core collab::boards ports the web's board data layer
(lib/repo/boards.ts, board-items.ts, board-writes.ts): a repo's boards
(newest revision per key), one board with every card (card.recent), an
item's cards and boards (card.onItem), the fold's items from the issue and
PR listings (closed ones kept by the auto-archive window or the 200 most
recently closed, card-named items by id in any repository), and every
write as one mutable document per member: create (intent-derived key,
raw rows counted), save, close/reopen/delete, card writes applied over a
fresh read of the item's newest card, moves with ranks, bulk
add/archive/remove, next iteration and quick add. board claims r 1 and
card r 1-2 (ROLE_GATED_TYPES, gated_write), as lib/rules/roles.ts.

private::board seals and opens a private repository's boards and cards
(private-repos.md §4.6), sharing the §4.4 AD and TLV padding helpers; the
49 sealed_board vectors now run in Rust. A repository made public opens
its private-era boards with the published keys.

dg board: list, view (--view, --archived, --json with the fold), create
(the web's kanban/sprint/triage/empty templates, --columns), move
(--top/--bottom/--before/--after), set field=value, add (--title opens an
issue), archive (--restore), remove, next-iteration, close (--reopen),
delete; priced and confirmed first, E106 on a partial bulk write. JSON
schemas, help snapshot, the Boards guide and design §6 updated.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
On testnet's scratch set the forge-meta v3 update landed, but the check
right after it read a node that still proved version 2, so the run stopped
with the update pending. deploy-v2 now reads the version again for a few
seconds after the broadcast, and before rebroadcasting a pending update (a
rebroadcast would be refused and overwrite the pre-broadcast balance the
cost is taken from). freeze-c1-check expects the recorded version rather
than 1, so it checks a set after an update.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
boards.live.test.ts runs the web's board data layer against a real
forge-meta with `board` and `card` (FORGE_LIVE=1; FORGE_BOARDS_RECORD points
it at a scratch set). It covers a member's board writes (create, rename,
close, reopen, delete) and card writes (place, move, fields, archive), and a
triage member's card. It reads them back through readBoards, readBoard,
readCardsSince, readItemCards and the fold.

Consensus refuses a stranger's card and board, a triage member's board, a
removed member's replace of its own card, and a card naming no issue or PR.
It prints each write's fee. It passed three times on testnet's scratch set.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…measured fees

The scratch set's forge-meta (8qj74sQt…) was updated to version 3 with board
and card: one DataContractUpdate of 10,913 B at contract nonce 3, costing
0.461175 tDASH. A C1 check passes 44/44. The live set's dry run builds the
same transition. Its real run waits for this branch to be on origin, since
deploy-v2 records a fetchable commit.

The fees boards.live.test.ts measured replace the estimates in cost.ts, in
dg's quotes and in the docs:
- board: 62.8M-63.8M for a repo's first, 53.7M-54.7M later;
- card: 70.5M-70.9M for an item's first, 88.3M-89.1M for a board's first,
  42.8M-43.2M when another member has one;
- replaces: 3.4M-5.2M.

Board writes are now priced by their real definition size. Board and card
replaces are admitted at the create's admission, which was never probed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
forge-meta on testnet (6arQJW8y…) is updated in place to version 3, adding
`board` and `card` (UPDATE-3): one DataContractUpdate of 10,913 B at the
deployer's contract nonce 3, 0.461175 tDASH. The record gains the update,
and the web snapshot is refreshed at protocol 14. C1 on the live set passes
44/44 (c1-v3.json).

The scratch set was updated first. boards.live.test.ts then passed against
the live set as well. It checked the member writes and reads, and consensus
refused a stranger, a triage member's board, a removed member's replace and
a card naming no issue or PR. Its fees fell within the scratch ranges the
cost model was set from, except two unexplained outliers, both still under
their previews: a triage member's first card at 79.2M, and a stranger's
first refusal at 10.3M. The docs and the CHANGELOG now say testnet has
boards.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
boardsDeployed asked contracts.fetch for forge-meta on every repo page's
first load, and contracts.fetch is a getDataContract request, never the
SDK's seeded cache: pb-1's cold issues list read 12 requests against its
budget of 11. It now answers from the build's bundled snapshot of
forge-meta when that declares board and card (an update can never
remove a document type, rs-dpp validate_update), and fetches only when
the snapshot predates the update.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A public repo's pages show short URLs (/owner/name/issues/12,
/owner/name/pull/7/files), so a link pasted from the address bar was
taken for a title and made a new issue named after the URL. Quick add now
expands short URLs (and drops the build's base path) before reading the
route, and leaves GitHub's own issue URLs alone.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- A board spanning repositories showed each card's whole owner/name
  label: a 44-character identity id that truncated the number away on
  cards and cut table titles to one letter. Cards, table rows, roadmap
  lines and the item panel now show `name #12` (ItemRef), the full
  label as the tooltip; repo: matches an owner's whole id or DPNS name
  for every repository, not a shortened id nobody can type.
- The table's Group picker had no None, and picking Status cleared the
  grouping: a table could not be grouped by Status at all.
- A roadmap could not be switched to plot two date fields when the board
  has an iteration field: a Dates picker sets view.date.
- The item panel sat 12px down the viewport (the page's space-y margin
  on a fixed layer); it stayed open on "Item not on this board" after
  Remove; its link read "Open issue" beside the state "Open issue".
- A keyboard move into another column lost the focus (the card's new
  element renders after the drop); it is now refocused there.
- A label defined from the item panel showed the fallback colour on the
  cards until a reload: the page reads the definitions again when an
  item carries a label they lack.
- Light-theme contrast: the drag ghost's dark-mode note and the card and
  settings grips (lib/design/contrast.test.ts).
- "Show archived" shows only archived items: renamed "Only archived".
  The filter box's example names this board's columns and fields; a
  single unresolved qualifier "names nothing"; settings no longer says
  closed items go to Done on a board without one; quick add says
  "Puts #7 in Done" (it moves an item already on the board).
- Settings' column and field rows line up whatever chips they carry; the
  new-board templates read from the top; the Boards list puts the most
  recently changed board first; the issue sidebar's controls share one
  height; the roadmap's today marker no longer crosses header labels.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The short-URL reading built a URL from any text that parses as one, and
a title such as "Bug: the build fails" parses as a URL of scheme `bug:`;
the second `new URL` then threw during render and took the board page
down. Only http(s) links are read as links, and a failed parse is a
title.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…dges

- The table's Repository column, a repository grouping's headings and
  repository swimlanes showed the whole owner/name label (a 44-character
  identity id first): they show the id shortened (repoLabelText), the
  full label as the tooltip.
- A keyboard drop refocuses its card only while the focus has not gone
  elsewhere (a dialog the move opened, a click away).
- The roadmap's Dates picker offers a date pair the URL or a saved view
  names the other way round, and None when nothing plots.
- The filter example quotes a name with a colon.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The read-only testnet suite's b-3 listed the repo tabs without Boards,
which every reader now sees on testnet (forge-meta v3).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Its "In" menu and "Creates an issue in …" used the items' owner/name
label (a 44-character identity id first) for the home repo and the bare
name for every other source repo.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…both clients

`repo:owner/name` matched each client's own label for a repository (the web's URL owner or
DPNS name, the CLI's owner id), so one view filtered and sorted differently in the web and in
`dg board view`. Now both rule ports resolve `repo:` to an id before the fold: the client
resolves the names `repoNamesOf` / `repo_names_of` list (owner by identity id or DPNS name, a
bare name of the home repository's owner) and passes them to the parse; an unresolved name is
reported. Sorting by repo orders by repository id, as grouping already did; the label is
display only. New vectors pin the parse, the names and the sort.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
On a 1280x720 window the sidebar's Boards section starts in view, so `useInView` read the
item's cards and each board's definition within a cold issue or PR page load on testnet.
`useDeferredInView` now waits, once in view, for a scroll, a pointer or focus on the section,
or the browser going idle 8 s after it mounted. pb-6 asserts no `card` or `board` read in a
cold thread load.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…unded item reads

- A write now gets each item's last landed card (kept 60 s by the card queue, for single and
  bulk writes alike) and `writeCard` applies its patch over it while the fresh read lags
  behind it by `$revision` (`overIfAhead`); once the read caught up, the read is the base.
- A create that meets the signer's card made meanwhile re-reads and applies the patch over
  the newest card, not over a card built before the conflict.
- Quick add puts a field column's or swimlane's values into the new issue's one card.
- The sidebar's boards read the owner's repositories first, then `card.onItem` with
  `repoId in` them, a bounded number of pages: strangers' cards naming the item cost nothing.
- A private source repository with no session is not read; another private repository's
  items open where this tab already holds its session (§2.5).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…nded item boards

- A source repository's pull requests are read page after page (newest first, up to 30
  pages) instead of the newest 100 only.
- `dg board view --archived`, or a view asking for `is:archived`, keeps the next 200 closed
  items past the window, as the web's "Show older" reads them, so items auto-archived without
  a card show.
- An item's boards read the owner's repositories first, then `card.onItem` with `repoId in`
  them, bounded: strangers' cards naming the item are never read.
- A private repository other than the home opens where the signer holds its key (§2.5).
- Card writes: a write builds on the card this process's last write of the item landed while
  the read lags behind its revision, and a create that meets the signer's card made meanwhile
  re-reads and applies the patch over the newest card before replacing it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…te items, CLI reads

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- dg: a private repository opens only where the signer holds a key for it (`require_key`): a
  keyring loads for a non-member too, so their board views failed with E307 instead of
  showing "a private item".
- web: an edit right after one that created the card replaces that card while the read
  lacks it (it went down the create path and was refused as a duplicate); only a card the
  signer landed counts.
- dg: a PR walk stopped by the page cap, or by a page it cannot go on from, says partial;
  a landed card is weighed by content when the read has no revision, as on the web.
- web: expired landed cards are dropped on every write; a scroll of any container lets the
  sidebar's Boards read.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Oct 28, 2026

Copy link
Copy Markdown

Important

Review skipped

Too many files!

This PR contains 261 files, which is 161 over the limit of 100.

To get a review, reduce the PR to 100 files or fewer by splitting it into smaller PRs or changing its base branch.

Upgrade to a paid plan to raise the limit.

This review couldn't start because sufficient usage credits or metered capacity aren't available. Add credits or update usage-based reviews in the billing tab, then retry.

Run configuration
  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 49705a56-4ae6-434e-8385-6375b7d30fce
Commits

Reviewing files that changed from the base of the PR and between e498d5e and 4410078.

Files selected for processing: 261
  • CHANGELOG.md
  • crates/dg/src/board.rs
  • crates/dg/src/board/tests.rs
  • crates/dg/src/errors.rs
  • crates/dg/src/json_schemas.rs
  • crates/dg/src/main.rs
  • crates/dg/src/quote.rs
  • crates/dg/tests/snapshots/dg-help.txt
  • crates/forge-core/Cargo.toml
  • crates/forge-core/src/collab/boards.rs
  • crates/forge-core/src/collab/boards/tests.rs
  • crates/forge-core/src/collab/mod.rs
  • crates/forge-core/src/collab/v2.rs
  • crates/forge-core/src/keyring.rs
  • crates/forge-core/src/layout.rs
  • crates/forge-core/src/members.rs
  • crates/forge-core/src/private/board.rs
  • crates/forge-core/src/private/board/conformance.rs
  • crates/forge-core/src/private/doc.rs
  • crates/forge-core/src/private/mod.rs
  • crates/forge-core/src/private/tlv.rs
  • crates/forge-core/src/rules.rs
  • crates/forge-core/src/rules/boards.rs
  • crates/forge-core/src/rules/boards/tests.rs
  • docs/contracts/forge-v2.md
  • docs/deploying-to-a-network.md
  • docs/design/boards.md
  • docs/economics.md
  • docs/guides/README.md
  • docs/guides/boards.md
  • docs/guides/collaborating.md
  • docs/guides/costs.md
  • docs/limits.md
  • docs/schemas/README.md
  • docs/schemas/dg/board-add.schema.json
  • docs/schemas/dg/board-archive.schema.json
  • docs/schemas/dg/board-close.schema.json
  • docs/schemas/dg/board-create.schema.json
  • docs/schemas/dg/board-delete.schema.json
  • docs/schemas/dg/board-list.schema.json
  • docs/schemas/dg/board-move.schema.json
  • docs/schemas/dg/board-next-iteration.schema.json
  • docs/schemas/dg/board-remove.schema.json
  • docs/schemas/dg/board-set.schema.json
  • docs/schemas/dg/board-view.schema.json
  • docs/schemas/dg/index.json
  • docs/schemas/generate.py
  • docs/security/private-repos.md
  • forge-contracts/contracts/mainnet/forge-meta.json
  • forge-contracts/deployments/contracts/testnet.json
  • forge-contracts/deployments/testnet.json
  • forge-contracts/evidence/testnet/README.md
  • forge-contracts/evidence/testnet/c1-v3.json
  • forge-contracts/evidence/testnet/rehearsal-c1-v3.json
  • forge-contracts/evidence/testnet/rehearsal-scratch-record.json
  • forge-contracts/evidence/testnet/update-meta-v3.sha256
  • forge-contracts/schema/build.py
  • forge-contracts/schema/vectors.py
  • forge-contracts/scripts/deploy-v2.mjs
  • forge-contracts/scripts/deploy-v2.test.mjs
  • forge-contracts/scripts/freeze-c1-check.mjs
  • forge-contracts/scripts/lib/offline-chain.test.mjs
  • forge-contracts/scripts/lib/seed-io.mjs
  • forge-contracts/scripts/lib/seed-io.test.mjs
  • forge-contracts/vectors/board_fold__arch_off.json
  • forge-contracts/vectors/board_fold__auto_archive_boundary.json
  • forge-contracts/vectors/board_fold__bad_rank_and_values.json
  • forge-contracts/vectors/board_fold__boards_newest.json
  • forge-contracts/vectors/board_fold__boards_with_deleted.json
  • forge-contracts/vectors/board_fold__newest_card.json
  • forge-contracts/vectors/board_fold__no_done_no_default.json
  • forge-contracts/vectors/board_fold__placement.json
  • forge-contracts/vectors/board_fold__removed.json
  • forge-contracts/vectors/board_fold__reopened_archived.json
  • forge-contracts/vectors/board_fold__same_block.json
  • forge-contracts/vectors/board_fold__sources.json
  • forge-contracts/vectors/board_iteration__at.json
  • forge-contracts/vectors/board_iteration__range.json
  • forge-contracts/vectors/board_iteration__range_leap_year.json
  • forge-contracts/vectors/board_query__match_archive_and_state.json
  • forge-contracts/vectors/board_query__match_before_first_iteration.json
  • forge-contracts/vectors/board_query__match_dates.json
  • forge-contracts/vectors/board_query__match_fields.json
  • forge-contracts/vectors/board_query__match_iterations.json
  • forge-contracts/vectors/board_query__match_no_viewer.json
  • forge-contracts/vectors/board_query__match_people_and_repo.json
  • forge-contracts/vectors/board_query__match_text.json
  • forge-contracts/vectors/board_query__parse_board_qualifiers.json
  • forge-contracts/vectors/board_query__parse_issue_qualifiers.json
  • forge-contracts/vectors/board_query__parse_repo.json
  • forge-contracts/vectors/board_query__parse_source.json
  • forge-contracts/vectors/board_query__parse_unresolved.json
  • forge-contracts/vectors/board_query__repo_names.json
  • forge-contracts/vectors/board_rank__between.json
  • forge-contracts/vectors/board_rank__between_implicit_bounds.json
  • forge-contracts/vectors/board_rank__between_refused.json
  • forge-contracts/vectors/board_rank__bottom.json
  • forge-contracts/vectors/board_rank__implicit.json
  • forge-contracts/vectors/board_rank__rerank_empty.json
  • forge-contracts/vectors/board_rank__rerank_three.json
  • forge-contracts/vectors/board_rank__rerank_too_many.json
  • forge-contracts/vectors/board_rank__rerank_wide.json
  • forge-contracts/vectors/board_rank__top.json
  • forge-contracts/vectors/board_spec__default_template.json
  • forge-contracts/vectors/board_spec__parse_canonical.json
  • forge-contracts/vectors/board_spec__parse_refused.json
  • forge-contracts/vectors/board_spec__parse_serde_refusals.json
  • forge-contracts/vectors/board_spec__values_dropped.json
  • forge-contracts/vectors/board_spec__values_escapes.json
  • forge-contracts/vectors/board_spec__values_exact_numbers.json
  • forge-contracts/vectors/board_spec__values_kept.json
  • forge-contracts/vectors/board_spec__values_lone_surrogate.json
  • forge-contracts/vectors/board_spec__values_not_json.json
  • forge-contracts/vectors/board_spec__values_not_object.json
  • forge-contracts/vectors/board_spec__values_null.json
  • forge-contracts/vectors/board_spec__values_numbers.json
  • forge-contracts/vectors/board_spec__values_overflow.json
  • forge-contracts/vectors/board_spec__values_serde_refusals.json
  • forge-contracts/vectors/board_view__group_assignee.json
  • forge-contracts/vectors/board_view__group_iteration.json
  • forge-contracts/vectors/board_view__group_label.json
  • forge-contracts/vectors/board_view__group_milestone.json
  • forge-contracts/vectors/board_view__group_repo.json
  • forge-contracts/vectors/board_view__group_select.json
  • forge-contracts/vectors/board_view__group_status.json
  • forge-contracts/vectors/board_view__group_unknown.json
  • forge-contracts/vectors/board_view__progress.json
  • forge-contracts/vectors/board_view__progress_no_points.json
  • forge-contracts/vectors/board_view__sort.json
  • forge-contracts/vectors/board_view__sort_repo.json
  • forge-contracts/vectors/board_view__totals.json
  • forge-contracts/vectors/board_view__totals_default_view.json
  • forge-contracts/vectors/board_view__totals_no_number_field.json
  • forge-contracts/vectors/rc1/forge-community.indices.json
  • forge-contracts/vectors/sealed_board__open_board.json
  • forge-contracts/vectors/sealed_board__open_board_epoch1.json
  • forge-contracts/vectors/sealed_board__open_board_moved_to_other_key.json
  • forge-contracts/vectors/sealed_board__open_card.json
  • forge-contracts/vectors/sealed_board__open_card_empty.json
  • forge-contracts/vectors/sealed_board__open_card_enc_as_board.json
  • forge-contracts/vectors/sealed_board__open_card_moved_to_other_board.json
  • forge-contracts/vectors/sealed_board__open_card_moved_to_other_item.json
  • forge-contracts/vectors/sealed_board__open_no_epoch.json
  • forge-contracts/vectors/sealed_board__open_no_key.json
  • forge-contracts/vectors/sealed_board__open_other_owner.json
  • forge-contracts/vectors/sealed_board__open_plaintext_beside_enc.json
  • forge-contracts/vectors/sealed_board__open_private_without_enc.json
  • forge-contracts/vectors/sealed_board__open_short_enc.json
  • forge-contracts/vectors/sealed_board__open_superseded_epoch_still_opens.json
  • forge-contracts/vectors/sealed_board__open_tlv_board_tag_in_card.json
  • forge-contracts/vectors/sealed_board__open_tlv_board_without_spec.json
  • forge-contracts/vectors/sealed_board__open_tlv_col_two_bytes.json
  • forge-contracts/vectors/sealed_board__open_tlv_content_tag_in_board.json
  • forge-contracts/vectors/sealed_board__open_tlv_empty_rank_absent.json
  • forge-contracts/vectors/sealed_board__open_tlv_extension_skipped.json
  • forge-contracts/vectors/sealed_board__open_tlv_out_of_order.json
  • forge-contracts/vectors/sealed_board__open_tlv_rank_trailing_zero.json
  • forge-contracts/vectors/sealed_board__open_tlv_repeated.json
  • forge-contracts/vectors/sealed_board__open_tlv_truncated.json
  • forge-contracts/vectors/sealed_board__open_under_burned_epoch_by_member.json
  • forge-contracts/vectors/sealed_board__open_under_burned_epoch_by_removed_member.json
  • forge-contracts/vectors/sealed_board__open_version_3.json
  • forge-contracts/vectors/sealed_board__seal_board.json
  • forge-contracts/vectors/sealed_board__seal_board_epoch1.json
  • forge-contracts/vectors/sealed_board__seal_board_key_max.json
  • forge-contracts/vectors/sealed_board__seal_board_key_zero.json
  • forge-contracts/vectors/sealed_board__seal_board_name_63_chars.json
  • forge-contracts/vectors/sealed_board__seal_board_name_64_chars.json
  • forge-contracts/vectors/sealed_board__seal_board_name_blank.json
  • forge-contracts/vectors/sealed_board__seal_board_name_control.json
  • forge-contracts/vectors/sealed_board__seal_board_spec_4096_bytes.json
  • forge-contracts/vectors/sealed_board__seal_board_spec_4097_bytes.json
  • forge-contracts/vectors/sealed_board__seal_board_spec_empty.json
  • forge-contracts/vectors/sealed_board__seal_board_unicode_name.json
  • forge-contracts/vectors/sealed_board__seal_card.json
  • forge-contracts/vectors/sealed_board__seal_card_col_256.json
  • forge-contracts/vectors/sealed_board__seal_card_col_zero.json
  • forge-contracts/vectors/sealed_board__seal_card_empty.json
  • forge-contracts/vectors/sealed_board__seal_card_fields_2048_bytes.json
  • forge-contracts/vectors/sealed_board__seal_card_fields_2049_bytes.json
  • forge-contracts/vectors/sealed_board__seal_card_rank_63.json
  • forge-contracts/vectors/sealed_board__seal_card_rank_64.json
  • forge-contracts/vectors/sealed_board__seal_card_rank_trailing_zero.json
  • forge-web/app/repo/board/client.tsx
  • forge-web/app/repo/board/page.tsx
  • forge-web/app/repo/board/settings/client.tsx
  • forge-web/app/repo/board/settings/page.tsx
  • forge-web/app/repo/boards/client.tsx
  • forge-web/app/repo/boards/page.tsx
  • forge-web/components/repo/boards/board-bits.tsx
  • forge-web/components/repo/boards/board-dialogs.tsx
  • forge-web/components/repo/boards/board-fields.tsx
  • forge-web/components/repo/boards/board-kanban.test.tsx
  • forge-web/components/repo/boards/board-kanban.tsx
  • forge-web/components/repo/boards/board-page.test.tsx
  • forge-web/components/repo/boards/board-page.tsx
  • forge-web/components/repo/boards/board-roadmap.test.tsx
  • forge-web/components/repo/boards/board-roadmap.tsx
  • forge-web/components/repo/boards/board-settings-model.test.ts
  • forge-web/components/repo/boards/board-settings-model.ts
  • forge-web/components/repo/boards/board-settings.test.tsx
  • forge-web/components/repo/boards/board-settings.tsx
  • forge-web/components/repo/boards/board-table.test.tsx
  • forge-web/components/repo/boards/board-table.tsx
  • forge-web/components/repo/boards/board-templates.ts
  • forge-web/components/repo/boards/boards-list.test.tsx
  • forge-web/components/repo/boards/boards-list.tsx
  • forge-web/components/repo/boards/item-boards.test.tsx
  • forge-web/components/repo/boards/item-boards.tsx
  • forge-web/components/repo/boards/item-panel.tsx
  • forge-web/components/repo/boards/layout-fixture.ts
  • forge-web/components/repo/boards/layout-props.ts
  • forge-web/components/repo/boards/quick-add.tsx
  • forge-web/components/repo/boards/use-guarded-board.ts
  • forge-web/components/repo/boards/view-state.test.ts
  • forge-web/components/repo/boards/view-state.ts
  • forge-web/components/repo/issue-content.tsx
  • forge-web/components/repo/pull-content.tsx
  • forge-web/components/repo/repo-header.test.ts
  • forge-web/components/repo/repo-header.tsx
  • forge-web/components/repo/repo-shell-header.tsx
  • forge-web/e2e/page-budget.spec.ts
  • forge-web/e2e/v2-home.spec.ts
  • forge-web/hooks/use-board.test.tsx
  • forge-web/hooks/use-board.ts
  • forge-web/hooks/use-in-view.ts
  • forge-web/lib/auth/passkey-vault/deployed.ts
  • forge-web/lib/layout.test.ts
  • forge-web/lib/layout.ts
  • forge-web/lib/page-title.ts
  • forge-web/lib/private/board.conformance.test.ts
  • forge-web/lib/private/board.ts
  • forge-web/lib/private/index.ts
  • forge-web/lib/private/testing.ts
  • forge-web/lib/repo/board-items.test.ts
  • forge-web/lib/repo/board-items.ts
  • forge-web/lib/repo/board-writes.ts
  • forge-web/lib/repo/boards-deployed.test.ts
  • forge-web/lib/repo/boards-deployed.ts
  • forge-web/lib/repo/boards.live.test.ts
  • forge-web/lib/repo/boards.test.ts
  • forge-web/lib/repo/boards.ts
  • forge-web/lib/repo/contract.ts
  • forge-web/lib/repo/index.ts
  • forge-web/lib/repo/issue-index.ts
  • forge-web/lib/repo/private-session.ts
  • forge-web/lib/repo/pull-index.ts
  • forge-web/lib/repo/resolveRepo.ts
  • forge-web/lib/rules/boards.conformance.test.ts
  • forge-web/lib/rules/boards.test.ts
  • forge-web/lib/rules/boards.ts
  • forge-web/lib/rules/conformance.test.ts
  • forge-web/lib/rules/index.ts
  • forge-web/lib/rules/roles.test.ts
  • forge-web/lib/rules/roles.ts
  • forge-web/lib/rules/search-terms.ts
  • forge-web/lib/sdk/cost.test.ts
  • forge-web/lib/sdk/cost.ts
  • forge-web/lib/sdk/index.ts
  • forge-web/lib/view/issue-query.ts
  • tools/private-repos-vectors/boards.py

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@PastaPastaPasta
PastaPastaPasta merged commit ac39b08 into master Oct 28, 2026
44 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant