chore(release): prepare v0.1.1

[flyingrobots]

Linked Issue

• Part of Release gate: v0.1.1 #624

Why

This is the release-prep PR for Wesley v0.1.1. Releases must be cut from tagged main, so version metadata and changelog state need to land on main before the signed v0.1.1 tag is created.

Changes

• Bump the root package version to 0.1.1.
• Bump the Wesley Rust crates and workspace path dependency constraints to 0.1.1.
• Move the accumulated unreleased changelog entries under 0.1.1 - 2026-06-26 and update compare links.

Risk

Low. This is metadata and changelog release prep only; no runtime or compiler behavior changes are introduced here.

Backout

Revert this PR before tagging if release-prep validation fails. After a public tag/publish, do not rewrite history; follow up with a corrective patch release.

Testing

• cargo check --workspace --all-targets
• cargo xtask package-crates --version 0.1.1
• cargo xtask release-check
• pnpm install --lockfile-only --frozen-lockfile
• cargo xtask legacy-preflight
• cargo xtask docs-check
• pnpm run lint
• pnpm run preflight
• git diff --check
• pre-push Rust product preflight
• pre-push JavaScript package preflight

Release Gate

#624 remains open until this PR lands, synced main passes release guards, and the v0.1.1 tag is cut from main.

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR bumps release-related versions to 0.1.1 across the Rust workspace and npm package, updates internal dependency version constraints, and adds the matching changelog entry and compare links.

Changes

v0.1.1 release bump

Layer / File(s)	Summary
Changelog release entry CHANGELOG.md	Adds the 0.1.1 changelog section and updates the release compare references.
Package version fields crates/wesley-core/Cargo.toml, crates/wesley-emit-*/Cargo.toml, crates/wesley-cli/Cargo.toml, crates/wesley-holmes/Cargo.toml, package.json	Bumps the package version fields in the Rust crates and npm manifest to 0.1.1.
Path dependency version pins crates/wesley-cli/Cargo.toml, crates/wesley-emit-codec/Cargo.toml, crates/wesley-emit-rust/Cargo.toml, crates/wesley-emit-typescript/Cargo.toml	Updates workspace path dependency version constraints to 0.1.1.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related issues

• Release gate: v0.1.1 #624: The PR updates the project to the v0.1.1 release version referenced by the issue.

Possibly related PRs

• flyingrobots/wesley#506: Both PRs update the same release/version fields across Rust manifests and changelog compare links.

Poem

A rabbit hops by, ears in the breeze,
"0.1.1!" sings the changelog trees.
Rust bits and notes now match with grace,
A tidy little version chase. 🐇

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly matches the release-prep version bump and changelog update.
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.
Description check	✅ Passed	The PR description covers the key release-prep sections, including linked issue, why, changes, risk, backout, testing, and release gate.

✨ 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/v0.1.1

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[github-actions]

🔍 The Case of Pull Request #640

Plain-English Readout

• Holmes (evidence investigation): Holmes says this change looks ready to ship.
• Watson (independent verification): Watson found verification concerns. Most important concern: No evidence citations were available for trust analysis.
• Moriarty (trend forecast): Moriarty does not have enough historical data yet to forecast readiness.

Suggested next actions

1. Resolve Watson’s verification concerns before trusting the Holmes verdict as final.

📚 Glossary (what the Holmes terms mean)

• HOLMES: Wesley’s main evidence investigation. It decides whether the cited proof is strong enough to justify shipping this commit.
• WATSON: An independent verification pass. It checks Holmes’s citations and score math instead of trusting them blindly.
• MORIARTY: A readiness forecast over time. It is advisory trend analysis, not the release gate itself.
• Schema coverage score (SCS): How much of the schema has direct supporting evidence across generated artifacts and cited proof.
• Test confidence index (TCI): How much test evidence exists for constraints, policies, relationships, and operations.
• Migration risk index (MRI): How risky the schema change is to roll out. Lower is better.
• Evidence trust: Whether the report is backed by exact citations, whole-file citations, or coarse references. Weak trust means the claim may be directionally right but not specific enough to trust blindly.
• Citation quality: A count of exact line-span citations versus whole-file or coarse references.
• ELEMENTARY: Ready to ship based on the current evidence.
• REQUIRES INVESTIGATION: More work or review is needed before shipping.
• YOU SHALL NOT PASS: Do not ship this change in its current state.

---

🕵️ SHA-lock HOLMES full report (click to expand)

🕵️ SHA-lock HOLMES Investigation

• Generated: 2026-01-01T00:00:00.000Z
• Commit SHA: b2084ef
• Bundle Version: 2.0.0

⚠️ Evidence valid only for commit b2084ef

🔍 Executive Deduction

"Watson, after careful examination of the evidence, I deduce..."

Weighted Completion: ██████████ 95.0%
Scores: SCS 95.0% · TCI 90.0% · MRI 10.0%
Verification Status: 2 claims verified
Citation Quality: 2 exact · 0 whole-file · 0 coarse
Evidence Trust: strong
Ship Verdict: ELEMENTARY

🧩 SCS Breakdown

Component	Score	Coverage
Sql	100.0%	1.00/1.00
Types	100.0%	1.00/1.00
Validation	100.0%	1.00/1.00
Tests	100.0%	1.00/1.00

🧪 TCI Breakdown

Component	Score	Coverage	Note
Unit Constraints	100.0%	1/1	N/A
Unit Rls	100.0%	1/1	N/A
Integration Relations	100.0%	1/1	N/A
E2e Ops	90.0%	9/10	N/A

