Feat/wall merging - #4
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
dallasteele
added a commit
to dallasteele/halofire-studio
that referenced
this pull request
Apr 22, 2026
Prepares the release-facing documentation for the v0.1.0 ship. - **CHANGELOG.md** — prepended the Keep-a-Changelog 1.1.0 header plus an `[Unreleased]` slot and a full `[0.1.0] — 2026-04-21` entry. Preserved the existing 0.4.x internal pre-release history below a `## Pre-release history` divider so the session-by-session changelog is not lost. The 0.1.0 entry is organized per the format's section guide: Added (Pascal fork + 12 node types, 10-stage Python pipeline, 40-part OpenSCAD catalog, `.hfproj` + autosave, Tauri 2 shell, sheet-set renderer → PDF/DXF/DWG, Auto-Design against the 1881 truth fixture, Pascal tools + InstancedCatalogRenderer, 403 Py + 274 Playwright + parity CI) / Changed (Turbopack NFT hygiene, Biome lint zero-state) / Fixed (PDF intake polygon bug + 12-test golden lock) / Known limitations (DoD-pascalorg#4 cold-launch, DoD-pascalorg#11 real 2nd-project, DoD-pascalorg#12 clean-VM MSI, LiveCalc re-READ vs re-SOLVE, OpenSCAD arm64) / Upgrade notes. - **docs/RELEASE_NOTES_v0.1.0.md** (new, 167 lines) — a ship note targeted at fire-protection engineers evaluating the product, not developers. Sections: What HaloFire Studio is, Headline features, Install + first bid, Known limits, What's next, Thanks. Tone is honest: we name the auto-design's measured error against the 1881 truth (−0.8% head count, +10.5% bid), we call out the four open DoD rows, and we thank Wade for the patience that made the cruel-test scoreboard possible. - **README.md `## Ship state`** — bumped 48/53 → 49/53 (counts the 0a943a6 Codex-sweep + f89b199 synthetic 2nd-project rows that shipped after the last README edit), corrected the test counts (403 Py / 274 Playwright, reflecting the current state from BUILD_LOG entry 31), added a Lint row (0/0 post-sweep), and linked CHANGELOG.md + RELEASE_NOTES_v0.1.0.md. No verification gates affected by this commit — documentation only. Editor build + lint unchanged. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
dallasteele
added a commit
to dallasteele/halofire-studio
that referenced
this pull request
Apr 22, 2026
Adds the tag-and-push release script and documents the invocation so the v0.1.0 ship is a single-command gesture when DoD-pascalorg#4/11/12 close. - **scripts/release.sh** (executable, 42 lines) — annotated-tag release script: - Accepts `vMAJOR.MINOR.PATCH[-prerelease]`, rejects other formats with a clear error. - Validates a clean working tree (no staged, unstaged, or untracked changes) before tagging — prevents tagging "a tag plus some unsaved scraps". - Rejects re-tagging an existing version. - Creates an annotated tag with message "HaloFire Studio $VERSION" and pushes to `origin`. - Prints the GitHub Actions URL where the MSI / DMG / AppImage matrix builds land (.github/workflows/build-desktop.yml is triggered by tag push). Not wired into root package.json — the existing `release` script there triggers a different workflow (`release.yml` for the viewer+core JS packages). `scripts/release.sh` is invoked directly: `bash scripts/release.sh v0.1.0`. - **docs/CODEX_SWEEP_READY.md** — appended a "Release invocation" section at the bottom so the review doc and the release doc cross-reference (the reviewer can see how the ship completes from the same page they opened to read Codex's five questions). DRY-RUN: the tag is *not* created by this commit. `git tag v0.1.0` is the user's call, executed via `bash scripts/release.sh v0.1.0` when ready. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
3 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.