Skip to content

fix: implement robust geometry alignment and auto return#19

Closed
w1ne wants to merge 2 commits intodevelopfrom
fix/extrude-visibility-alignment
Closed

fix: implement robust geometry alignment and auto return#19
w1ne wants to merge 2 commits intodevelopfrom
fix/extrude-visibility-alignment

Conversation

@w1ne
Copy link
Copy Markdown
Owner

@w1ne w1ne commented Feb 14, 2026

This PR fixes visibility issues with extrusions and ensuring strict index alignment between the worker and the UI. It also introduces the Auto-Return mechanism.

w1ne added a commit that referenced this pull request May 2, 2026
* docs(spec): v0.1.0 NORTHSTAR re-baseline + first public ship design

Re-version to v0.1.0 (NORTHSTAR-strict honest baseline). Delete 34 cruft tags. Publish to npm. Add smoke test + acceptance demo. SKILL.md install path. README quickstart rewrite. Close stale PR #19.

* docs(spec): v0.1.0 spec — MIT license + Path 1 strategic positioning

Switch license from BUSL-1.1 to MIT. Add A9 four-anchor positioning (open, MCP-native, AST-edit-primacy, diagnostic-rigorous). Add S9 to scope. CHANGELOG positioning section. Strip residual competitor refs. Lock open question 3.

* docs(plan): v0.1.0 NORTHSTAR re-baseline implementation plan

9 tasks (Task 0 branch + draft PR; Tasks 1-7 prep; Task 8 cutover). Each task has bite-sized steps with exact commands and pass criteria. Task 8 includes a CONFIRMATION GATE before destructive tag deletion + post-publish smoke test + end-to-end live verify on a fresh shell.

* chore(release): add MIT LICENSE and npm files manifest

- LICENSE: MIT, copyright Andrii Shylenko
- package.json: add files=[dist/cli, README.md, LICENSE] to scope npm publish payload
- Verified tarball <10 MB via npm pack --dry-run

Part of v0.1.0 NORTHSTAR re-baseline (spec: docs/superpowers/specs/2026-05-02-v0.1.0-northstar-rebaseline-design.md).

* feat(examples): add v0.1 acceptance demo (bracket with hole + fillet)

The exact .kcad.ts script v0.1 must successfully run end-to-end —
NORTHSTAR open question #1 (open since 2026-04-29). Used by:

- README quickstart (Task 4 of v0.1.0 plan)
- scripts/smokeTest.sh (Task 7 of v0.1.0 plan, post-publish verification)
- GitHub Release artifact (Task 8 of v0.1.0 plan)

Exercises: param() with 3 axes (Width/Height/Thickness), box primitive,
cylinder primitive, .translate(), .subtract(), .fillet().

* docs(skill): add npm install path to SKILL.md

New '## Installation' section between intro and Coordinate System.
Replaces the implicit clone-the-repo install path with a one-line
'npm install -g kernelcad'. Drift sentinels still pass (they assert
name presence, not section ordering).

Part of v0.1.0 NORTHSTAR re-baseline.

* docs(readme): flat install + first-script quickstart for v0.1.0

Replace the multi-step 'Prerequisites / Installation / Clone' wall
with a one-line install + drop-this-in-a-file demo + run commands.
Web-app dev workflow moves to '## Contributing'.

Removed stale sections:
- ## Usage (referenced replicad.Sketcher API not exposed by kernelCAD)
- ## Architecture (web-app internals; not relevant to npm consumers)
- ### Documentation Index (linked to files moved to archive/doc/)

License section now references LICENSE file properly.

Part of v0.1.0 NORTHSTAR re-baseline.

* docs(readme): strip pre-existing leading whitespace from intro

Lines 2-18 had a single leading space (pre-existing from initial commit).
CommonMark renders these correctly anyway, but column-0 markdown is the
convention. Fixed alongside the v0.1.0 README polish (commit eae85d9).

No semantic change. Heading structure, content, code blocks all unchanged.

* docs(changelog): v0.1.0 re-baseline entry

First entry above the rc.17 history. Documents:
- The version reset rationale (NORTHSTAR-strict, every v0.N.0 = one NORTHSTAR module)
- What ships in v0.1.0 (Foundation contract + bonus surface from later modules)
- Diagnostic surface (53 codes, HINTS-enforced)
- Strategic positioning (open, MCP-native, AST-edit-primacy, diagnostic-rigorous)
- License (MIT)

The rc.1-rc.17 history below stays as development record.

* docs(changelog): disambiguate legacy v0.1.0 header

Pre-existing entry from 2026-04-29 (internal architecture milestone
that was never published) shared the heading 'v0.1.0' with the new
public release entry from Task 5. Renaming the legacy heading to
'v0.1.0 (internal architecture milestone, never published) — 2026-04-29'
preserves the architectural-milestone history while making the new
public release the unambiguous v0.1.0.

Body content of the legacy entry untouched.

* release(v0.1.0): private:false + version 0.1.0

NORTHSTAR-strict re-baseline. Every v0.N.0 from this point corresponds
to one NORTHSTAR module fully delivered. The 17-rc cycle ends here.

private:false unblocks 'npm publish' for Task 8.

qc:full: lint + typecheck + vitest pass; Playwright env failure
acceptable per established precedent (browsers not installed in
this environment).

Part of v0.1.0 NORTHSTAR re-baseline.

* chore(release): smoke test for npm install path

scripts/smokeTest.sh runs a clean node:22-slim container, installs
kernelcad@latest from npm, evaluates examples/bracket-with-hole.kcad.ts,
exports STL, and verifies the binary header forensic stamp.

JSON evaluate shape: parses .ok (boolean), not .status. Matches the
actual CLI output verified during Task 2.

Invoked manually post-publish in Task 8. Not gated in CI for v0.1.0
(CI sandbox + Docker-in-CI is out of scope per spec).

---------

Co-authored-by: w1ne <w1ne@users.noreply.github.com>
@w1ne
Copy link
Copy Markdown
Owner Author

w1ne commented May 2, 2026

Closing — predates the rc.6 query-first topology refactor and the rc.13 mirror/reflect surface; the underlying alignment behavior is now handled differently. Reopen if the original symptom recurs. Branch ref preserved (not deleted).

@w1ne w1ne closed this May 2, 2026
w1ne added a commit that referenced this pull request May 3, 2026
* docs: corpus expansion #19 v0.2 tracked-refs spec + plan (DRAFT)

* feat(eval): 3 v0.2 tracked-refs corpus tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant