Repository navigation
feat: issue-tracking boards — kanban, table and roadmap views with fields, iterations and saved views - #611
Merged
Merged
Conversation
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>
|
Important Review skippedToo 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.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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:cardper item and their ownboardrevision, 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 (state2 marks a deletion), so a deleted newest document can never bring an older one back.What's in it
boardandcardin forge-meta. Testnet is already updated: forge-meta6arQJW8y…went v2→v3 (10,913 B, 0.4612 tDASH, C1 44/44), after a rehearsal on the scratch set. The evidence is inforge-contracts/evidence/testnet/.lib/rules/boards.ts,forge-core::rules::boards) withboard_*vectors: the spec format, ranks, the placement fold, the query language, iterations, grouping, sorting and totals. 49sealed_board__*vectors pin the private format (private-repos.md§4.6).dg board list|view|create|move|set|add|archive|remove|next-iteration|close|delete, with--jsonschemas.docs/guides/boards.md, plusforge-v2.md,limits.md,costs.mdandeconomics.md(with measured fees).How it was proved
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 incost.tsand the docs.cargo testfor 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.tsfails on the build box with git 2.53, the same as on master.🤖 Generated with Claude Code