⚠️ MRI Breakdown

Component	Risk Share	Points	Count
Drops	0.0%	0	0
Renames Without Uid	0.0%	0	0
Add Not Null Without Default	100.0%	1	1
Non Concurrent Indexes	0.0%	0	0

📊 The Weight of Evidence

"Observe, Watson, how not all features carry equal importance..."

Element	Weight	Status	Evidence	Strength	Deduction
schema	5	✅ Exact SQL & tests	test/fixtures/examples/.wesley-cache/shipme-fixture/tests.sql:1-1@b2084ef	exact	Elementary!

🚪 Security & Performance Gates

"Elementary security measures, Watson..."

Gate	Status	Evidence	Holmes's Ruling
Migration Risk	✅	MRI: 10.0%	"Trivial risk"
Test Coverage	✅	TCI: 90.0%	"Excellent coverage"
Sensitive Fields	✅	0 fields	"All secured"
Evidence Quality	✅	2 exact · 0 whole-file · 0 coarse	"All 2 citations resolve to exact line spans."

📋 The Verdict

✅ ELEMENTARY - Ship immediately!
"The evidence is conclusive. No mysteries remain."

Signed and sealed,

• S. Holmes, Consulting Detective

[END OF INVESTIGATION FOR COMMIT b2084ef]

🧵 Command Run

• Run ID: run-69b2e857-70dc-486d-bd7b-362d600e4ce8
• Transmutation: holmes-investigate
• Command: investigate
• Status: completed
• Ledger: /home/runner/work/wesley/wesley/test/fixtures/examples/.wesley-cache/ledger

---

🩺 Dr. WATSON full report (click to expand)

🩺 Dr. Watson's Independent Verification Report

Medical Examination of Evidence

• Examination Date: 2026-06-26T00:54:39.111Z
• Patient SHA: b2084ef

🔬 Citation Verification

"Let me examine each piece of evidence independently..."

• Citations Examined: 2
• Verified: 0 ✅
• Failed: 0 ❌
• Unable to Verify: 2
• Exact Subrange Citations: 0
• Whole-file Citations: 0
• Coarse Citations: 0
• Evidence Trust: missing
• Trust Note: No evidence citations were available for trust analysis.

Verification Rate: 0.0%

📊 Mathematical Verification

"I shall recalculate Holmes's arithmetic..."

Holmes claimed SCS: 95.0%
Watson calculates: 100.0%
Difference: ⚠️ Significant

🔍 Consistency Analysis

"Checking for contradictions in Holmes's deductions..."

✅ No logical inconsistencies detected

🩺 Dr. Watson's Medical Opinion

VERIFICATION: CONCERNS NOTED ⚠️

"While Holmes's methods are generally sound, I have noted some"
"discrepancies that warrant further investigation. No evidence citations were available for trust analysis."

Respectfully submitted,

• Dr. J. Watson, M.D.
  Medical Examiner & Verification Specialist

🧵 Command Run

• Run ID: run-378bad44-bda4-4e2c-a25c-b5c19c05db78
• Transmutation: watson-verify
• Command: verify
• Status: completed
• Ledger: /home/runner/work/wesley/wesley/test/fixtures/examples/.wesley-cache/ledger

---

🔮 Professor MORIARTY full report (click to expand)

🧠 Professor Moriarty's Temporal Predictions

The Mathematics of Inevitability

• Analysis Date: 2026-06-26T00:55:07.496Z

INSUFFICIENT DATA

"I require at least two data points to predict the future."
"Run Wesley generate multiple times to build history."

🧵 Command Run

• Run ID: run-2e63060d-9e4a-425e-bf5d-df1bba1a8796
• Transmutation: moriarty-predict
• Command: predict
• Status: completed
• Ledger: /home/runner/work/wesley/wesley/test/fixtures/examples/.wesley-cache/ledger

---

Machine-readable reports: holmes-report.json · watson-report.json · moriarty-report.json (see workflow artifacts).

---

Filed at 221B Repository Street

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 8085ab0c92

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Update release-facing docs before tagging v0.1.1

Creating the 0.1.1 changelog section here makes this tree the source for the v0.1.1 tag, but the release guard still requires an exact ## What's New in v0.1.1 README heading and a whole-version v0.1.1 reference in docs/TECHNICAL_TEARDOWN.md (xtask/src/main.rs:455-459, :971-979, :1022-1029). Those docs still only describe the 0.1.0 release/no v0.1.1, so cargo xtask release-guard --tag v0.1.1 will fail once the tag is created and the release prep cannot be cut without another change.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Clear v0.1.1 backlog blocker before release prep

With the release version now set to 0.1.1, the pre-tag gate is blocked: cargo xtask release-prep-guard --version 0.1.1 calls check_release_tracker_clear, whose backlog scan rejects any docs/method/backlog file containing this exact version, and it currently fails on docs/method/backlog/bad-code/README.md because that signpost still says v0.1.1. That prevents the required release-prep guard from passing before the tag can be cut.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Keep xtask in the workspace version bump

When this release prep bumps the Rust workspace to 0.1.1, it leaves the xtask workspace member at 0.1.0 in both xtask/Cargo.toml and Cargo.lock. The release policy says workspace members must not drift independently, so the v0.1.1 source snapshot will report mixed workspace versions via cargo metadata even though this commit is the release version bump.

Useful? React with 👍 / 👎.