Skip to content

v0.10.2

Choose a tag to compare

@daus95 daus95 released this 19 Aug 11:52
· 26 commits to main since this release
86e1d2a

Added

  • A Back button in the toolbar when a Clarification or Specification file is open. Opening
    a clarification file — from the Clarification Overview table, the sidebar's Clarification
    file list, or the Home page's "files needing clarification" list — left no way back to the
    Clarification Overview page short of clicking "Clarification" in the sidebar tree, which
    wasn't an obvious "go back" affordance. A Back arrow now sits at the start of the toolbar
    whenever a file is open (both Clarification and Specification), returning to that section's
    overview and still prompting to discard unsaved changes first, same as before.

Changed

  • Clarified the Home page's "close working folder" button. It previously showed only a bare
    X icon relying on a hover tooltip, easy to mistake for dismissing the panel rather than
    unlinking the workspace. It now carries a visible "Close" label alongside the icon, styled as
    a bordered pill consistent with the rest of the workspace panel.

  • Moved "Clear All" off the Home page to Settings → Maintenance → Danger Zone. It previously
    sat directly beneath the Start Implementation button, one step below buttons that get clicked
    repeatedly during a normal run — an easy target for a stray click on a destructive,
    unrecoverable action. It's now under its own red-bordered "Danger Zone" group in Maintenance,
    alongside Restart Server. Behavior (including the confirmation dialog) is unchanged.

Fixed

  • Fixed six self-contradictions in the POS example PRD.
    examples/02-web-app-with-db/PRD.md ships as a reference PRD that is meant to keep the first
    clarification round short, but it disagreed with itself: the discount could be a percentage or
    a fixed amount while Sale had a single discount column to hold it; "total due" drove both
    the change calculation and the paid-amount validation without ever being defined; the Cashier
    had "POS/checkout access only" in the business process yet a Dashboard in the UI section, and
    was promised a per-shift history with no Shift entity anywhere in the data model; the void
    step was "same-day" in its heading only; Stock In recorded a supplier and a receipt price that
    StockMovement had no column for; and the receipt "prints" despite a non-goal ruling printers
    out of scope. All six are now resolved in the document — totals arithmetic spelled out, the
    discount modelled as type/value/amount, a per-role Dashboard, the same-day void rule stated in
    the step itself, and supplier + unit cost added to StockMovement — with the ERD, the
    validation list and the acceptance criteria updated to match. The tech stack, which hedged
    every choice with "or an equivalent", is now pinned: React + Vite, Node.js/Express,
    PostgreSQL + Prisma, and JWT rather than "session or JWT".

Full changelog: v0.10.1...v0.10.2