Skip to content

[epic] Pre-release (v0.5.0) hardening batch — audit follow-ups #279

Description

@sobechestnut-dev

Source: a 4-dimension pre-release audit (GitHub backlog, documented gaps, test coverage, UX/DX) run from a read-only planning session. This is the entry point for the main coding session to pick up the batch.

The codebase is healthy (1 TODO, 1 intentional skip). Findings cluster in release mechanics, the newest v0.4.0 CNC/laser surface, doc accuracy, and demo/adapter polish. Goal: turn the currently-thin next release (two camera changesets only) into a substantive, honest v0.5.0.

Themed PRs → dev

Non-PR tasks

Sequencing

  1. Land the themed PRs ([docs] Refresh stale compatibility matrix + README adapter count (Q1, Q4) #273[test] Harden CNC/laser parsing coverage — adversarial tier + hostile canned cycles (M1, M2, M5) #277) on dev, each carrying its own changeset where noted.
  2. [housekeeping] Close completed milestones M0–M5, dedupe label pairs (Q5) #278 housekeeping anytime (independent).
  3. Then [release] Regenerate version PR to v0.5.0 — #271 is stale and drops the #268 changeset #272 — verify/regenerate the version PR → v0.5.0, all changesets consumed, CHANGELOGs complete.

Checklist

Two items are agent-reported with file refs but unconfirmed by hand — verify before coding: #274 (GcodePreview.svelte:71 non-reactivity) and #275/M4 (canvas tabindex + OrbitControls keys absence).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions