List view

• v13.2

  A Harness You Can Download and Run — scope forming via the D#14561 weighting round; cornerstones linked post-fold

  No due date

  •3/20 issues closed
  15% complete17 open3 closed

• v13.1

  First post-v13 release roadmap. Scope = the LOCKED main cornerstones (the harness phase-1-completion slice, ~50-100 main PRs as a planning target) — NOT a hard cap: headroom for the always-present emergent (bugs + workflow/MX friction→gold). Milestone-based, ~7-10 day rhythm. Cornerstones + rationale in the #13012 v13.1 roadmap checkpoint. Epic-owners: assign your epic's v13.1-slice subs here (epic-ownership, not ticket-grab).

  No due date

  •52/53 issues closed
  98% complete1 open52 closed

• Harness M4: Wow Effect

  The full arc demo-able cold to a new user: login → widget → dashboard → multi-window split + live agent mutation + streaming chat riding the worker topology. Definition sharpens as M1-M3 land. Epic #13012.

  No due date
  0% complete0 open0 closed

• Harness M3: First Neo Dashboard

  From one widget to a composed dashboard: multiple widgets, shared state wiring, blueprint persistence (serialize the live design). Epic #13012.

  No due date

  •1/1 issues closed
  100% complete0 open1 closed

• Harness M2: First Neo Widget

  The canonical demo: chat pane → "build me a neo grid" → a separate pane that can become its own browser window — dummy grid (5 columns), live-mutable. Impedance match + multi-window in one gesture. Epic #13012.

  No due date

  •3/3 issues closed
  100% complete0 open3 closed

• Harness M1: Login

  A downloaded harness signs the user in — native Anthropic-account login in the Electron shell (bring-your-harness via extended-NL as the parallel entry). First end-user product checkpoint of Epic #13012.

  No due date

  •1/2 issues closed
  50% complete1 open1 closed

• 11.12.0

  No due date

  •1/1 issues closed
  100% complete0 open1 closed

• neo.d.ts - Typescript definitions for all neo framework classes

  To make neo development easier and more accesible, Typescript definition files for all {core parts of the framework}* are provided and consumed via typedef-comments. The workspace tooling (`npx neo-app`, `create-class`, etc.) use the typedef-comments instead of inline JSDoc types.

  No due date

  •2/2 issues closed
  100% complete0 open2 closed

• Neo-Material Component Library v0.1

  An initial set of Material Component following the design are implemented as neo-components and can be used in any neo application. This doesn't necessarily include all existing Material components from the design spec, but a {base set}* that is commonly used when creating business applications. The created components are theme-able. The tooling for neo workspaces (e.g. `npx neo-app`) are upgraded so that out-of-the box usage of the Neo-Material component library is possible.

  No due date

  •1/1 issues closed
  100% complete0 open1 closed