Skip to content

chore(release): v0.0.3#506

Merged
flyingrobots merged 2 commits into
mainfrom
release/v0.0.3
May 14, 2026
Merged

chore(release): v0.0.3#506
flyingrobots merged 2 commits into
mainfrom
release/v0.0.3

Conversation

@flyingrobots
Copy link
Copy Markdown
Owner

@flyingrobots flyingrobots commented May 14, 2026

Summary

  • bump the published Wesley Rust crates to 0.0.3
  • move runtime optic compiler work into the 0.0.3 changelog section
  • add the README release summary and update install docs
  • satisfy the release clippy gate for runtime optic traversal helpers

Validation

  • git diff --check
  • cargo fmt --check
  • cargo xtask docs-check
  • cargo check --workspace --all-targets
  • cargo test --workspace --all-features
  • cargo clippy --workspace --all-targets -- -D warnings
  • cargo xtask release-check
  • cargo audit
  • cargo xtask release-prep-guard --version 0.0.3
  • cargo xtask package-crates --version 0.0.3
  • cargo xtask preflight
  • pnpm run preflight

Summary by CodeRabbit

  • Documentation

    • Added "What's New in v0.0.3" section to README with release highlights
    • Updated CHANGELOG with v0.0.3 release information
    • Updated installation instructions across documentation
  • Chores

    • Bumped all package versions to 0.0.3

Review Change Stack

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 14, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 3aaa8aa3-0df3-4220-a827-83bb66f742a8

📥 Commits

Reviewing files that changed from the base of the PR and between 49d4632 and c51735f.

