chore(release): 0.42.6

[jobordu]

Release 0.42.6

CI/CD testing release

Checklist (all verified locally before push)

• package.json bumped to 0.42.6
• package-lock.json synced (npm install --package-lock-only)
• CHANGELOG entry for [0.42.6]
• terminal.svg regenerated
• npm ci --ignore-scripts passes
• check:assets passes
• lint:isolation passes

After merge

CI will automatically: test -> tag v0.42.6 -> create GitHub Release -> publish to npm @latest -> align @next dist-tag

Verify after release:

npm dist-tag ls @nforma.ai/nforma

Summary by CodeRabbit

• Chores

  • Version bumped to 0.42.6
  • Cleaned up planning snapshot metadata to remove merge artifacts

• Documentation

  • Added changelog entry noting release pipeline validation

• Tests

  • Made a requirements-dependent test suite skip when local requirement data is absent to avoid false failures

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 10d8fc7b-e901-4dd4-96fa-9bfbbd8cae32

📥 Commits

Reviewing files that changed from the base of the PR and between a15da73 and 65c4914.

📒 Files selected for processing (2)

• .planning/formal/requirements.json
• test/install-virgin.test.cjs

💤 Files with no reviewable changes (1)

• .planning/formal/requirements.json

---

📝 Walkthrough

Walkthrough

Bumped project version to 0.42.6, added an Unreleased changelog entry about CI release scripts validating the full release pipeline, cleaned merge-conflict artifacts in .planning/formal/requirements.json, and made the test/install-virgin.test.cjs suite conditional on the presence of the local requirements file.

Changes

Cohort / File(s)	Summary
Version & Changelog CHANGELOG.md, package.json	Added Unreleased entry for v0.42.6 noting release scripts (prepare-release.sh, release.sh) now validate the full release pipeline; bumped version to 0.42.6.
Requirements snapshot .planning/formal/requirements.json	Updated snapshot metadata (aggregated_at, content_hash, frozen_at) and removed embedded Git merge conflict markers, restoring valid JSON content.
Tests — conditional execution test/install-virgin.test.cjs	Made the "TUI data loading: requirements" test suite conditional on existence of .planning/formal/requirements.json by checking filesystem presence and passing skip: !hasLocalRequirements to describe.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Poem

🐇 I hopped through lines and smoothed a fight,
I nudged the version up just right,
Cleared the crumbs that git left strewn,
Tests now wait until the file's in tune,
Ready to release beneath the moon. 🌙

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description deviates significantly from the required template, missing key sections like 'What', 'Why', 'Testing' checkboxes, and 'Breaking Changes'.	Restructure the description to match the template with 'What', 'Why', 'Testing', and 'Breaking Changes' sections; preserve the custom release checklist as supplementary detail.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes the main change: a release version bump to 0.42.6, following conventional commit format.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch release/0.42.6

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}