v0.3.0-beta.2

dev-process-kit 0.3.0-beta.2

A follow-up beta for the 0.3.0 page model. Install dev-process-kit@0.3.0-beta.2
(npm dist-tag beta); @latest remains 0.2.1.

Fixes

• Prototype sidebar overflow (#18) — the navigation grid now uses a
  minmax(0, 1fr) track and its items have min-width: 0. A long story name is
  ellipsized inside the rich select instead of widening the rail; the
  scenario/app switch, activity/story selects, step list and detail panel stay
  inside the sidebar column.
• GitHub Pages pins the checkout's package version through version.json, so
  the landing site loads the matching beta bundle.

Features

• The page switcher's + can add Whiteboard, Example Mapping and
  Kanban pages when boards.js is loaded (introduced in 0.3.0-beta.1).

The full 0.3.0 surface is described in the 0.3.0-beta.0 notes.

v0.3.0-beta.1

dev-process-kit 0.3.0-beta.1

A follow-up beta for the 0.3.0 page model. Install dev-process-kit@0.3.0-beta.1
(npm dist-tag beta); @latest remains 0.2.1.

Features

• The page switcher's + can now add Whiteboard, Example Mapping and Kanban pages,
  alongside the addable views. Board options appear when boards.js has registered the board, so
  an app is never offered a page it cannot create.
• Board definitions carry their own addable flag; diagram boards remain non-addable.

Fixes

• GitHub Pages now pins the version from package.json via version.json; the landing site loads
  the matching jsDelivr bundle instead of npm latest.

The full 0.3.0 surface (app/page/view/board model, review badges, supplements, alternatives,
task-board tabs, Event Storming/ERD fixes) is described in the 0.3.0-beta.0 notes.

v0.3.0-beta.0

dev-process-kit 0.3.0-beta.0

A beta for trying the new page model and review surfaces from a real page. Install
dev-process-kit@0.3.0-beta.0 (npm dist-tag beta); @latest remains 0.2.1.

Features

• App / page / view / board model — <dpk-app> holds pages, <dpk-page> holds exactly one
  whole-page view or board, and components live inside them. Pages share the app's header, review
  rail, draft and hash navigation (#page=…).
• Views — User Story Mapping, UX Prototype, Slides, Task Context Board, Delegation Poker and
  Plain, each with a documented base-data shape and review targets.
• Boards — ER, state, sequence, dependency, architecture map, mind map, kanban, event storming,
  example mapping and whiteboard; a board can be a page on its own or embedded in a view.
• Components — alternatives comparison, tabbed code groups, line charts, declarative
  right-click extensions, checklist, commentable, comment popover/thread, dialog panel, table,
  matrix, tag filter, combobox, select, browser and editor components.
• Review loop — Check Mode with reader-only marks, question (grill) badges anchored to their
  cards, a context menu, inline editing, comments and the hand-off brief.
• Supplements — supporting boards and notes open in a bottom drawer with one height across
  tabs; drag its top edge (or use the keyboard) to resize it.
• Task board — outputs in a left rail, with Context, Work log, Questions and Tasks tabs; tasks
  render as a Kanban.
• Event Storming and ERD — sharper note text, no editing outline, and relation glyphs that stay
  on the line. ERD tables and columns can carry grill questions.
• Design — refreshed tokens, card/callout/controls atoms, a coherent motion layer and light/dark
  parity throughout.
• Docs — every view, board and component has a page; the base-data/order and page-height
  contracts are explicit.

Breaking Changes

• The template model is replaced by the app/page/view/board model. A page must have exactly one
  view or board; there is no template-as-root wrapper and no variant="board".
• dpk-template-* elements are now dpk-view-*; board and component tags follow the
  dpk-board-* / dpk-* rules. Pages and drafts use the new page-qualified targets and #page=
  navigation.
• Entry points are views/<name>.js, boards.js, components.js and index.js. Pages pinned
  to an older bundle must migrate to a 0.3.x entry.
• No compatibility aliases are shipped. See docs/index.md at the tag for the current markup and
  data contracts.

Internal

• Layout/router benchmarks, browser QA fixtures and a docs-only generation check.

v0.2.1

Bug Fixes

• Questions in boards of <dpk-page>:
  • A data-dpk-grill block inside a board is no longer ignored. The page now asks its own questions and every board's in one panel.
  • A board's questions are qualified by the board, so they never collide: grill:retry@scope is shown as Q1@scope.
  • A board removed with REMOVE_BOARD no longer has its questions asked or counted. (#14)
• Question badges are now shown on marks in the sidebar, such as task-board's todos and outputs.
• Question badges now follow scrolling inside the shell, for example task-board's stacked layout on narrow screens.

Features

• Cards rendered from a template's base data take an optional questions field ("Q1 Q4"). It puts a question badge on the card, as diagram nodes already do. Supported in:

  • example-mapping: every card
  • usm: activities, steps, milestones and stories
  • event-storming: contexts and notes
  • task-board: todos, outputs and log entries
  • delegation-poker: decision areas
  • whiteboard: items

  (#14)

• The diagram docs now show that heading replaces a diagram's default toolbar title. (#15)

v0.2.0

Features

• Pages of boards: <dpk-page> holds several dpk-template-* boards in one page with a shared header, review rail, draft and storage. A left icon rail switches boards, and readers can add or remove boards through the ADD_BOARD / REMOVE_BOARD draft actions. Board targets are qualified as <type>:<id>@<board>, and the URL hash is namespaced per board. See docs/page.md. (#10)
• ER diagram
  • Reviewers can add a column (ADD_FIELD) or change a column's type and nullability (EDIT_FIELD) from a table card. These edits are recorded in the draft and shown as added or changed rows. Relation columns stay read-only. (#12)
  • Redesigned after Liam ERD:
    • compact table cards with key icons;
    • routed relationship lines;
    • hovering or selecting a table highlights the tables it is keyed to and fades the rest.
  • Columns are edited in a tooltip next to the row. Its type field is a combobox. It lists the types already used in the schema and also accepts a new type.
  • Column editing needs an id on <dpk-component-er-diagram>, so the draft can record it.
• User story map: each story has a STORY-n key that is unique on the map. The key is shown on the card and in the story panel, and pressing it copies it. #story= navigation and the dependency picker accept it. Stories may set an optional number. ADD_STORY carries the number the UI gave the new story. (#11)
• Whiteboard: copy and paste duplicates the selected items. (#9)

Bug Fixes

• The hand-off dock floats over an open supplement and no longer shrinks it. Diagram zoom and legend controls move up so the dock does not cover them.
• User story map: a deleted story's number is never given to a new story.

v0.1.0

Breaking Changes

• dpk-template-grill and the templates/grill.js entry are removed. Questions are now a shell feature of every template: put a page's questions and history in a script[data-dpk-grill] block beside the base data of another template (for example Plain). Answers are recorded as the core answer action on grill:<id> targets, and data-grill-questions marks get Q badges.
• The memo slot is no longer shown. Wrap each piece in <section slot="supplement" data-name="…">. Supplements line up in a bar at the bottom of the main column and open one at a time; an unnamed one is labelled "Memo". The console warns while slot="memo" remains.
• USM burndown measure: the state field weighted: boolean is replaced by measure: 'stories' | 'points' | 'weighted' (defaults to points when estimates exist, otherwise stories), the SET_WEIGHTED action by SET_MEASURE, and the unit navigation parameter is gone.

Features

Review and shell (all templates)

• The header pins two toggles, Changes and Review comments, each with its own count. dpk-component-comment-panel takes a section (changes / comments); notes="changes" opens the rail at the changes.
• The review rail now floats in a popover below its toggles instead of taking a column, so the main column keeps its width. It stays open while the reader works and closes from its toggle or Escape.
• Templates can offer switches through settings(state), shown behind a gear in the shared header. Header icon buttons show their label on hover or focus.
• Cancel beside a text field now discards the typed text; Escape still keeps it.
• Tighter header.

Prototype

• A comment on a UI element can be a note instead of feedback: notes are kept as base data, shown as badges on the element (not in the app view), and can be rewritten in place or deleted.

USM (User Story Mapping)

• Story comments on the map are kept as base data (stories[].comments[], via ADD_STORY_COMMENT / DELETE_STORY_COMMENT), separate from review comments. Cards show both counts.
• Choose which status counts as done on the statuses tab (doneStatusId, SET_DONE_STATUS); it and every later status count as done for blockers, the map, the burndown and the progress ring.
• Finished stories are hidden on the map by default; a "Show Done" checkbox (done=show navigation) brings them back.
• The burndown asks for one measure — stories, story points, or points weighted by status — and shows only that measure's settings. Status weights are optional, read as parts of 10, and edited on a bar with draggable lines. The critical path follows the same measure.
• Dependency pickers are searchable comboboxes, navigable with Ctrl+N / Ctrl+P.
• Optional features move from the tab-bar menu into the header settings.

Bug Fixes

• Supplements fold and reopen from the chevron.
• A long element name no longer scrolls a popover sideways.
• The USM map fills the page down to its bottom edge.

v0.0.18

Features

• usm: Drag an activity group or a step to reorder the columns. The whole column (its head and every cell under it) lifts as one piece, and it can be dropped on any part of another column, which lights from its head to its last cell. Steps move only inside their own activity.
• usm: A "Critical path" toggle in the map toolbar highlights the chain of unfinished stories with the most work left and dims the rest. It is navigation (highlight=critical-path), so it can be linked.
• usm: The page tabs keep to one line; the ones that do not fit fold behind a "…" menu, while the current tab always stays shown.

Bug Fixes

• usm: The map filters stay in a sticky row under the tabs while the map scrolls.
• usm: The empty Labels page now only says that labels can be added.

Improvements

• usm: Tighter vertical spacing on the map's backbone rows, the page tabs and the filter row, so more of the map fits on screen.

Full Changelog: v0.0.17...v0.0.18

v0.0.17

Features

• USM: dependencies between stories. A story can list the stories it waits on in stories[].blockedBy (self-references, unknown ids and cycles are rejected). Cards show how many stories a story blocks or waits on, and the story panel edits both directions (ADD_STORY_BLOCKER / REMOVE_STORY_BLOCKER).
• USM: estimates and a weighted burndown. Stories take an estimate from a scale in estimates[] (stories[].estimateId; a story without one counts as 1 point). Each status can carry a weight for the effort of moving past it, and milestones a dueDate. A new Burndown tab charts the weighted remaining points per milestone from recorded snapshots[], with an ideal line to the due date, today and time gridlines, and an interactive readout on hover or from the keyboard.
• USM: members and assignees. A team is listed in members[] and each story can have one assignee (stories[].assigneeId). Members are managed on their own tab, cards show the assignee's avatar, and the story panel picks the assignee. member:<id> is a new reference target for comments and change notices.
• USM: optional features. Estimates with the burndown, and members with assignees, are optional: a base turns them on with features: ["estimates", "assignees"], and both are off by default. Readers can switch each one from the new "Features" menu in the board bar, which is recorded as a SET_FEATURE draft action. Turning a feature off only hides it; its data stays in the base.
• USM: one-row map filter. The map filter is a single row of dropdowns for status, label and, when enabled, estimate and assignee, each with per-option counts. Filters are kept in the URL hash.

v0.0.16

Features

• USM: free-form labels. Stories can carry free-form labels, listed on their own tab so the map itself stays uncluttered.
• USM: keyboard access to the story panel. The story panel can be reached and dismissed from the keyboard.
• Prototype: screen actions. A screen can declare actions (fill in sample values, click elements) that the reader runs from the stage's menu on the rendition on screen; the mock hears a dpk-action event so its own script can do the rest.
• Change notices: "Mark all as read". The change list and the toasts offer a single button that marks every unread change as read.

Bug Fixes

• Change notices announce only what a reader has not seen. The change log is now an append-only history (revisions): each regeneration appends one version with only that round's changes. A first-time reader is told about the latest version only, a returning reader about the versions since their last visit, and the list groups changes by version. The previous single-version form is still read, and stored read state migrates automatically.

Docs

• The "Change notices" section of the docs and the Artifact revising guide now tell agents to append a version per regeneration instead of rewriting the log.

Full Changelog: v0.0.15...v0.0.16

v0.0.15

Bug Fixes

• Templates fill the window when the host has no height. Previously only prototype and grill fell back to the viewport height; every other template grew with its content, leaving a band below the shell on short pages (visible as a white strip in a Claude Artifact's dark theme) and scrolling the header and memo away on long ones. All templates now fill the window (minus the safe-area insets a Claude Artifact adds). A host that sets a height still wins.
• Change notices stay unread until you show them. Opening the bell's list used to mark every unread change as seen, so showing one change cleared them all. Now opening the list only marks changes that have no Show target; a change with a Show stays unread until the reader follows it.
• The prototype Base data example parses again. The documented example put screen directly on a step, which the current schema rejects, so a page copied from it opened to the error banner. Every template's Base data example is now checked against that template's parser.

Documentation

• Publishing as a Claude Artifact is now the default when the Artifact tool is available, and the Artifact guide lives in the versioned docs (docs/claude-artifact.md). It states that the kit works inside the Artifact viewer, that its rules override generic Artifact design guidance, and that the comments capability must be declared on the first publish (otherwise Send to Claude is missing; republish to recover).
• A single "Page height" section documents the form (height: 100%) that works both locally and in an Artifact. Samples use it too.
• The "Agree on → Template" table moved from the skill to docs/index.md, so the list of templates always matches the version you load.

Full Changelog: v0.0.14...v0.0.15