⛔ Files ignored due to path filters (1)
  • Cargo.lock is excluded by !**/*.lock
📒 Files selected for processing (10)
  • CHANGELOG.md
  • README.md
  • crates/wesley-cli/Cargo.toml
  • crates/wesley-core/Cargo.toml
  • crates/wesley-core/src/adapters/apollo.rs
  • crates/wesley-emit-rust/Cargo.toml
  • crates/wesley-emit-typescript/Cargo.toml
  • docs/BEARING.md
  • docs/ENTRYPOINTS.md
  • docs/GUIDE.md

📝 Walkthrough

Walkthrough

This pull request releases v0.0.3 across all wesley crates with manifest version bumps, changelog and documentation updates, and refactoring in the apollo adapter to reduce parameter threading via context objects.

Changes

v0.0.3 Release and Refactoring

Layer / File(s) Summary
Crate version and dependency bumps
crates/wesley-cli/Cargo.toml, crates/wesley-core/Cargo.toml, crates/wesley-emit-rust/Cargo.toml, crates/wesley-emit-typescript/Cargo.toml
Version bumped from 0.0.2 to 0.0.3 in all four crates. All interdependencies (wesley-cli → wesley-core, wesley-emit-rust, wesley-emit-typescript; wesley-emit-rust → wesley-core; wesley-emit-typescript → wesley-core) are updated to match.
Release documentation and changelog
CHANGELOG.md, README.md, docs/BEARING.md, docs/ENTRYPOINTS.md, docs/GUIDE.md
Changelog introduces 0.0.3 release section (dated 2026-05-14) with updated compare links; README adds "What's New in v0.0.3" section documenting the runtime optic compiler surface; installation instructions across all documentation files updated from 0.0.2 to 0.0.3.
Context-based parameter threading in apollo adapter
crates/wesley-core/src/adapters/apollo.rs
Selection argument binding and payload codec field collection refactored to use SelectionArgumentBindingContext and PayloadCodecContext respectively, eliminating repeated schema/fragments parameter threading through recursive functions while preserving all validation and type-lookup behavior.
List compatibility boolean simplification
crates/wesley-core/src/adapters/apollo.rs
list_items_are_compatible rewritten from match expression to equivalent !matches! boolean pattern with same nullable edge-case semantics.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Poem

🐰 Version hops along to 0.0.3 so fine,
Context threads are woven, no more parameter line;
Apollo sings cleaner with shape-bound embrace,
Changelog marks the milestone with grace!

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title 'chore(release): v0.0.3' accurately reflects the primary change - a version bump release to v0.0.3 across all crates and documentation.
Description check ✅ Passed The description provides a clear summary of changes and lists comprehensive validation steps, though it deviates from the template structure by using 'Validation' instead of the template's 'Testing' section and omits other template sections like Risk, Backout, and Merge Strategy.
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/v0.0.3

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

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

@github-actions
Copy link
Copy Markdown

🔍 The Case of Pull Request #506

Plain-English Readout

  • Holmes (evidence investigation): Holmes says this change should not ship in its current state. Main reasons: No evidence citations were available for trust analysis; test evidence is incomplete; schema coverage is incomplete.
  • Watson (independent verification): Watson found verification concerns. Most important concern: Low migration risk claimed but schema incomplete.
  • Moriarty (trend forecast): Moriarty sees progress as stalled right now, so forecast confidence is limited.

Suggested next actions

  1. Tighten citations so the report points to exact lines instead of whole files or coarse references.
  2. Resolve Watson’s verification concerns before trusting the Holmes verdict as final.
  3. Treat the readiness forecast as stalled until new evidence or real progress moves the trend again.
  4. Add or strengthen tests for the schema elements and operations HOLMES flagged as weakly proven.
📚 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-05-14T04:50:49.912Z
  • Commit SHA: 8f79e08
  • Bundle Version: 2.0.0

⚠️ Evidence valid only for commit 8f79e08

🔍 Executive Deduction

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

Weighted Completion: ░░░░░░░░░░ 0.0%
Scores: SCS 0.0% · TCI 0.0% · MRI 0.0%
Verification Status: 0 claims verified
Citation Quality: 0 exact · 0 whole-file · 0 coarse
Evidence Trust: missing
Ship Verdict: YOU SHALL NOT PASS

🧩 SCS Breakdown

Component Score Coverage
Sql 0.0% 0.00/154.00
Types 0.0% 0.00/154.00
Validation 0.0% 0.00/154.00
Tests 0.0% 0.00/154.00

🧪 TCI Breakdown

Component Score Coverage Note
Unit Constraints 0.0% 0/104 N/A
Unit Rls 0.0% N/A
Integration Relations 0.0% 0/3 N/A
E2e Ops N/A Query operation test tracking not yet implemented

⚠️ MRI Breakdown

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

📊 The Weight of Evidence

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

Element Weight Status Evidence Strength Deduction

🚪 Security & Performance Gates

"Elementary security measures, Watson..."

Gate Status Evidence Holmes's Ruling
Migration Risk MRI: 0.0% "Trivial risk"
Test Coverage ⚠️ TCI: 0.0% "Theatrical tests!"
Sensitive Fields 0 fields "All secured"
Evidence Quality 0 exact · 0 whole-file · 0 coarse "No evidence citations were available for trust analysis."

📋 The Verdict

YOU SHALL NOT PASS
"Critical evidence is missing! Return to your laboratory!"

Signed and sealed,

  • S. Holmes, Consulting Detective

[END OF INVESTIGATION FOR COMMIT 8f79e08]

🧵 Command Run

  • Run ID: run-mp50gqw7-vlbr50
  • 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-05-14T04:51:53.746Z
  • Patient SHA: 8f79e08

🔬 Citation Verification

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

  • Citations Examined: 0
  • Verified: 0 ✅
  • Failed: 0 ❌
  • Unable to Verify: 0
  • 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: 0.0%
Watson calculates: 0.0%
Difference: ✅ Negligible

🔍 Consistency Analysis

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

⚠️ Low migration risk claimed but schema incomplete

🩺 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-mp50hgcn-943k4e
  • 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-05-14T04:52:35.419Z

🔮 Current State

SCS: ░░░░░░░░░░ 0.0%
TCI: ░░░░░░░░░░ 0.0%
MRI: 0.0% risk
Evidence Trust: missing

📈 Velocity Analysis

SCS Velocity: +0.00%/day
Git Activity (window): 24h · commits 2 (0 relevant) · ~2.00 commits/day
↳ Magnitude: ~0 relevant LOC/day across ~0.0 files/day
Activity Index: 3 / 100 (PR 0, Window 8)
Blended Velocity: +0.02%/day
Commit Size Burstiness: 0 / 100 (higher = more uneven commit sizes)
⚠️ PLATEAU DETECTED - Low SCS movement and low recent Git activity.

⏰ Completion Predictions

ETA: Cannot predict (insufficient velocity)

"At current velocity, completion is... improbable."

⚠️ Warnings

  • Evidence trust is missing; No evidence citations were available for trust analysis.

🧪 Readiness EXPLAIN

  • SCS ≥ 80% → FAIL ❌ (actual 0.0%)
  • TCI ≥ 70% → FAIL ❌ (actual 0.0%)
  • MRI ≤ 40% → PASS ✅ (actual 0.0%)
  • CI Stability ≥ 90% (branch main) → FAIL ❌ (actual 89% over ~168h)
  • Evidence Trust ≥ moderate → FAIL ❌ (actual missing) — No evidence citations were available for trust analysis.
  • Delivery context (last 168h): 0 issues closed · 7 PRs merged (informational, not gating)

Signals blend: SCS velocity (70%) + Git activity (30%, branch-first). Activity only suppresses false plateaus; it never inflates readiness.

📊 Historical Trajectory

05-14: ░░░░░░░░░░ 0.0%
05-14: ░░░░░░░░░░ 0.0%
05-14: ░░░░░░░░░░ 0.0%

"Every problem becomes elementary when reduced to mathematics"
— Professor Moriarty

🧵 Command Run

  • Run ID: run-mp50icig-b0kbn9
  • 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

@flyingrobots flyingrobots merged commit e8a8f36 into main May 14, 2026
23 checks passed
@flyingrobots flyingrobots deleted the release/v0.0.3 branch May 14, 2026 04:53
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