\\n>

⌛ How to resolve this issue?

\\n> \\n> After the wait time has elapsed, a review can be triggered using the `@coderabbitai review` command as a PR comment. Alternatively, push new commits to this PR.\\n> \\n> We recommend that you space out your commits to avoid hitting the rate limit.\\n> \\n>

\\n> \\n> \\n>

\\n>

🚦 How do rate limits work?

\\n> \\n> CodeRabbit enforces hourly rate limits for each developer per organization.\\n> \\n> Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.\\n> \\n> Please see our [FAQ](https://docs.coderabbit.ai/faq) for further information.\\n> \\n>

\\n> \\n>

\\n>

ℹ️ Review info

\\n> \\n>

\\n>

⚙️ Run configuration

\\n> \\n> **Configuration used**: Path: .coderabbit.yaml\\n> \\n> **Review profile**: CHILL\\n> \\n> **Plan**: Pro\\n> \\n> **Run ID**: `9045b028-a14f-41f7-81fa-f61c7b6e5894`\\n> \\n>

\\n> \\n>

\\n>

📥 Commits

\\n> \\n> Reviewing files that changed from the base of the PR and between 483439d47f3754d00f9c836dfb9ab8118f6c3ecb and 0ac0e6450fc06665d0d46a617b897e3efe8fcf62.\\n> \\n>

\\n> \\n>

\\n>

📒 Files selected for processing (6)

\\n> \\n> * `CHANGELOG.md`\\n> * `crates/wesley-core/src/adapters/apollo.rs`\\n> * `crates/wesley-core/tests/lowering_validation.rs`\\n> * `docs/BEARING.md`\\n> * `docs/design/0009-rust-core-and-wasm-capability-abi/phase-0-ir-truth-manifest.md`\\n> * `docs/design/0013-rust-ir-parity-sentinel/rust-ir-parity-sentinel.md`\\n> \\n>

\\n> \\n>

\\n\\n\\n\\n\\n\\n

\\n

📝 Walkthrough

\\n\\n## Walkthrough\\n\\nThis PR establishes the Rust IR parity foundation for v0.0.6 by implementing directive canonicalization in the Apollo lowering adapter, expanding the fixture corpus with three new test schemas covering directive-heavy, legacy-alias, and schema-extension patterns, and introducing design packet 0013 specifying the parity sentinel verification workflow.\\n\\n## Changes\\n\\n**Rust IR Parity Foundation**\\n\\n|Layer / File(s)|Summary|\\n|---|---|\\n|**Directive Canonicalization and Duplicate Rejection**
`crates/wesley-core/src/adapters/apollo.rs`|Apollo adapter now canonicalizes directive aliases (e.g., `table`, `pk`) to Wesley-internal canonical names and rejects duplicate canonical directives with a lowering error instead of last-write-wins behavior.|\\n|**Lowering Validation Tests for Canonicalization and Duplicates**
`crates/wesley-core/tests/lowering_validation.rs`|New Tokio async tests validate fixture lowering and assert that legacy directive aliases are canonicalized correctly and that duplicate canonical directives fail with expected error messages.|\\n|**Directive-Heavy Schema Fixture**
`test/fixtures/ir-parity/directive-heavy-schema.graphql`, `directive-heavy-schema.l1.json`, `directive-heavy-schema.l1.hash`|Multi-type fixture with extensive `@wes_*` directive coverage including table mappings, keys/constraints, defaults, and RLS policies across Organization, Account, and AccountEvent types, with canonical L1 IR and hash artifacts.|\\n|**Legacy-Alias Schema Fixture**
`test/fixtures/ir-parity/legacy-alias-schema.graphql`, `legacy-alias-schema.l1.json`, `legacy-alias-schema.l1.hash`|Tenant and Member types using both canonical and legacy-alias directive forms to validate canonicalization during lowering, provided as GraphQL source and canonical L1 IR JSON with hash.|\\n|**Schema-Extensions Fixture**
`test/fixtures/ir-parity/schema-extensions-schema.graphql`, `schema-extensions-schema.l1.json`, `schema-extensions-schema.l1.hash`|Comprehensive fixture covering scalar extensions, interface composition, unions, enum extensions, and input objects with defaults, including User and Team types with timestamps and relationships, provided as GraphQL and canonical L1 IR with hash.|\\n|**Invalid Fixture for Negative Testing**
`test/fixtures/ir-parity-invalid/duplicate-directive-alias.graphql`|Account type fixture declaring the same directive in both canonical and legacy forms to validate that the lowerer correctly rejects duplicate-directive errors.|\\n|**Design Packet 0013 and IR Truth Manifest**
`docs/design/0013-rust-ir-parity-sentinel/rust-ir-parity-sentinel.md`, `docs/design/0009-rust-core-and-wasm-capability-abi/phase-0-ir-truth-manifest.md`, `docs/design/README.md`|New design document specifying the Rust IR Parity Sentinel comparator contract (fixture inputs, normalized semantic IR comparison, hash verification, failure diagnostics); phase-0 manifest updated with invalid fixture documentation and fixture-hash catalog; design README reference added.|\\n|**BEARING Roadmap and ASAP Backlog Reframing**
`docs/BEARING.md`, `docs/method/backlog/asap/README.md`|BEARING reframed around v0.0.6 Rust IR parity and module-boundary enforcement with updated timeline, Parity Sentinel section, module-boundary emphasis, and revised tensions/next-target plan; ASAP backlog shortened to Rust IR parity evidence and domain-empty boundary work.|\\n|**v0.0.5 Release Evidence and Changelog**
`docs/method/releases/v0.0.5/verification.md`, `CHANGELOG.md`|v0.0.5 verification section filled with publication evidence (signed tag, GitHub Release, CI runs, crates.io confirmations); CHANGELOG updated with Unreleased entries documenting directive canonicalization, fixture expansion, and bearing refinements.|\\n\\n## Estimated code review effort\\n\\n🎯 3 (Moderate) | ⏱️ ~25 minutes\\n\\n## Suggested labels\\n\\n`enhancement`\\n\\n## Poem\\n\\n> 🐰 *Directives now stand tall and true,* \\n> *Canonicalized through and through,* \\n> *With fixtures broad and parity bright,* \\n> *The Rust compiler takes flight—* \\n> *No more silent semantic drift in view!* 🚀\\n\\n

\\n\\n\\n\\n\\n

\\n

🚥 Pre-merge checks | ✅ 3 | ❌ 2

\\n\\n### ❌ Failed checks (1 warning, 1 inconclusive)\\n\\n| Check name | Status | Explanation | Resolution |\\n| :----------------: | :------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\\n| Docstring Coverage | ⚠️ Warning | Docstring coverage is 72.73% which is insufficient. The required threshold is 80.00%. | Write docstrings for the functions missing them to satisfy the coverage threshold. |\\n| Description check | ❓ Inconclusive | The PR description covers the main changes and includes a validation section with testing steps, but omits several required template sections (Why/Rationale, Risk, Backout, EvidenceMap/SourceMap). | Complete the PR description by adding Why/Rationale for the parity approach, Risk/mitigation notes, Backout strategy, and any EvidenceMap confirmations if applicable. |\\n\\n

\\n

✅ Passed checks (3 passed)

\\n\\n| Check name | Status | Explanation |\\n| :------------------------: | :------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\\n| Title check | ✅ Passed | The title clearly summarizes the main change: expanding the parity fixture coverage with new test fixtures for directive-heavy schemas, schema extensions, legacy aliases, and invalid cases. |\\n| Linked Issues check | ✅ Passed | Check skipped because no linked issues were found for this pull request. |\\n| Out of Scope Changes check | ✅ Passed | Check skipped because no linked issues were found for this pull request. |\\n\\n

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

\\n\\n\\n\\n\\n

\\n

✨ Finishing Touches

\\n\\n

\\n

🧪 Generate unit tests (beta)

\\n\\n- [ ] Create PR with unit tests\\n- [ ] Commit unit tests in branch `codex/v0.0.6-bearing`\\n\\n

\\n\\n

\\n\\n\\n\\n\\n---\\n\\nThanks for using [CodeRabbit](https://coderabbit.ai?utm_source=oss&utm_medium=github&utm_campaign=flyingrobots/wesley&utm_content=513)! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.\\n\\n

\\n

❤️ Share

\\n\\n- [X](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai)\\n- [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai)\\n- [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai)\\n- [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)\\n\\n

\\n\\n\\n_{Comment `@coderabbitai help` to get the list of available commands and usage tips.}\\n\\n\\n\\n\\n\\n\\n\\n\",\"path\":null,\"side\":null,\"line\":null}{\"type\":\"pull_request_comment\",\"body\":\"\\n\\n# 🔍 The Case of Pull Request #513\\n\\n## Plain-English Readout\\n\\n- **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.\\n- **Watson (independent verification)**: Watson found verification concerns. Most important concern: Low migration risk claimed but schema incomplete.\\n- **Moriarty (trend forecast)**: Moriarty sees progress as stalled right now, so forecast confidence is limited.\\n\\n## Suggested next actions\\n\\n1. Tighten citations so the report points to exact lines instead of whole files or coarse references.\\n2. Resolve Watson’s verification concerns before trusting the Holmes verdict as final.\\n3. Treat the readiness forecast as stalled until new evidence or real progress moves the trend again.\\n4. Add or strengthen tests for the schema elements and operations HOLMES flagged as weakly proven.\\n\\n

📚 Glossary (what the Holmes terms mean)

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

\\n\\n---\\n\\n

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

\\n\\n### 🕵️ SHA-lock HOLMES Investigation\\n\\n- Generated: 2026-05-22T08:04:37.673Z\\n- Commit SHA: 9fe1fbfac851cab61a482766420494a5bdea04ff\\n- Bundle Version: 2.0.0\\n\\n> ⚠️ Evidence valid only for commit `9fe1fbf`\\n\\n## 🔍 Executive Deduction\\n\\n\\\"Watson, after careful examination of the evidence, I deduce...\\\"\\n\\n**Weighted Completion**: ░░░░░░░░░░ 0.0%\\n**Scores**: SCS 0.0% · TCI 0.0% · MRI 0.0%\\n**Verification Status**: 0 claims verified\\n**Citation Quality**: 0 exact · 0 whole-file · 0 coarse\\n**Evidence Trust**: missing\\n**Ship Verdict**: YOU SHALL NOT PASS\\n\\n## 🧩 SCS Breakdown\\n\\n| Component | Score | Coverage |\\n|-----------|-------|----------|\\n| Sql | 0.0% | 0.00/154.00 |\\n| Types | 0.0% | 0.00/154.00 |\\n| Validation | 0.0% | 0.00/154.00 |\\n| Tests | 0.0% | 0.00/154.00 |\\n\\n## 🧪 TCI Breakdown\\n\\n| Component | Score | Coverage | Note |\\n|-----------|-------|----------|------|\\n| Unit Constraints | 0.0% | 0/104 | N/A |\\n| Unit Rls | 0.0% | — | N/A |\\n| Integration Relations | 0.0% | 0/3 | N/A |\\n| E2e Ops | N/A | — | Query operation test tracking not yet implemented |\\n\\n## ⚠️ MRI Breakdown\\n\\n| Component | Risk Share | Points | Count |\\n|-----------|------------|--------|-------|\\n| Drops | 0% | 0 | 0 |\\n| Renames Without Uid | 0% | 0 | 0 |\\n| Add Not Null Without Default | 0% | 0 | 0 |\\n| Non Concurrent Indexes | 0% | 0 | 0 |\\n\\n## 📊 The Weight of Evidence\\n\\n\\\"Observe, Watson, how not all features carry equal importance...\\\"\\n\\n| Element | Weight | Status | Evidence | Strength | Deduction |\\n|---------|--------|--------|----------|----------|-----------|\\n\\n## 🚪 Security & Performance Gates\\n\\n\\\"Elementary security measures, Watson...\\\"\\n\\n| Gate | Status | Evidence | Holmes's Ruling |\\n|------|--------|----------|-----------------|\\n| Migration Risk | ✅ | MRI: 0.0% | \\\"Trivial risk\\\" |\\n| Test Coverage | ⚠️ | TCI: 0.0% | \\\"Theatrical tests!\\\" |\\n| Sensitive Fields | ✅ | 0 fields | \\\"All secured\\\" |\\n| Evidence Quality | ⛔ | 0 exact · 0 whole-file · 0 coarse | \\\"No evidence citations were available for trust analysis.\\\" |\\n\\n## 📋 The Verdict\\n\\n⛔ **YOU SHALL NOT PASS**\\n\\\"Critical evidence is missing! Return to your laboratory!\\\"\\n\\nSigned and sealed,\\n- S. Holmes, Consulting Detective\\n\\n[END OF INVESTIGATION FOR COMMIT 9fe1fbf]\\n\\n## 🧵 Command Run\\n\\n- Run ID: run-mpgmwtsy-y0c4uv\\n- Transmutation: holmes-investigate\\n- Command: investigate\\n- Status: completed\\n- Ledger: /home/runner/work/wesley/wesley/test/fixtures/examples/.wesley-cache/ledger\\n\\n

\\n\\n---\\n\\n

🩺 Dr. WATSON full report (click to expand)

\\n\\n### 🩺 Dr. Watson's Independent Verification Report\\n\\n_Medical Examination of Evidence_\\n\\n- Examination Date: 2026-05-22T08:05:41.039Z\\n- Patient SHA: 9fe1fbfac851cab61a482766420494a5bdea04ff\\n\\n## 🔬 Citation Verification\\n\\n\\\"Let me examine each piece of evidence independently...\\\"\\n\\n- **Citations Examined**: 0\\n- **Verified**: 0 ✅\\n- **Failed**: 0 ❌\\n- **Unable to Verify**: 0\\n- **Exact Subrange Citations**: 0\\n- **Whole-file Citations**: 0\\n- **Coarse Citations**: 0\\n- **Evidence Trust**: missing\\n- **Trust Note**: No evidence citations were available for trust analysis.\\n\\n**Verification Rate**: 0.0%\\n\\n## 📊 Mathematical Verification\\n\\n\\\"I shall recalculate Holmes's arithmetic...\\\"\\n\\nHolmes claimed SCS: 0.0%\\nWatson calculates: 0.0%\\nDifference: ✅ Negligible\\n\\n## 🔍 Consistency Analysis\\n\\n\\\"Checking for contradictions in Holmes's deductions...\\\"\\n\\n⚠️ Low migration risk claimed but schema incomplete\\n\\n## 🩺 Dr. Watson's Medical Opinion\\n\\n**VERIFICATION: CONCERNS NOTED** ⚠️\\n\\n\\\"While Holmes's methods are generally sound, I have noted some\\\"\\n\\\"discrepancies that warrant further investigation. No evidence citations were available for trust analysis.\\\"\\n\\nRespectfully submitted,\\n- Dr. J. Watson, M.D.\\n Medical Examiner & Verification Specialist\\n\\n## 🧵 Command Run\\n\\n- Run ID: run-mpgmxhd1-cptc1c\\n- Transmutation: watson-verify\\n- Command: verify\\n- Status: completed\\n- Ledger: /home/runner/work/wesley/wesley/test/fixtures/examples/.wesley-cache/ledger\\n\\n

\\n\\n---\\n\\n

🔮 Professor MORIARTY full report (click to expand)

\\n\\n### 🧠 Professor Moriarty's Temporal Predictions\\n\\n_The Mathematics of Inevitability_\\n\\n- Analysis Date: 2026-05-22T08:06:21.204Z\\n\\n## 🔮 Current State\\n\\n**SCS**: ░░░░░░░░░░ 0.0%\\n**TCI**: ░░░░░░░░░░ 0.0%\\n**MRI**: 0.0% risk\\n**Evidence Trust**: missing\\n\\n## 📈 Velocity Analysis\\n\\n**SCS Velocity**: +0.00%/day\\n**Git Activity (window)**: 24h · commits 14 (1 relevant) · ~14.00 commits/day\\n↳ Magnitude: ~313 relevant LOC/day across ~6.0 files/day\\n**Activity Index**: 25 / 100 (PR 0, Window 62)\\n**Blended Velocity**: +0.15%/day\\n**Commit Size Burstiness**: 0 / 100 (higher = more uneven commit sizes)\\n⚠️ **PLATEAU DETECTED** - Low SCS movement and low recent Git activity.\\n\\n## ⏰ Completion Predictions\\n\\n**ETA**: Cannot predict (insufficient velocity)\\n\\n\\\"At current velocity, completion is... improbable.\\\"\\n\\n## ⚠️ Warnings\\n\\n- Evidence trust is missing; No evidence citations were available for trust analysis.\\n\\n## 🧪 Readiness EXPLAIN\\n\\n- SCS ≥ 80% → FAIL ❌ (actual 0.0%)\\n- TCI ≥ 70% → FAIL ❌ (actual 0.0%)\\n- MRI ≤ 40% → PASS ✅ (actual 0.0%)\\n- CI Stability ≥ 90% (branch main) → FAIL ❌ (actual 87% over ~168h)\\n- Evidence Trust ≥ moderate → FAIL ❌ (actual missing) — No evidence citations were available for trust analysis.\\n- Delivery context (last 168h): 0 issues closed · 4 PRs merged (informational, not gating)\\n\\n_Signals blend:_ SCS velocity (70%) + Git activity (30%, branch-first). Activity only suppresses false plateaus; it never inflates readiness.\\n\\n## 📊 Historical Trajectory\\n\\n05-22: ░░░░░░░░░░ 0.0%\\n05-22: ░░░░░░░░░░ 0.0%\\n05-22: ░░░░░░░░░░ 0.0%\\n\\n*\\\"Every problem becomes elementary when reduced to mathematics\\\"*\\n— Professor Moriarty\\n\\n## 🧵 Command Run\\n\\n- Run ID: run-mpgmyccy-9565tx\\n- Transmutation: moriarty-predict\\n- Command: predict\\n- Status: completed\\n- Ledger: /home/runner/work/wesley/wesley/test/fixtures/examples/.wesley-cache/ledger\\n\\n

\\n\\n---\\n\\n_Machine-readable reports:_ holmes-report.json · watson-report.json · moriarty-report.json (see workflow artifacts).\\n\\n---\\n\\n*Filed at 221B Repository Street*\\n\",\"path\":null,\"side\":null,\"line\":null}{\"type\":\"pull_request_comment\",\"body\":\"## Self-Code Review Findings\\n\\n@codex please confirm whether you agree with these findings before merge. Review basis: local clean worktree, `git fetch origin --prune`, then `git diff origin/main...HEAD`.\\n\\n| Severity | File / line | Type | Evidence | Recommended mitigation prompt |\\n| --- | --- | --- | --- | --- |\\n| High | `crates/wesley-core/src/adapters/apollo.rs:507` | Logical regression / unintended compatibility break | The new duplicate check runs for every directive name after `canonical_directive_name`, not only for Wesley aliases. Valid GraphQL SDL with a repeatable non-Wesley directive now fails: `directive @tag(name: String!) repeatable on FIELD_DEFINITION` plus `@tag(name: \\\"a\\\") @tag(name: \\\"b\\\")` exits with `Lowering error: Duplicate directive '@tag' in directive`. | `Narrow Rust duplicate-directive rejection so it only rejects canonical collisions for the supported core Wesley directive aliases, or implement explicit repeatable-directive support in L1. Add a regression test proving non-Wesley repeatable directives are either preserved correctly or rejected by a documented unsupported-feature diagnostic rather than by the generic duplicate alias path.` |\\n| Medium | `docs/design/0013-rust-ir-parity-sentinel/rust-ir-parity-sentinel.md:49` | Design contract gap | The packet says the sentinel records and compares legacy JS semantic IR bytes against Rust semantic IR bytes, but the named JS anchor emits a table IR shape with `tables`, `enums`, `scalars`, and `relationships` (`packages/wesley-runtime-node/src/GraphQLAdapter.mjs:148`), while Rust L1 fixtures emit `types`. The packet never defines a projection or equivalence layer, so the next implementation slice has no coherent comparator contract. | `Revise the parity sentinel packet to define the comparison projection explicitly: either compare only a documented common semantic subset, introduce a JS-to-L1/Rust-to-legacy normalization adapter, or exclude non-overlapping fixtures until a real crosswalk exists. Add playback questions that force the implementation to prove the chosen projection.` |\\n| Medium | `docs/BEARING.md:77` | Documentation reproducibility / transient local state | `BEARING.md` commits a machine-local path and ephemeral sibling-repo worktree state: `~/git/wesley-postgres` has local `main` ahead of `origin/main` and uncommitted bootstrap work. That is useful session evidence, but not stable project direction and will become stale immediately. | `Replace the local path/worktree-status sentence with stable repository-level doctrine: wesley-postgres is the database extraction authority and Wesley should coordinate before changing database-shaped compatibility seams. Move the exact local inspection result to PR notes or session memory instead of committed BEARING text.` |\\n| Low | `docs/BEARING.md:108` | Planning drift / stale next-action list | The `Next Target` list still tells the next agent to keep v0.0.5 publication evidence complete and expand the L1 fixture corpus, but this branch already does both. After merge, BEARING should point to the remaining next moves, not replay completed work. | `Update the BEARING next-target list so completed slices are recorded as current evidence, and the remaining active pulls start with implementing the parity sentinel command, defining the IR projection/crosswalk, and pulling domain-empty core boundary enforcement.` |\\n\\nIssue count: High 1, Medium 2, Low 1.\",\"path\":null,\"side\":null,\"line\":null}{\"type\":\"pull_request_comment\",\"body\":\"_⚠️ Potential issue_ | _🟡 Minor_ | _⚡ Quick win_\\n\\n**Avoid machine-local path/state in shared roadmap docs.**\\n\\nLine 77 and Line 78 encode host-specific state (`~/git/...`, local `main` ahead of `origin/main`) that will quickly go stale and cannot be validated by other contributors. Prefer repository-relative/remote references plus a dated note in release evidence docs.\\n\\n

\\n

🤖 Prompt for AI Agents

\\n\\n```\\nVerify each finding against current code. Fix only still-valid issues, skip the\\nrest with a brief reason, keep changes minimal, and validate.\\n\\nIn `@docs/BEARING.md` around lines 77 - 79, Replace the machine-local path and\\nhost-specific branch state in BEARING.md: remove the literal\\n\\\"`~/git/wesley-postgres`\\\" and the note \\\"local `main` ahead of `origin/main`\\\" and\\ninstead reference the repository by its remote name or repo URL (e.g.,\\n\\\"wesley-postgres\\\" or the remote Git URL) and, if necessary, add a dated note in\\nrelease evidence or changelog indicating the local bootstrap work and its date;\\nupdate the surrounding sentence that mentions PostgreSQL/Supabase generation and\\nexecution adapters to use the repository-relative/remote reference and add the\\ndate/context note rather than machine-local state.\\n```\\n\\n

\\n\\n\\n\\n\\n\\n✅ Addressed in commit 0ac0e64\",\"path\":\"docs/BEARING.md\",\"side\":\"RIGHT\",\"line\":null}{\"type\":\"pull_request_comment\",\"body\":\"**Actionable comments posted: 1**\\n\\n

\\n

🧹 Nitpick comments (1)

\\n\\n
\\n
crates/wesley-core/src/adapters/apollo.rs (1)
\\n\\n`960-972`: _⚡ Quick win_\\n\\n**Consider adding a doc comment to explain the canonicalization contract.**\\n\\nThe function correctly implements the alias-to-canonical mapping, but a doc comment would clarify the purpose and supported aliases for future maintainers.\\n\\n\\n\\n
\\n
📝 Suggested doc comment
\\n\\n```diff\\n+/// Maps legacy Wesley directive aliases to their canonical internal names.\\n+///\\n+/// This normalization ensures that directives declared with different aliases\\n+/// (e.g., `@table`, `@wesley_table`) are recognized as the same directive\\n+/// and stored under a single canonical key (`wes_table`).\\n+///\\n+/// Returns the canonical name if a mapping exists, otherwise returns the input unchanged.\\n fn canonical_directive_name(name: &str) -> &str {\\n match name {\\n```\\n
\\n\\n
\\n
🤖 Prompt for AI Agents
\\n\\n```\\nVerify each finding against current code. Fix only still-valid issues, skip the\\nrest with a brief reason, keep changes minimal, and validate.\\n\\nIn `@crates/wesley-core/src/adapters/apollo.rs` around lines 960 - 972, Add a\\nconcise doc comment for the function canonical_directive_name describing its\\ncontract: that it maps known directive aliases (list the aliases and their\\ncanonical names like \\\"wesley_table\\\"/\\\"table\\\" -> \\\"wes_table\\\",\\n\\\"wesley_pk\\\"/\\\"pk\\\"/\\\"primaryKey\\\" -> \\\"wes_pk\\\", etc.), that it returns a borrowed\\n&str of the canonical name (does not allocate), and that unknown names are\\nreturned unchanged; include purpose and examples of expected inputs/outputs so\\nfuture maintainers understand supported aliases and return semantics.\\n```\\n\\n
\\n\\n
\\n\\n

\\n\\n

\\n

🤖 Prompt for all review comments with AI agents

\\n\\n```\\nVerify each finding against current code. Fix only still-valid issues, skip the\\nrest with a brief reason, keep changes minimal, and validate.\\n\\nInline comments:\\nIn `@docs/BEARING.md`:\\n- Around line 77-79: Replace the machine-local path and host-specific branch\\nstate in BEARING.md: remove the literal \\\"`~/git/wesley-postgres`\\\" and the note\\n\\\"local `main` ahead of `origin/main`\\\" and instead reference the repository by\\nits remote name or repo URL (e.g., \\\"wesley-postgres\\\" or the remote Git URL) and,\\nif necessary, add a dated note in release evidence or changelog indicating the\\nlocal bootstrap work and its date; update the surrounding sentence that mentions\\nPostgreSQL/Supabase generation and execution adapters to use the\\nrepository-relative/remote reference and add the date/context note rather than\\nmachine-local state.\\n\\n---\\n\\nNitpick comments:\\nIn `@crates/wesley-core/src/adapters/apollo.rs`:\\n- Around line 960-972: Add a concise doc comment for the function\\ncanonical_directive_name describing its contract: that it maps known directive\\naliases (list the aliases and their canonical names like \\\"wesley_table\\\"/\\\"table\\\"\\n-> \\\"wes_table\\\", \\\"wesley_pk\\\"/\\\"pk\\\"/\\\"primaryKey\\\" -> \\\"wes_pk\\\", etc.), that it\\nreturns a borrowed &str of the canonical name (does not allocate), and that\\nunknown names are returned unchanged; include purpose and examples of expected\\ninputs/outputs so future maintainers understand supported aliases and return\\nsemantics.\\n```\\n\\n

\\n\\n

\\n

🪄 Autofix (Beta)

\\n\\nFix all unresolved CodeRabbit comments on this PR:\\n\\n- [ ] Push a commit to this branch (recommended)\\n- [ ] Create a new PR with the fixes\\n\\n

\\n\\n---\\n\\n

\\n

ℹ️ Review info

\\n\\n

\\n

⚙️ Run configuration

\\n\\n**Configuration used**: Path: .coderabbit.yaml\\n\\n**Review profile**: CHILL\\n\\n**Plan**: Pro\\n\\n**Run ID**: `220b721d-b1df-403f-bdc5-7cd03e5c7394`\\n\\n

\\n\\n

\\n

📥 Commits

\\n\\nReviewing files that changed from the base of the PR and between fa42c71832520b70e55447e865e0425e467db2a5 and 483439d47f3754d00f9c836dfb9ab8118f6c3ecb.\\n\\n

\\n\\n

\\n

📒 Files selected for processing (20)

\\n\\n* `CHANGELOG.md`\\n* `crates/wesley-core/src/adapters/apollo.rs`\\n* `crates/wesley-core/tests/lowering_validation.rs`\\n* `docs/BEARING.md`\\n* `docs/design/0009-rust-core-and-wasm-capability-abi/phase-0-ir-truth-manifest.md`\\n* `docs/design/0013-rust-ir-parity-sentinel/rust-ir-parity-sentinel.md`\\n* `docs/design/README.md`\\n* `docs/method/backlog/asap/README.md`\\n* `docs/method/backlog/asap/SOURCE_wesley-core-rs-parity-sentinel.md`\\n* `docs/method/releases/v0.0.5/verification.md`\\n* `test/fixtures/ir-parity-invalid/duplicate-directive-alias.graphql`\\n* `test/fixtures/ir-parity/directive-heavy-schema.graphql`\\n* `test/fixtures/ir-parity/directive-heavy-schema.l1.hash`\\n* `test/fixtures/ir-parity/directive-heavy-schema.l1.json`\\n* `test/fixtures/ir-parity/legacy-alias-schema.graphql`\\n* `test/fixtures/ir-parity/legacy-alias-schema.l1.hash`\\n* `test/fixtures/ir-parity/legacy-alias-schema.l1.json`\\n* `test/fixtures/ir-parity/schema-extensions-schema.graphql`\\n* `test/fixtures/ir-parity/schema-extensions-schema.l1.hash`\\n* `test/fixtures/ir-parity/schema-extensions-schema.l1.json`\\n\\n

\\n\\n

\\n

💤 Files with no reviewable changes (1)

\\n\\n* docs/method/backlog/asap/SOURCE_wesley-core-rs-parity-sentinel.md\\n\\n

\\n\\n

\\n\\n\",\"path\":null,\"side\":null,\"line\":null}{\"type\":\"pull_request_comment\",\"body\":\"\\n### 💡 Codex Review\\n\\nHere are some automated review suggestions for this pull request.\\n\\n**Reviewed commit:** `483439d47f`\\n \\n\\n

ℹ️ About Codex in GitHub

\\n
\\n\\n[Your team has set up Codex to review pull requests in this repo](https://chatgpt.com/codex/cloud/settings/general). Reviews are triggered when you\\n- Open a pull request for review\\n- Mark a draft as ready\\n- Comment \\\"@codex review\\\".\\n\\nIf Codex has suggestions, it will comment; otherwise it will react with 👍.\\n\\n\\n\\n\\nCodex can also answer questions or update the PR. Try commenting \\\"@codex address that feedback\\\".\\n \\n

\",\"path\":null,\"side\":null,\"line\":null}{\"type\":\"pull_request_comment\",\"body\":\"**_{_{![P1 Badge](https://img.shields.io/badge/P1-orange?style=flat)}} Restrict duplicate rejection to canonical Wesley aliases**\\n\\nThe duplicate guard now checks `canonical_name` for every directive, so any repeatable non-Wesley directive (for example `@tag` declared as `repeatable`) is rejected even though the SDL is valid. I reproduced this by lowering a schema with `@tag(name: \\\"a\\\") @tag(name: \\\"b\\\")`, which now fails with `Lowering error: Duplicate directive '@tag' in directive`; this is a compatibility regression introduced by this change because the new logic conflates alias-collision protection with general repeatable-directive handling.\\n\\nUseful? React with 👍 / 👎.\",\"path\":\"crates/wesley-core/src/adapters/apollo.rs\",\"side\":\"RIGHT\",\"line\":null}{\"type\":\"pull_request_comment\",\"body\":\"**_{_{![P2 Badge](https://img.shields.io/badge/P2-yellow?style=flat)}} Define an explicit JS↔Rust IR projection before byte compare**\\n\\nThe comparator contract says to compare legacy JS semantic IR bytes directly against Rust semantic IR bytes, but it does not define any crosswalk/projection despite the referenced JS anchor emitting a different IR shape (`tables/enums/scalars/relationships` in `packages/wesley-runtime-node/src/GraphQLAdapter.mjs`) than Rust L1 fixtures (`types`). Without a normalization/projection contract here, a parity sentinel implementation cannot distinguish expected structural differences from real regressions, so the design is currently non-executable as written.\\n\\nUseful? React with 👍 / 👎.\",\"path\":\"docs/design/0013-rust-ir-parity-sentinel/rust-ir-parity-sentinel.md\",\"side\":\"RIGHT\",\"line\":null}{\"type\":\"pull_request_comment\",\"body\":\"**_{_{![P3 Badge](https://img.shields.io/badge/P3-lightgrey?style=flat)}} Remove machine-local worktree state from project bearing**\\n\\nThis commits a local filesystem path and transient sibling-repo branch/dirty-state snapshot into `BEARING.md`, which will become stale immediately for other contributors and CI contexts and does not provide durable repository direction. Keeping ephemeral workstation state in the canonical bearing doc harms reproducibility of planning context and should be moved to PR/session notes instead.\\n\\nUseful? React with 👍 / 👎.\",\"path\":\"docs/BEARING.md\",\"side\":\"RIGHT\",\"line\":null}{\"type\":\"pull_request_comment\",\"body\":\"## Self-Code Review Resolution\\n\\n@codex follow-up commit `0ac0e645` resolves the four findings from comment `4516291171`.\\n\\n| Original severity | Resolution |\\n| --- | --- |\\n| High | Narrowed duplicate directive rejection to canonical core Wesley directives only. Repeated custom directives are now preserved as ordered arrays, with regression coverage for repeatable `@tag`. |\\n| Medium | Updated design packet `0013` to require a named `js-table-vs-rust-table.v0` projection/crosswalk before comparing legacy JS table IR with Rust L1 bytes. |\\n| Medium | Removed transient local `~/git/wesley-postgres` worktree status from committed BEARING text and kept only stable sibling-repo coordination doctrine. |\\n| Low | Updated BEARING so completed publication-evidence and fixture-expansion slices are current evidence, while the next pulls are the remaining sentinel/projection/domain-boundary work. |\\n\\nValidation after the fix:\\n\\n- `cargo fmt --check`\\n- `cargo test -p wesley-core --test lowering_validation`\\n- `cargo clippy -p wesley-core --all-targets -- -D warnings`\\n- `cargo xtask docs-check`\\n- `git diff --check`\\n- repeatable custom directive CLI reproduction now succeeds\\n- `pnpm run preflight`\\n- push hook repository preflight\",\"path\":null,\"side\":null,\"line\":null}{\"type\":\"pull_request_comment\",\"body\":\"### Summary\\n* Added a concise doc comment to `canonical_core_directive_name` clarifying alias-to-canonical mapping scope, borrowed return semantics, and passthrough behavior for non-core/custom directives, with concrete examples. [crates/wesley-core/src/adapters/apollo.rsL961-L970](https://github.com/flyingrobots/wesley/blob/0ac0e6450fc06665d0d46a617b897e3efe8fcf62/crates/wesley-core/src/adapters/apollo.rs#L961-L970)\\n* Committed the change on the current branch as `e887bf8` with message: `docs(ir): document core directive alias canonicalization`. [crates/wesley-core/src/adapters/apollo.rsL961-L970](https://github.com/flyingrobots/wesley/blob/0ac0e6450fc06665d0d46a617b897e3efe8fcf62/crates/wesley-core/src/adapters/apollo.rs#L961-L970)\\n\\n**Testing**\\n* ✅ `cargo fmt --check`\\n* ✅ `cargo test -p wesley-core --test lowering_validation`\\n* ✅ `pnpm run preflight` (passes; shows non-blocking engine warning for local Node v20 vs wanted >=22)\\n\\n [View task →](https://chatgpt.com/s/cd_6a100e38a6788191a0c5e3d80a78fcb3)\",\"path\":null,\"side\":null,\"line\":null}{\"type\":\"pull_request_comment\",\"body\":\"## Self-Code Review Findings\\n\\n@codex please confirm before merge. Review basis: clean local worktree, `git fetch origin --prune`, then `git diff origin/main...HEAD`.\\n\\n| Severity | File / line | Type | Evidence | Recommended mitigation prompt |\\n| --- | --- | --- | --- | --- |\\n| Medium | `docs/README.md:33` | Documentation drift / front-door inconsistency | This branch resets `docs/BEARING.md` and `docs/method/backlog/asap/README.md` to v0.0.6 Rust IR parity work, but the docs front door still says “The active release center is now the v0.0.5 clean-house packet” and links only `0012-product-leftover-cleanup`. Because `docs/README.md` is an indexed public/front-door doc, this leaves readers with two contradictory active centers. | `Update docs/README.md Current Center Of Gravity so it states that v0.0.5 clean-house is shipped/historical evidence and v0.0.6 centers on Rust IR parity. Link both the shipped 0012 cleanup packet as background and the active 0013 parity sentinel packet as the current release packet. Run docs-check/preflight after the edit.` |\\n\\nIssue count: Medium 1.\",\"path\":null,\"side\":null,\"line\":null}{\"type\":\"pull_request_comment\",\"body\":\"\\n### 💡 Codex Review\\n\\nHere are some automated review suggestions for this pull request.\\n\\n**Reviewed commit:** `0ac0e6450f`\\n \\n\\n

ℹ️ About Codex in GitHub

\",\"path\":null,\"side\":null,\"line\":null}{\"type\":\"pull_request_comment\",\"body\":\"**_{_{![P2 Badge](https://img.shields.io/badge/P2-yellow?style=flat)}} Update docs front door for v0.0.6 release center**\\n\\nThis change declares `v0.0.6` as the active gravity in BEARING, but `docs/README.md` still says the active release center is `v0.0.5` (line 33 in that file), so the two top-level navigation docs now contradict each other about what is current. That inconsistency was introduced here and will misroute readers who start from the docs front door; please update `docs/README.md` in the same change to mark `v0.0.5` as shipped/history and point active work to the `0013` parity packet.\\n\\nUseful? React with 👍 / 👎.\",\"path\":\"docs/BEARING.md\",\"side\":\"RIGHT\",\"line\":17}","text_elements",[],{"_383":533,"_364":365,"_385":371},{"_386":534,"_388":-5,"_41":-5,"_389":-5,"_94":320,"_90":391},[535],{"_45":529,"_90":536},"input_text",{"_383":538,"_364":365,"_385":371},{"_386":539,"_388":-5,"_41":-5,"_389":-5,"_94":320,"_90":391},[540,541],{"_45":543,"_90":536},{"_45":542,"_90":536},"\n /workspace/wesley\n bash\n 2026-05-22\n Etc/UTC\n","# AGENTS.md instructions for /workspace/wesley\n\n\n# AGENTS\n\nThis guide is for AI agents and human operators recovering context in the Wesley repository.\n\n## Git Rules\n\n- **NEVER** amend commits.\n- **NEVER** rebase or force-push.\n- **NEVER** push to `main` without explicit permission.\n- Always use standard commits and regular pushes.\n\n## Documentation & Planning Map\n\nDo not audit the repository by recursively walking the filesystem. Follow the authoritative manifests:\n\n### 1. The Entrance\n- **`README.md`**: Public front door, core value prop, and quick start.\n- **`docs/GUIDE.md`**: Orientation, fast path, and system orchestration.\n\n### 2. The Bedrock\n- **`docs/ARCHITECTURE.md`**: Authoritative structural reference (Base Platform, Modules, Pipeline).\n- **`docs/VISION.md`**: Core tenets and the \"Trustworthy Change\" mission.\n- **`docs/METHOD.md`**: Repo work doctrine (Backlog lanes, Cycle loop).\n\n### 3. The Direction\n- **`docs/BEARING.md`**: Current execution gravity and active tensions.\n- **`docs/design/README.md`**: Active design packets and structural doctrine.\n- **`docs/method/backlog/`**: The active source of truth for pending work.\n\n### 4. The Proof\n- **`CHANGELOG.md`**: Historical truth of merged behavior.\n- **`docs/audit/`**: Structural health and due diligence reports.\n\n## Context Recovery Protocol\n\nWhen starting a new session or recovering from context loss:\n\n1. **Read `docs/BEARING.md`** to find the current execution gravity.\n2. **Read `docs/METHOD.md`** to understand the work doctrine.\n3. **Check `docs/method/backlog/asap/`** for imminent work.\n4. **Check `git log -n 5` and `git status`** to verify the current branch state.\n\n## End of Turn Checklist\n\nAfter altering files:\n\n1. **Verify Truth**: Ensure documentation is updated if behavior or structure changed.\n2. **Log Debt**: Add follow-on backlog items to `bad-code/` or `cool-ideas/`.\n3. **Commit**: Use focused, conventional commit messages. Propose a draft before executing.\n4. **Validate**: Run `pnpm run preflight`.\n\n---\n**The goal is inevitably. Every feature is defined by its tests.**\n\n",{"_383":545,"_364":365,"_385":371},{"_386":546,"_388":-5,"_41":-5,"_389":-5,"_94":547,"_90":391},[548,549],"developer",{"_45":551,"_90":536},{"_45":550,"_90":536},"\n## Skills\nA skill is a set of local instructions to follow that is stored in a `SKILL.md` file. Below is the list of skills that can be used. Each entry includes a name, description, and file path so you can open the source for full instructions when using a specific skill.\n### Available skills\n- imagegen: Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output should be a bitmap asset rather than repo-native code or vector. Do not use when the task is better handled by editing existing SVG/vector/code-native assets, extending an established icon or logo system, or building the visual directly in HTML/CSS/canvas. (file: /opt/codex/skills/.system/imagegen/SKILL.md)\n- openai-docs: Use when the user asks how to build with OpenAI products or APIs and needs up-to-date official documentation with citations, help choosing the latest model for a use case, or model upgrade and prompt-upgrade guidance; prioritize OpenAI docs MCP tools, use bundled references only as helper context, and restrict any fallback browsing to official OpenAI domains. (file: /opt/codex/skills/.system/openai-docs/SKILL.md)\n- plugin-creator: Create and scaffold plugin directories for Codex with a required `.codex-plugin/plugin.json`, optional plugin folders/files, and baseline placeholders you can edit before publishing or testing. Use when Codex needs to create a new local plugin, add optional plugin structure, or generate or update repo-root `.agents/plugins/marketplace.json` entries for plugin ordering and availability metadata. (file: /opt/codex/skills/.system/plugin-creator/SKILL.md)\n- skill-creator: Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Codex's capabilities with specialized knowledge, workflows, or tool integrations. (file: /opt/codex/skills/.system/skill-creator/SKILL.md)\n- skill-installer: Install Codex skills into $CODEX_HOME/skills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private repos). (file: /opt/codex/skills/.system/skill-installer/SKILL.md)\n### How to use skills\n- Discovery: The list above is the skills available in this session (name + description + file path). Skill bodies live on disk at the listed paths.\n- Trigger rules: If the user names a skill (with `$SkillName` or plain text) OR the task clearly matches a skill's description shown above, you must use that skill for that turn. Multiple mentions mean use them all. Do not carry skills across turns unless re-mentioned.\n- Missing/blocked: If a named skill isn't in the list or the path can't be read, say so briefly and continue with the best fallback.\n- How to use a skill (progressive disclosure):\n 1) After deciding to use a skill, open its `SKILL.md`. Read only enough to follow the workflow.\n 2) When `SKILL.md` references relative paths (e.g., `scripts/foo.py`), resolve them relative to the skill directory listed above first, and only consider other paths if needed.\n 3) If `SKILL.md` points to extra folders such as `references/`, load only the specific files needed for the request; don't bulk-load everything.\n 4) If `scripts/` exist, prefer running or patching them instead of retyping large code blocks.\n 5) If `assets/` or templates exist, reuse them instead of recreating from scratch.\n- Coordination and sequencing:\n - If multiple skills apply, choose the minimal set that covers the request and state the order you'll use them.\n - Announce which skill(s) you're using and why (one short line). If you skip an obvious skill, say why.\n- Context hygiene:\n - Keep context small: summarize long sections instead of pasting them; only load extra files when needed.\n - Avoid deep reference-chasing: prefer opening only files directly linked from `SKILL.md` unless you're blocked.\n - When variants exist (frameworks, providers, domains), pick only the relevant reference file(s) and note that choice.\n- Safety and fallback: If a skill can't be applied cleanly (missing files, unclear instructions), state the issue, pick the next-best approach, and continue.\n","\nFilesystem sandboxing defines which files can be read or written. `sandbox_mode` is `danger-full-access`: No filesystem sandboxing - all commands are permitted. Network access is enabled.\nApproval policy is currently never. Do not provide the `sandbox_permissions` for any reason, commands will be rejected.\n","turn/started",{"_364":365,"_85":554},{"_101":-5,"_41":371,"_372":555,"_374":375,"_376":556},[],"inProgress",{"_376":558,"_364":365},{"_559":560,"_90":561},"activeFlags",[],"active","thread/started",{"_564":565},"thread",{"_566":-5,"_567":-5,"_568":569,"_570":375,"_430":431,"_571":15,"_572":-5,"_573":-5,"_41":365,"_574":575,"_179":-5,"_159":576,"_577":207,"_435":578,"_376":579,"_75":580,"_581":375},"agentNickname","agentRole","cliVersion","0.124.0","createdAt","ephemeral","forkedFromId","gitInfo","modelProvider","openai","/opt/codex/sessions/2026/05/22/rollout-2026-05-22T09-34-58-019e4f09-b9af-79c1-a2bb-b6ff3195adbe.jsonl","preview","vscode",{"_90":380},[],"updatedAt",[],"messages",[585],{"_41":586,"_587":588,"_589":590,"_591":590,"_386":592,"_376":593,"_388":-5,"_594":31,"_595":596,"_597":598,"_599":-5},"5bfb3330-1e1c-4d88-aad0-4bd1794c7ff0","author",{"_94":320,"_179":-5,"_595":608},"create_time",1779442496.896797,"update_time",{"_604":45,"_605":606},"finished_successfully","weight","metadata",{"_600":601},"recipient","all","channel","l1239dk1",{"_602":603},"inline_comments",[],"content_type","parts",[607],"## Self-Code Review Resolution\n\n@codex follow-up commit `9789f8e3` resolves the remaining `docs/README.md` front-door drift from comment `4517010571`.\n\n| Original severity | Resolution |\n| --- | --- |\n| Medium | `docs/README.md` now marks v0.0.5 clean-house / packet `0012` as shipped release context and names v0.0.6 Rust IR parity / packet `0013` as the active release center. |\n\nValidation after the fix:\n\n- `cargo xtask docs-check`\n- `git diff --check`\n- `pnpm run preflight`\n- push hook repository preflight\nexpand parity fixture coverage\n\n## Summary\n\n- Reset `docs/BEARING.md` for the v0.0.6 Rust IR parity and module-boundary release lane.\n- Replaced pending v0.0.5 publication wording with the concrete release, tag, workflow, and crates.io evidence.\n- Pulled `SOURCE_wesley-core-rs-parity-sentinel.md` out of `asap` into design packet `0013-rust-ir-parity-sentinel`.\n- Expanded the Rust L1 fixture corpus with directive-heavy, schema-extension, legacy-alias, and invalid duplicate-directive coverage.\n- Canonicalized the current core Wesley directive aliases in Rust L1 lowering and rejected duplicate canonical directives.\n\n## Validation\n\n- `pnpm fixtures:ir`\n- `cargo fmt --check`\n- `cargo test -p wesley-core --test lowering_validation`\n- `cargo xtask docs-check`\n- `git diff --check`\n- `pnpm run preflight`\n- Pre-push hook: repository preflight and repo Bats smoke suite\n\n## Notes\n\n`~/git/wesley-postgres` was inspected but not edited. It remains active as the PostgreSQL extraction home; local `main` is ahead of `origin/main` with `.gitignore` modified and `Cargo.toml`/`src/` untracked.\n\n\n\n## Summary by CodeRabbit\n\n* **New Features**\n * Added comprehensive test fixtures and validation for schema directives with multiple scenarios (directive-heavy, schema extensions, and legacy directive aliases).\n * Introduced IR parity sentinel design for upcoming release verification.\n\n* **Bug Fixes**\n * Fixed duplicate directive handling to properly reject invalid schemas instead of silently overwriting directives.\n\n* **Documentation**\n * Updated release verification and publication evidence documentation.\n * Expanded design documentation for schema validation and compiler parity checks.\n * Revised roadmap focusing on IR parity and module boundary enforcement.\n\n* **Tests**\n * Added integration tests for directive canonicalization and duplicate detection across multiple schema scenarios.\n\n\n\n[![Review Change Stack](https://storage.googleapis.com/coderabbit_public_assets/review-stack-in-coderabbit-ui.svg)](https://app.coderabbit.ai/change-stack/flyingrobots/wesley/pull/513?utm_source=github_walkthrough&utm_medium=github&utm_campaign=change_stack)\n\n\n\n\n\n\n\n> [!WARNING]\n> ## Rate limit exceeded\n> \n> `@flyingrobots` has exceeded the limit for the number of commits that can be reviewed per hour. Please wait **13 minutes and 5 seconds** before requesting another review.\n> \n> You’ve run out of usage credits. Purchase more in the [billing tab](https://app.coderabbit.ai/settings/subscription?tab=usage&tenantId=4252c417-78a1-49cd-a607-68d1e6bdacc4).\n> \n>

\n>

⌛ How to resolve this issue?

\n> \n> After the wait time has elapsed, a review can be triggered using the `@coderabbitai review` command as a PR comment. Alternatively, push new commits to this PR.\n> \n> We recommend that you space out your commits to avoid hitting the rate limit.\n> \n>

\n> \n> \n>

\n>

🚦 How do rate limits work?

\n> \n> CodeRabbit enforces hourly rate limits for each developer per organization.\n> \n> Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.\n> \n> Please see our [FAQ](https://docs.coderabbit.ai/faq) for further information.\n> \n>

\n> \n>

\n>

ℹ️ Review info

\n> \n>

\n>

⚙️ Run configuration

\n> \n> **Configuration used**: Path: .coderabbit.yaml\n> \n> **Review profile**: CHILL\n> \n> **Plan**: Pro\n> \n> **Run ID**: `9045b028-a14f-41f7-81fa-f61c7b6e5894`\n> \n>

\n> \n>

\n>

📥 Commits

\n> \n> Reviewing files that changed from the base of the PR and between 483439d47f3754d00f9c836dfb9ab8118f6c3ecb and 0ac0e6450fc06665d0d46a617b897e3efe8fcf62.\n> \n>

\n> \n>

\n>

📒 Files selected for processing (6)

\n> \n> * `CHANGELOG.md`\n> * `crates/wesley-core/src/adapters/apollo.rs`\n> * `crates/wesley-core/tests/lowering_validation.rs`\n> * `docs/BEARING.md`\n> * `docs/design/0009-rust-core-and-wasm-capability-abi/phase-0-ir-truth-manifest.md`\n> * `docs/design/0013-rust-ir-parity-sentinel/rust-ir-parity-sentinel.md`\n> \n>

\n> \n>

\n\n\n\n\n\n

📝 Walkthrough

\n\n## Walkthrough\n\nThis PR establishes the Rust IR parity foundation for v0.0.6 by implementing directive canonicalization in the Apollo lowering adapter, expanding the fixture corpus with three new test schemas covering directive-heavy, legacy-alias, and schema-extension patterns, and introducing design packet 0013 specifying the parity sentinel verification workflow.\n\n## Changes\n\n**Rust IR Parity Foundation**\n\n|Layer / File(s)|Summary|\n|---|---|\n|**Directive Canonicalization and Duplicate Rejection**
`crates/wesley-core/src/adapters/apollo.rs`|Apollo adapter now canonicalizes directive aliases (e.g., `table`, `pk`) to Wesley-internal canonical names and rejects duplicate canonical directives with a lowering error instead of last-write-wins behavior.|\n|**Lowering Validation Tests for Canonicalization and Duplicates**
`crates/wesley-core/tests/lowering_validation.rs`|New Tokio async tests validate fixture lowering and assert that legacy directive aliases are canonicalized correctly and that duplicate canonical directives fail with expected error messages.|\n|**Directive-Heavy Schema Fixture**
`test/fixtures/ir-parity/directive-heavy-schema.graphql`, `directive-heavy-schema.l1.json`, `directive-heavy-schema.l1.hash`|Multi-type fixture with extensive `@wes_*` directive coverage including table mappings, keys/constraints, defaults, and RLS policies across Organization, Account, and AccountEvent types, with canonical L1 IR and hash artifacts.|\n|**Legacy-Alias Schema Fixture**
`test/fixtures/ir-parity/legacy-alias-schema.graphql`, `legacy-alias-schema.l1.json`, `legacy-alias-schema.l1.hash`|Tenant and Member types using both canonical and legacy-alias directive forms to validate canonicalization during lowering, provided as GraphQL source and canonical L1 IR JSON with hash.|\n|**Schema-Extensions Fixture**
`test/fixtures/ir-parity/schema-extensions-schema.graphql`, `schema-extensions-schema.l1.json`, `schema-extensions-schema.l1.hash`|Comprehensive fixture covering scalar extensions, interface composition, unions, enum extensions, and input objects with defaults, including User and Team types with timestamps and relationships, provided as GraphQL and canonical L1 IR with hash.|\n|**Invalid Fixture for Negative Testing**
`test/fixtures/ir-parity-invalid/duplicate-directive-alias.graphql`|Account type fixture declaring the same directive in both canonical and legacy forms to validate that the lowerer correctly rejects duplicate-directive errors.|\n|**Design Packet 0013 and IR Truth Manifest**
`docs/design/0013-rust-ir-parity-sentinel/rust-ir-parity-sentinel.md`, `docs/design/0009-rust-core-and-wasm-capability-abi/phase-0-ir-truth-manifest.md`, `docs/design/README.md`|New design document specifying the Rust IR Parity Sentinel comparator contract (fixture inputs, normalized semantic IR comparison, hash verification, failure diagnostics); phase-0 manifest updated with invalid fixture documentation and fixture-hash catalog; design README reference added.|\n|**BEARING Roadmap and ASAP Backlog Reframing**
`docs/BEARING.md`, `docs/method/backlog/asap/README.md`|BEARING reframed around v0.0.6 Rust IR parity and module-boundary enforcement with updated timeline, Parity Sentinel section, module-boundary emphasis, and revised tensions/next-target plan; ASAP backlog shortened to Rust IR parity evidence and domain-empty boundary work.|\n|**v0.0.5 Release Evidence and Changelog**
`docs/method/releases/v0.0.5/verification.md`, `CHANGELOG.md`|v0.0.5 verification section filled with publication evidence (signed tag, GitHub Release, CI runs, crates.io confirmations); CHANGELOG updated with Unreleased entries documenting directive canonicalization, fixture expansion, and bearing refinements.|\n\n## Estimated code review effort\n\n🎯 3 (Moderate) | ⏱️ ~25 minutes\n\n## Suggested labels\n\n`enhancement`\n\n## Poem\n\n> 🐰 *Directives now stand tall and true,* \n> *Canonicalized through and through,* \n> *With fixtures broad and parity bright,* \n> *The Rust compiler takes flight—* \n> *No more silent semantic drift in view!* 🚀\n\n

\n\n\n\n\n

🚥 Pre-merge checks | ✅ 3 | ❌ 2

\n\n### ❌ Failed checks (1 warning, 1 inconclusive)\n\n| Check name | Status | Explanation | Resolution |\n| :----------------: | :------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| Docstring Coverage | ⚠️ Warning | Docstring coverage is 72.73% which is insufficient. The required threshold is 80.00%. | Write docstrings for the functions missing them to satisfy the coverage threshold. |\n| Description check | ❓ Inconclusive | The PR description covers the main changes and includes a validation section with testing steps, but omits several required template sections (Why/Rationale, Risk, Backout, EvidenceMap/SourceMap). | Complete the PR description by adding Why/Rationale for the parity approach, Risk/mitigation notes, Backout strategy, and any EvidenceMap confirmations if applicable. |\n\n

✅ Passed checks (3 passed)

\n\n| Check name | Status | Explanation |\n| :------------------------: | :------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| Title check | ✅ Passed | The title clearly summarizes the main change: expanding the parity fixture coverage with new test fixtures for directive-heavy schemas, schema extensions, legacy aliases, and invalid cases. |\n| Linked Issues check | ✅ Passed | Check skipped because no linked issues were found for this pull request. |\n| Out of Scope Changes check | ✅ Passed | Check skipped because no linked issues were found for this pull request. |\n\n

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

\n\n\n\n\n

✨ Finishing Touches

\n\n

🧪 Generate unit tests (beta)

\n\n- [ ] Create PR with unit tests\n- [ ] Commit unit tests in branch `codex/v0.0.6-bearing`\n\n

\n\n

\n\n\n\n\n---\n\nThanks for using [CodeRabbit](https://coderabbit.ai?utm_source=oss&utm_medium=github&utm_campaign=flyingrobots/wesley&utm_content=513)! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.\n\n

❤️ Share

\n\n- [X](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai)\n- [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai)\n- [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai)\n- [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)\n\n

\n\n\n_{Comment `@coderabbitai help` to get the list of available commands and usage tips.}\n\n\n\n\n\n\n\n\n\n\n# 🔍 The Case of Pull Request #513\n\n## Plain-English Readout\n\n- **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.\n- **Watson (independent verification)**: Watson found verification concerns. Most important concern: Low migration risk claimed but schema incomplete.\n- **Moriarty (trend forecast)**: Moriarty sees progress as stalled right now, so forecast confidence is limited.\n\n## Suggested next actions\n\n1. Tighten citations so the report points to exact lines instead of whole files or coarse references.\n2. Resolve Watson’s verification concerns before trusting the Holmes verdict as final.\n3. Treat the readiness forecast as stalled until new evidence or real progress moves the trend again.\n4. Add or strengthen tests for the schema elements and operations HOLMES flagged as weakly proven.\n\n

📚 Glossary (what the Holmes terms mean)

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

\n\n---\n\n

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

\n\n### 🕵️ SHA-lock HOLMES Investigation\n\n- Generated: 2026-05-22T08:04:37.673Z\n- Commit SHA: 9fe1fbfac851cab61a482766420494a5bdea04ff\n- Bundle Version: 2.0.0\n\n> ⚠️ Evidence valid only for commit `9fe1fbf`\n\n## 🔍 Executive Deduction\n\n\"Watson, after careful examination of the evidence, I deduce...\"\n\n**Weighted Completion**: ░░░░░░░░░░ 0.0%\n**Scores**: SCS 0.0% · TCI 0.0% · MRI 0.0%\n**Verification Status**: 0 claims verified\n**Citation Quality**: 0 exact · 0 whole-file · 0 coarse\n**Evidence Trust**: missing\n**Ship Verdict**: YOU SHALL NOT PASS\n\n## 🧩 SCS Breakdown\n\n| Component | Score | Coverage |\n|-----------|-------|----------|\n| Sql | 0.0% | 0.00/154.00 |\n| Types | 0.0% | 0.00/154.00 |\n| Validation | 0.0% | 0.00/154.00 |\n| Tests | 0.0% | 0.00/154.00 |\n\n## 🧪 TCI Breakdown\n\n| Component | Score | Coverage | Note |\n|-----------|-------|----------|------|\n| Unit Constraints | 0.0% | 0/104 | N/A |\n| Unit Rls | 0.0% | — | N/A |\n| Integration Relations | 0.0% | 0/3 | N/A |\n| E2e Ops | N/A | — | Query operation test tracking not yet implemented |\n\n## ⚠️ MRI Breakdown\n\n| Component | Risk Share | Points | Count |\n|-----------|------------|--------|-------|\n| Drops | 0% | 0 | 0 |\n| Renames Without Uid | 0% | 0 | 0 |\n| Add Not Null Without Default | 0% | 0 | 0 |\n| Non Concurrent Indexes | 0% | 0 | 0 |\n\n## 📊 The Weight of Evidence\n\n\"Observe, Watson, how not all features carry equal importance...\"\n\n| Element | Weight | Status | Evidence | Strength | Deduction |\n|---------|--------|--------|----------|----------|-----------|\n\n## 🚪 Security & Performance Gates\n\n\"Elementary security measures, Watson...\"\n\n| Gate | Status | Evidence | Holmes's Ruling |\n|------|--------|----------|-----------------|\n| Migration Risk | ✅ | MRI: 0.0% | \"Trivial risk\" |\n| Test Coverage | ⚠️ | TCI: 0.0% | \"Theatrical tests!\" |\n| Sensitive Fields | ✅ | 0 fields | \"All secured\" |\n| Evidence Quality | ⛔ | 0 exact · 0 whole-file · 0 coarse | \"No evidence citations were available for trust analysis.\" |\n\n## 📋 The Verdict\n\n⛔ **YOU SHALL NOT PASS**\n\"Critical evidence is missing! Return to your laboratory!\"\n\nSigned and sealed,\n- S. Holmes, Consulting Detective\n\n[END OF INVESTIGATION FOR COMMIT 9fe1fbf]\n\n## 🧵 Command Run\n\n- Run ID: run-mpgmwtsy-y0c4uv\n- Transmutation: holmes-investigate\n- Command: investigate\n- Status: completed\n- Ledger: /home/runner/work/wesley/wesley/test/fixtures/examples/.wesley-cache/ledger\n\n

\n\n---\n\n

🩺 Dr. WATSON full report (click to expand)

\n\n### 🩺 Dr. Watson's Independent Verification Report\n\n_Medical Examination of Evidence_\n\n- Examination Date: 2026-05-22T08:05:41.039Z\n- Patient SHA: 9fe1fbfac851cab61a482766420494a5bdea04ff\n\n## 🔬 Citation Verification\n\n\"Let me examine each piece of evidence independently...\"\n\n- **Citations Examined**: 0\n- **Verified**: 0 ✅\n- **Failed**: 0 ❌\n- **Unable to Verify**: 0\n- **Exact Subrange Citations**: 0\n- **Whole-file Citations**: 0\n- **Coarse Citations**: 0\n- **Evidence Trust**: missing\n- **Trust Note**: No evidence citations were available for trust analysis.\n\n**Verification Rate**: 0.0%\n\n## 📊 Mathematical Verification\n\n\"I shall recalculate Holmes's arithmetic...\"\n\nHolmes claimed SCS: 0.0%\nWatson calculates: 0.0%\nDifference: ✅ Negligible\n\n## 🔍 Consistency Analysis\n\n\"Checking for contradictions in Holmes's deductions...\"\n\n⚠️ Low migration risk claimed but schema incomplete\n\n## 🩺 Dr. Watson's Medical Opinion\n\n**VERIFICATION: CONCERNS NOTED** ⚠️\n\n\"While Holmes's methods are generally sound, I have noted some\"\n\"discrepancies that warrant further investigation. No evidence citations were available for trust analysis.\"\n\nRespectfully submitted,\n- Dr. J. Watson, M.D.\n Medical Examiner & Verification Specialist\n\n## 🧵 Command Run\n\n- Run ID: run-mpgmxhd1-cptc1c\n- Transmutation: watson-verify\n- Command: verify\n- Status: completed\n- Ledger: /home/runner/work/wesley/wesley/test/fixtures/examples/.wesley-cache/ledger\n\n

\n\n---\n\n

🔮 Professor MORIARTY full report (click to expand)

\n\n### 🧠 Professor Moriarty's Temporal Predictions\n\n_The Mathematics of Inevitability_\n\n- Analysis Date: 2026-05-22T08:06:21.204Z\n\n## 🔮 Current State\n\n**SCS**: ░░░░░░░░░░ 0.0%\n**TCI**: ░░░░░░░░░░ 0.0%\n**MRI**: 0.0% risk\n**Evidence Trust**: missing\n\n## 📈 Velocity Analysis\n\n**SCS Velocity**: +0.00%/day\n**Git Activity (window)**: 24h · commits 14 (1 relevant) · ~14.00 commits/day\n↳ Magnitude: ~313 relevant LOC/day across ~6.0 files/day\n**Activity Index**: 25 / 100 (PR 0, Window 62)\n**Blended Velocity**: +0.15%/day\n**Commit Size Burstiness**: 0 / 100 (higher = more uneven commit sizes)\n⚠️ **PLATEAU DETECTED** - Low SCS movement and low recent Git activity.\n\n## ⏰ Completion Predictions\n\n**ETA**: Cannot predict (insufficient velocity)\n\n\"At current velocity, completion is... improbable.\"\n\n## ⚠️ Warnings\n\n- Evidence trust is missing; No evidence citations were available for trust analysis.\n\n## 🧪 Readiness EXPLAIN\n\n- SCS ≥ 80% → FAIL ❌ (actual 0.0%)\n- TCI ≥ 70% → FAIL ❌ (actual 0.0%)\n- MRI ≤ 40% → PASS ✅ (actual 0.0%)\n- CI Stability ≥ 90% (branch main) → FAIL ❌ (actual 87% over ~168h)\n- Evidence Trust ≥ moderate → FAIL ❌ (actual missing) — No evidence citations were available for trust analysis.\n- Delivery context (last 168h): 0 issues closed · 4 PRs merged (informational, not gating)\n\n_Signals blend:_ SCS velocity (70%) + Git activity (30%, branch-first). Activity only suppresses false plateaus; it never inflates readiness.\n\n## 📊 Historical Trajectory\n\n05-22: ░░░░░░░░░░ 0.0%\n05-22: ░░░░░░░░░░ 0.0%\n05-22: ░░░░░░░░░░ 0.0%\n\n*\"Every problem becomes elementary when reduced to mathematics\"*\n— Professor Moriarty\n\n## 🧵 Command Run\n\n- Run ID: run-mpgmyccy-9565tx\n- Transmutation: moriarty-predict\n- Command: predict\n- Status: completed\n- Ledger: /home/runner/work/wesley/wesley/test/fixtures/examples/.wesley-cache/ledger\n\n

\n\n---\n\n_Machine-readable reports:_ holmes-report.json · watson-report.json · moriarty-report.json (see workflow artifacts).\n\n---\n\n*Filed at 221B Repository Street*\n\n## Self-Code Review Findings\n\n@codex please confirm whether you agree with these findings before merge. Review basis: local clean worktree, `git fetch origin --prune`, then `git diff origin/main...HEAD`.\n\n| Severity | File / line | Type | Evidence | Recommended mitigation prompt |\n| --- | --- | --- | --- | --- |\n| High | `crates/wesley-core/src/adapters/apollo.rs:507` | Logical regression / unintended compatibility break | The new duplicate check runs for every directive name after `canonical_directive_name`, not only for Wesley aliases. Valid GraphQL SDL with a repeatable non-Wesley directive now fails: `directive @tag(name: String!) repeatable on FIELD_DEFINITION` plus `@tag(name: \"a\") @tag(name: \"b\")` exits with `Lowering error: Duplicate directive '@tag' in directive`. | `Narrow Rust duplicate-directive rejection so it only rejects canonical collisions for the supported core Wesley directive aliases, or implement explicit repeatable-directive support in L1. Add a regression test proving non-Wesley repeatable directives are either preserved correctly or rejected by a documented unsupported-feature diagnostic rather than by the generic duplicate alias path.` |\n| Medium | `docs/design/0013-rust-ir-parity-sentinel/rust-ir-parity-sentinel.md:49` | Design contract gap | The packet says the sentinel records and compares legacy JS semantic IR bytes against Rust semantic IR bytes, but the named JS anchor emits a table IR shape with `tables`, `enums`, `scalars`, and `relationships` (`packages/wesley-runtime-node/src/GraphQLAdapter.mjs:148`), while Rust L1 fixtures emit `types`. The packet never defines a projection or equivalence layer, so the next implementation slice has no coherent comparator contract. | `Revise the parity sentinel packet to define the comparison projection explicitly: either compare only a documented common semantic subset, introduce a JS-to-L1/Rust-to-legacy normalization adapter, or exclude non-overlapping fixtures until a real crosswalk exists. Add playback questions that force the implementation to prove the chosen projection.` |\n| Medium | `docs/BEARING.md:77` | Documentation reproducibility / transient local state | `BEARING.md` commits a machine-local path and ephemeral sibling-repo worktree state: `~/git/wesley-postgres` has local `main` ahead of `origin/main` and uncommitted bootstrap work. That is useful session evidence, but not stable project direction and will become stale immediately. | `Replace the local path/worktree-status sentence with stable repository-level doctrine: wesley-postgres is the database extraction authority and Wesley should coordinate before changing database-shaped compatibility seams. Move the exact local inspection result to PR notes or session memory instead of committed BEARING text.` |\n| Low | `docs/BEARING.md:108` | Planning drift / stale next-action list | The `Next Target` list still tells the next agent to keep v0.0.5 publication evidence complete and expand the L1 fixture corpus, but this branch already does both. After merge, BEARING should point to the remaining next moves, not replay completed work. | `Update the BEARING next-target list so completed slices are recorded as current evidence, and the remaining active pulls start with implementing the parity sentinel command, defining the IR projection/crosswalk, and pulling domain-empty core boundary enforcement.` |\n\nIssue count: High 1, Medium 2, Low 1.\n_⚠️ Potential issue_ | _🟡 Minor_ | _⚡ Quick win_\n\n**Avoid machine-local path/state in shared roadmap docs.**\n\nLine 77 and Line 78 encode host-specific state (`~/git/...`, local `main` ahead of `origin/main`) that will quickly go stale and cannot be validated by other contributors. Prefer repository-relative/remote references plus a dated note in release evidence docs.\n\n

🤖 Prompt for AI Agents

\n\n```\nVerify each finding against current code. Fix only still-valid issues, skip the\nrest with a brief reason, keep changes minimal, and validate.\n\nIn `@docs/BEARING.md` around lines 77 - 79, Replace the machine-local path and\nhost-specific branch state in BEARING.md: remove the literal\n\"`~/git/wesley-postgres`\" and the note \"local `main` ahead of `origin/main`\" and\ninstead reference the repository by its remote name or repo URL (e.g.,\n\"wesley-postgres\" or the remote Git URL) and, if necessary, add a dated note in\nrelease evidence or changelog indicating the local bootstrap work and its date;\nupdate the surrounding sentence that mentions PostgreSQL/Supabase generation and\nexecution adapters to use the repository-relative/remote reference and add the\ndate/context note rather than machine-local state.\n```\n\n

\n\n\n\n\n\n✅ Addressed in commit 0ac0e64\n**Actionable comments posted: 1**\n\n

🧹 Nitpick comments (1)

\n\n
\n
crates/wesley-core/src/adapters/apollo.rs (1)
\n\n`960-972`: _⚡ Quick win_\n\n**Consider adding a doc comment to explain the canonicalization contract.**\n\nThe function correctly implements the alias-to-canonical mapping, but a doc comment would clarify the purpose and supported aliases for future maintainers.\n\n\n\n
\n
📝 Suggested doc comment
\n\n```diff\n+/// Maps legacy Wesley directive aliases to their canonical internal names.\n+///\n+/// This normalization ensures that directives declared with different aliases\n+/// (e.g., `@table`, `@wesley_table`) are recognized as the same directive\n+/// and stored under a single canonical key (`wes_table`).\n+///\n+/// Returns the canonical name if a mapping exists, otherwise returns the input unchanged.\n fn canonical_directive_name(name: &str) -> &str {\n match name {\n```\n
\n\n
\n
🤖 Prompt for AI Agents
\n\n```\nVerify each finding against current code. Fix only still-valid issues, skip the\nrest with a brief reason, keep changes minimal, and validate.\n\nIn `@crates/wesley-core/src/adapters/apollo.rs` around lines 960 - 972, Add a\nconcise doc comment for the function canonical_directive_name describing its\ncontract: that it maps known directive aliases (list the aliases and their\ncanonical names like \"wesley_table\"/\"table\" -> \"wes_table\",\n\"wesley_pk\"/\"pk\"/\"primaryKey\" -> \"wes_pk\", etc.), that it returns a borrowed\n&str of the canonical name (does not allocate), and that unknown names are\nreturned unchanged; include purpose and examples of expected inputs/outputs so\nfuture maintainers understand supported aliases and return semantics.\n```\n\n
\n\n
\n\n

\n\n

🤖 Prompt for all review comments with AI agents

\n\n```\nVerify each finding against current code. Fix only still-valid issues, skip the\nrest with a brief reason, keep changes minimal, and validate.\n\nInline comments:\nIn `@docs/BEARING.md`:\n- Around line 77-79: Replace the machine-local path and host-specific branch\nstate in BEARING.md: remove the literal \"`~/git/wesley-postgres`\" and the note\n\"local `main` ahead of `origin/main`\" and instead reference the repository by\nits remote name or repo URL (e.g., \"wesley-postgres\" or the remote Git URL) and,\nif necessary, add a dated note in release evidence or changelog indicating the\nlocal bootstrap work and its date; update the surrounding sentence that mentions\nPostgreSQL/Supabase generation and execution adapters to use the\nrepository-relative/remote reference and add the date/context note rather than\nmachine-local state.\n\n---\n\nNitpick comments:\nIn `@crates/wesley-core/src/adapters/apollo.rs`:\n- Around line 960-972: Add a concise doc comment for the function\ncanonical_directive_name describing its contract: that it maps known directive\naliases (list the aliases and their canonical names like \"wesley_table\"/\"table\"\n-> \"wes_table\", \"wesley_pk\"/\"pk\"/\"primaryKey\" -> \"wes_pk\", etc.), that it\nreturns a borrowed &str of the canonical name (does not allocate), and that\nunknown names are returned unchanged; include purpose and examples of expected\ninputs/outputs so future maintainers understand supported aliases and return\nsemantics.\n```\n\n

\n\n

🪄 Autofix (Beta)

\n\nFix all unresolved CodeRabbit comments on this PR:\n\n- [ ] Push a commit to this branch (recommended)\n- [ ] Create a new PR with the fixes\n\n

\n\n---\n\n

ℹ️ Review info

\n\n

⚙️ Run configuration

\n\n**Configuration used**: Path: .coderabbit.yaml\n\n**Review profile**: CHILL\n\n**Plan**: Pro\n\n**Run ID**: `220b721d-b1df-403f-bdc5-7cd03e5c7394`\n\n

\n\n

📥 Commits

\n\nReviewing files that changed from the base of the PR and between fa42c71832520b70e55447e865e0425e467db2a5 and 483439d47f3754d00f9c836dfb9ab8118f6c3ecb.\n\n

\n\n

📒 Files selected for processing (20)

\n\n* `CHANGELOG.md`\n* `crates/wesley-core/src/adapters/apollo.rs`\n* `crates/wesley-core/tests/lowering_validation.rs`\n* `docs/BEARING.md`\n* `docs/design/0009-rust-core-and-wasm-capability-abi/phase-0-ir-truth-manifest.md`\n* `docs/design/0013-rust-ir-parity-sentinel/rust-ir-parity-sentinel.md`\n* `docs/design/README.md`\n* `docs/method/backlog/asap/README.md`\n* `docs/method/backlog/asap/SOURCE_wesley-core-rs-parity-sentinel.md`\n* `docs/method/releases/v0.0.5/verification.md`\n* `test/fixtures/ir-parity-invalid/duplicate-directive-alias.graphql`\n* `test/fixtures/ir-parity/directive-heavy-schema.graphql`\n* `test/fixtures/ir-parity/directive-heavy-schema.l1.hash`\n* `test/fixtures/ir-parity/directive-heavy-schema.l1.json`\n* `test/fixtures/ir-parity/legacy-alias-schema.graphql`\n* `test/fixtures/ir-parity/legacy-alias-schema.l1.hash`\n* `test/fixtures/ir-parity/legacy-alias-schema.l1.json`\n* `test/fixtures/ir-parity/schema-extensions-schema.graphql`\n* `test/fixtures/ir-parity/schema-extensions-schema.l1.hash`\n* `test/fixtures/ir-parity/schema-extensions-schema.l1.json`\n\n

\n\n

💤 Files with no reviewable changes (1)

\n\n* docs/method/backlog/asap/SOURCE_wesley-core-rs-parity-sentinel.md\n\n

\n\n

\n\n\n\n### 💡 Codex Review\n\nHere are some automated review suggestions for this pull request.\n\n**Reviewed commit:** `483439d47f`\n \n\n

ℹ️ About Codex in GitHub

\n
\n\n[Your team has set up Codex to review pull requests in this repo](https://chatgpt.com/codex/cloud/settings/general). Reviews are triggered when you\n- Open a pull request for review\n- Mark a draft as ready\n- Comment \"@codex review\".\n\nIf Codex has suggestions, it will comment; otherwise it will react with 👍.\n\n\n\n\nCodex can also answer questions or update the PR. Try commenting \"@codex address that feedback\".\n \n

\n**_{_{![P1 Badge](https://img.shields.io/badge/P1-orange?style=flat)}} Restrict duplicate rejection to canonical Wesley aliases**\n\nThe duplicate guard now checks `canonical_name` for every directive, so any repeatable non-Wesley directive (for example `@tag` declared as `repeatable`) is rejected even though the SDL is valid. I reproduced this by lowering a schema with `@tag(name: \"a\") @tag(name: \"b\")`, which now fails with `Lowering error: Duplicate directive '@tag' in directive`; this is a compatibility regression introduced by this change because the new logic conflates alias-collision protection with general repeatable-directive handling.\n\nUseful? React with 👍 / 👎.\n**_{_{![P2 Badge](https://img.shields.io/badge/P2-yellow?style=flat)}} Define an explicit JS↔Rust IR projection before byte compare**\n\nThe comparator contract says to compare legacy JS semantic IR bytes directly against Rust semantic IR bytes, but it does not define any crosswalk/projection despite the referenced JS anchor emitting a different IR shape (`tables/enums/scalars/relationships` in `packages/wesley-runtime-node/src/GraphQLAdapter.mjs`) than Rust L1 fixtures (`types`). Without a normalization/projection contract here, a parity sentinel implementation cannot distinguish expected structural differences from real regressions, so the design is currently non-executable as written.\n\nUseful? React with 👍 / 👎.\n**_{_{![P3 Badge](https://img.shields.io/badge/P3-lightgrey?style=flat)}} Remove machine-local worktree state from project bearing**\n\nThis commits a local filesystem path and transient sibling-repo branch/dirty-state snapshot into `BEARING.md`, which will become stale immediately for other contributors and CI contexts and does not provide durable repository direction. Keeping ephemeral workstation state in the canonical bearing doc harms reproducibility of planning context and should be moved to PR/session notes instead.\n\nUseful? React with 👍 / 👎.\n## Self-Code Review Resolution\n\n@codex follow-up commit `0ac0e645` resolves the four findings from comment `4516291171`.\n\n| Original severity | Resolution |\n| --- | --- |\n| High | Narrowed duplicate directive rejection to canonical core Wesley directives only. Repeated custom directives are now preserved as ordered arrays, with regression coverage for repeatable `@tag`. |\n| Medium | Updated design packet `0013` to require a named `js-table-vs-rust-table.v0` projection/crosswalk before comparing legacy JS table IR with Rust L1 bytes. |\n| Medium | Removed transient local `~/git/wesley-postgres` worktree status from committed BEARING text and kept only stable sibling-repo coordination doctrine. |\n| Low | Updated BEARING so completed publication-evidence and fixture-expansion slices are current evidence, while the next pulls are the remaining sentinel/projection/domain-boundary work. |\n\nValidation after the fix:\n\n- `cargo fmt --check`\n- `cargo test -p wesley-core --test lowering_validation`\n- `cargo clippy -p wesley-core --all-targets -- -D warnings`\n- `cargo xtask docs-check`\n- `git diff --check`\n- repeatable custom directive CLI reproduction now succeeds\n- `pnpm run preflight`\n- push hook repository preflight\n### Summary\n* Added a concise doc comment to `canonical_core_directive_name` clarifying alias-to-canonical mapping scope, borrowed return semantics, and passthrough behavior for non-core/custom directives, with concrete examples. [crates/wesley-core/src/adapters/apollo.rsL961-L970](https://github.com/flyingrobots/wesley/blob/0ac0e6450fc06665d0d46a617b897e3efe8fcf62/crates/wesley-core/src/adapters/apollo.rs#L961-L970)\n* Committed the change on the current branch as `e887bf8` with message: `docs(ir): document core directive alias canonicalization`. [crates/wesley-core/src/adapters/apollo.rsL961-L970](https://github.com/flyingrobots/wesley/blob/0ac0e6450fc06665d0d46a617b897e3efe8fcf62/crates/wesley-core/src/adapters/apollo.rs#L961-L970)\n\n**Testing**\n* ✅ `cargo fmt --check`\n* ✅ `cargo test -p wesley-core --test lowering_validation`\n* ✅ `pnpm run preflight` (passes; shows non-blocking engine warning for local Node v20 vs wanted >=22)\n\n [View task →](https://chatgpt.com/s/cd_6a100e38a6788191a0c5e3d80a78fcb3)\n## Self-Code Review Findings\n\n@codex please confirm before merge. Review basis: clean local worktree, `git fetch origin --prune`, then `git diff origin/main...HEAD`.\n\n| Severity | File / line | Type | Evidence | Recommended mitigation prompt |\n| --- | --- | --- | --- | --- |\n| Medium | `docs/README.md:33` | Documentation drift / front-door inconsistency | This branch resets `docs/BEARING.md` and `docs/method/backlog/asap/README.md` to v0.0.6 Rust IR parity work, but the docs front door still says “The active release center is now the v0.0.5 clean-house packet” and links only `0012-product-leftover-cleanup`. Because `docs/README.md` is an indexed public/front-door doc, this leaves readers with two contradictory active centers. | `Update docs/README.md Current Center Of Gravity so it states that v0.0.5 clean-house is shipped/historical evidence and v0.0.6 centers on Rust IR parity. Link both the shipped 0012 cleanup packet as background and the active 0013 parity sentinel packet as the current release packet. Run docs-check/preflight after the edit.` |\n\nIssue count: Medium 1.\n\n### 💡 Codex Review\n\nHere are some automated review suggestions for this pull request.\n\n**Reviewed commit:** `0ac0e6450f`\n \n\n

ℹ️ About Codex in GitHub

\n**_{_{![P2 Badge](https://img.shields.io/badge/P2-yellow?style=flat)}} Update docs front door for v0.0.6 release center**\n\nThis change declares `v0.0.6` as the active gravity in BEARING, but `docs/README.md` still says the active release center is `v0.0.5` (line 33 in that file), so the two top-level navigation docs now contradict each other about what is current. That inconsistency was introduced here and will misroute readers who start from the docs front door; please update `docs/README.md` in the same change to mark `v0.0.5` as shipped/history and point active work to the `0013` parity packet.\n\nUseful? React with 👍 / 👎.",{},"created",1779442532.4723043,"Completing the task","event_type","info",{"_90":391,"_94":91,"_386":817},{"_90":616,"_617":618},"partial_repo_snapshot","files",[619,620],{"_159":733,"_622":-5,"_623":734,"_625":-5},{"_159":621,"_622":-5,"_623":624,"_625":-5},"docs/BEARING.md","contents","line_range_contents",[626],"missing_reason",{"_627":628,"_629":630,"_386":631,"_632":57},"line_range_start",1,"line_range_end",126,[633,634,207,635,636,207,637,638,639,640,641,642,643,207,644,207,645,207,646,647,648,207,649,650,651,652,207,653,207,654,655,656,657,658,659,660,661,662,207,663,207,664,665,666,667,668,669,670,207,671,207,672,673,207,674,675,676,677,678,679,207,680,207,681,682,683,684,685,686,687,207,688,207,689,690,207,691,692,693,694,207,695,207,696,697,698,699,700,701,702,703,704,705,706,707,708,709,710,711,712,207,713,207,714,715,207,716,717,718,207,719,207,720,721,722,723,724,725,726,727,728,729,207,730,731,732],"contains_end_of_file","# BEARING","","Current direction and active tensions. Historical ship data is in","`CHANGELOG.md`.","```mermaid","timeline"," Phase 1 : v0.0.5 Shipped : Clean House : Domain-Empty Backlog"," Phase 2 : v0.0.6 : Rust IR Parity : Fixture Truth"," Phase 3 : Module Boundary : External Targets : Artifact Evidence"," Phase 4 : Core Release : Legacy Node Retirement : Postgres Module Cutover","```","## Active Gravity","### 1. v0.0.6 Rust IR Parity","The next Wesley hill is not another product lane. It is a compiler-truth","release that makes the Rust core harder to drift from the legacy JS lowering","surface while Wesley finishes moving toward one native compiler brain.","v0.0.5 closed the clean-house release. v0.0.6 should turn that cleanup into","evidence: richer canonical fixtures, clearer compatibility diagnostics, and a","separate JS/Rust parity sentinel that proves whether current Rust L1 bytes","still match the legacy truth anchors where they are expected to match.","### 2. Domain-Empty Core","- Wesley's identity is the core `GraphQL -> whatever` compiler and assurance"," toolchain.","- The `whatever` must come from explicitly loaded external modules, not"," built-in product or database semantics.","- Echo, jedit, Continuum, WARPspace, and `warp-ttd` behavior belongs in the"," owning repos or owning modules.","- PostgreSQL/Supabase behavior belongs in `wesley-postgres`, not in"," `wesley-core`, Wesley generators, generic host packages, or generic task"," execution packages.","### 3. Rust L1 Fixture Truth","- Treat the Rust workspace as the primary compiler surface.","- Expand the canonical fixture corpus before broad rewrites.","- Keep nondeterministic metadata out of parity-sensitive IR bytes.","- Preserve directive spelling, alias normalization, extension folding, and"," invalid-SDL diagnostics as explicit tests instead of tribal knowledge.","- Keep jedit-shaped consumer fixtures as compiler coverage, not as jedit"," product ownership.","### 4. Parity Sentinel Before Retirement","`pnpm fixtures:ir` regenerates Rust L1 golden files. It is not JS/Rust parity","proof.","The new sentinel work lives in","[0013-rust-ir-parity-sentinel](./design/0013-rust-ir-parity-sentinel/rust-ir-parity-sentinel.md).","It should compare normalized semantic IR from the legacy JS lowerer and the","Rust lowerer over an explicit corpus, then fail with a useful mismatch path and","hash evidence. Only after that evidence exists should Wesley retire or demote","legacy Node lowering.","### 5. Module Capability Boundary","- Use the module capability registry as the seam between loaded modules and"," Wesley base verbs.","- Keep `wesley compile` dispatching only through module-owned `wesley.targets`.","- Keep Wesley core CI independent of external product and database repos by"," exercising hermetic fixture modules across supported capability collections.","- Move product/runtime/database semantics to owning repos or modules before"," deleting generic compatibility evidence that external consumers still need.","### 6. Wesley-Postgres Preservation","`wesley-postgres` is the PostgreSQL-family extraction home. It is active and","must not be abandoned while Wesley tightens its domain-empty boundary.","That repo remains the home for PostgreSQL/Supabase generation, PostgreSQL","execution adapters, and database safety primitives. Wesley should coordinate","by preserving generic module seams and avoiding new database semantics in the","base platform.","## Tensions","- **Two-Brain Confusion**: Rust and Node surfaces still coexist. The intended"," shape is one compiler brain (`crates/wesley-core`), one native command body"," (`crates/wesley-cli`), and legacy Node support surfaces under `packages/`"," until ported, extracted, or retired.","- **Fixture Churn**: IR, hash, directive, or generated-artifact changes can"," affect Echo and jedit fixtures. Those changes need explicit compatibility"," notes rather than accidental hash churn.","- **Alias Semantics**: Legacy directive aliases are compatibility input, not a"," license to preserve arbitrary spelling in semantic Rust L1 output.","- **Invalid Diagnostics**: The Rust lowerer can reject invalid SDL, but stable"," codes and spans are not yet part of the L1 fixture contract.","- **External Module Gap**: Wesley can name the domain-empty boundary, but"," external modules still need enough capability runtime and artifact evidence"," to consume it cleanly.","- **Sibling Repo Coordination**: Wesley should reference `wesley-postgres` as"," the database authority without editing or overwriting sibling work from this"," repo.","## Next Target","The immediate focus is **v0.0.6 Rust IR parity and module-boundary","enforcement**:","Current evidence now includes complete v0.0.5 publication proof and an expanded","Rust L1 corpus for directive-heavy SDL, schema extensions, legacy aliases, and","invalid duplicate-directive coverage.","The next pulls are:","1. Implement the JS/Rust parity sentinel command from design packet"," [0013-rust-ir-parity-sentinel](./design/0013-rust-ir-parity-sentinel/rust-ir-parity-sentinel.md).","2. Land the `js-table-vs-rust-table.v0` projection/crosswalk before comparing"," legacy JS table IR with Rust L1 bytes.","3. Pull the domain-empty core boundary card into enforcement work so product"," and database behavior stays outside generic Wesley.","4. Continue the IR contract fixture lane for stable invalid-SDL diagnostics,"," including codes and spans where available.","5. Keep `wesley-postgres` visible as the database extraction home and avoid"," reshaping sibling work from Wesley release branches.","Echo and jedit do not need more Wesley feature gravity for their current work.","Wesley should coordinate on compatibility only when a concrete artifact, hash,","or generated-surface change requires it.","docs/README.md",[735],{"_627":628,"_629":217,"_386":736,"_632":57},[737,634,207,738,207,739,740,207,741,207,742,743,744,745,746,747,748,749,750,751,752,753,754,755,207,756,207,757,758,759,760,207,761,207,762,207,763,207,764,207,765,766,767,207,768,769,207,770,771,772,773,207,774,775,776,207,777,778,779,207,780,207,781,207,782,783,784,785,786,787,788,789,790,791,792,207,793,207,788,794,795,796,797,207,798,207,799,800,801,802,803,207,804,207,805,806,807,207,808,207,809,810,811,812,813,814,815,816],"# Wesley Documentation","This is the calm front door for Wesley's docs.","Use it when you need to orient on the repo quickly without reverse-engineering","which signpost is supposed to answer which question.","## Signposts","| Surface | Role |","| --- | --- |","| [README.md](../README.md) | Product-facing front door: what Wesley is, what is real today, and where to start. |","| [ENTRYPOINTS.md](./ENTRYPOINTS.md) | Short answer for which Wesley to run or edit: Rust kernel, native CLI, xtask, or legacy Node tooling. |","| [LEGACY_NODE_MIGRATION.md](./LEGACY_NODE_MIGRATION.md) | Deletion map for the historical Node CLI, packages, generators, hosts, and evidence tooling. |","| [WESLEY_GLOSSARY.md](./WESLEY_GLOSSARY.md) | Fast noun map for the Wesley base platform, modules, and project workspace. |","| [Wesley North Star](./NORTHSTAR.md) | Ultimate doctrine for bounded, lawful autonomy through GraphQL-declared runtime optics. |","| [SDL, Shape, And Law](./SDL.md) | Why GraphQL SDL is Wesley's contract substrate and where domain law interpretation belongs. |","| [BEARING](./BEARING.md) | Current direction, what is already real in the repo, and the tensions that still matter. |","| [Extending Wesley](./guides/extending.md) | How to add Rust compiler behavior, native CLI commands, emitter projections, or external modules. |","| [VISION](./VISION.md) | Bounded executive synthesis grounded in repo-visible truth. |","| [Design Packets](./design/README.md) | Active design packets and doctrinal boundary notes. |","| [METHOD Process](./method/process.md) | How cycles run, close, and reconcile in this repo. |","| [METHOD Release](./method/release.md) | How releases are shaped, verified, and documented. |","## Current Center Of Gravity","The most recent Continuum cycle packet is","[Continuum Contract Compiler](./design/0003-continuum-contract-compiler/continuum-contract-compiler.md).","It closed as a `partial` landing in","[its retro packet](./method/retro/0003-continuum-contract-compiler/continuum-contract-compiler.md).","The v0.0.5 clean-house packet is shipped release context:","- [Product Leftover Cleanup](./design/0012-product-leftover-cleanup/product-leftover-cleanup.md)","The active release center is now v0.0.6 Rust IR parity:","- [Rust IR Parity Sentinel](./design/0013-rust-ir-parity-sentinel/rust-ir-parity-sentinel.md)","The old Continuum-heavy `v0.1.0/` lane has been retired to","[graveyard/v0.1.0](./method/graveyard/v0.1.0/README.md). Treat those notes as","historical extraction context, not as active Wesley release commitments.","The repo already has the important generic building blocks around that","direction:","- a module-driven `wesley compile` surface where targets come from loaded"," external modules","- a real current-state witness path via"," the Continuum-owned Wesley module that lives outside this repository","The former repo-local `compile-ttd` and `bundle-echo` commands were retired","from generic Wesley during the domain-empty extraction. Recreate those surfaces","only as Continuum-owned module commands or external packages.","It also now has a more explicit METHOD closeout surface under","`docs/method/retro/`, `docs/method/graveyard/`, `docs/method/releases/`, and","`docs/releases/`.","## Start Paths","### Product Orientation","- [README.md](../README.md)","- [ENTRYPOINTS.md](./ENTRYPOINTS.md)","- [LEGACY_NODE_MIGRATION.md](./LEGACY_NODE_MIGRATION.md)","- [WESLEY_GLOSSARY.md](./WESLEY_GLOSSARY.md)","- [Wesley North Star](./NORTHSTAR.md)","- [SDL, Shape, And Law](./SDL.md)","- [BEARING](./BEARING.md)","- [Design Packets](./design/README.md)","- [Wesley Core Versus Toolchain](./architecture/wesley-core-vs-toolchain.md)","- [Extending Wesley](./guides/extending.md)","- [Module Contract](./design/wesley-module-contract.md)","### Continuum Orientation","- [Wesley Role In Continuum](./architecture/continuum-wesley-role.md)","- [Continuum Minimum Shared Contract Surface](./architecture/continuum-minimum-shared-contract-surface.md)","- [Continuum Contract Compiler](./design/0003-continuum-contract-compiler/continuum-contract-compiler.md)","- [0003 Retro](./method/retro/0003-continuum-contract-compiler/continuum-contract-compiler.md)","### Workflow Orientation","- [METHOD Process](./method/process.md)","- [METHOD Guide](./method/guide.md)","- [Backlog](./method/backlog/README.md)","- [Retro Packets](./method/retro/README.md)","- [METHOD Release](./method/release.md)","## Stable Reference Surfaces","- [Invariants](./invariants/README.md)","- [Legends](./method/legends/README.md)","- [Directive Truth Table](./DIRECTIVES.md)","## Current Honesty Rules","- The root `README.md` is intentionally product-facing, not the full METHOD"," doctrine front door.","- Active execution lives in the filesystem queue, with `docs/BEARING.md` as"," the current direction surface and `docs/design/README.md` as the design"," packet index.","- If docs contradict runtime behavior, the docs must change.","- Retros and witnesses are the closeout surface; chat and PR commentary are"," not enough on their own.",[818,819,820,821],{"_604":45,"_45":827},{"_604":823,"_159":733,"_627":825,"_629":826},{"_604":823,"_159":621,"_627":824,"_629":325},{"_604":45,"_45":822},"\n* I verified the repository is currently clean (no uncommitted changes), so there was nothing new to commit and no new PR to create from this run. This keeps us compliant with the “no empty/update-less PR action” rule. \n\n**Testing**\n* ✅ `git status --short`\n* ✅ `git log -n 5 --oneline`\n* ✅ `sed -n '1,120p' docs/README.md`\n* ✅ `sed -n '1,140p' docs/BEARING.md | sed -n '1,40p'`","repo_file_citation",13,32,43,"### Summary\n* I reviewed the trigger and current branch state, and I agree the remaining front-door drift is resolved by commit `9789f8e` (`docs(readme): align current release center`). The docs front door now marks v0.0.5 as shipped context and v0.0.6 Rust IR parity (`0013`) as the active release center, matching BEARING’s active gravity. ",{"_90":320,"_41":82,"_94":320,"_830":831,"_832":833,"_834":835,"_130":-5,"_117":836},[81],"input_items",[854,855,856,857,858,859,860,861,862,863,864,865,866,867,868,869],"external_post_config",{"_837":838,"_260":194,"_839":300,"_271":-5,"_840":254,"_841":-5,"_842":843,"_844":845,"_846":-5,"_847":-5,"_848":849,"_850":15,"_851":57,"_852":52,"_853":15},"user_model_slug","slug",1779442484.798703,"installation_id",89912914,"pr_number","repo_id","review_trigger","comment_id",4517482978,"comment_type","issue","pr_write_guard_token","pending_pr_reaction_id","pending_comment_reaction_id",360571445,"comment_if_no_findings","comment_on_error","share_url","is_parallel_review",{"_90":391,"_94":320,"_386":894},{"_307":308,"_309":310,"_891":314,"_892":127,"_316":-5,"_90":893},{"_90":870,"_309":890,"_159":-5,"_872":-5,"_874":-5},{"_90":870,"_309":889,"_159":-5,"_872":-5,"_874":-5},{"_90":870,"_309":888,"_159":-5,"_872":-5,"_874":-5},{"_90":870,"_309":887,"_159":621,"_872":873,"_874":-5},{"_90":870,"_309":886,"_159":-5,"_872":-5,"_874":-5},{"_90":870,"_309":885,"_159":-5,"_872":-5,"_874":-5},{"_90":870,"_309":883,"_159":884,"_872":873,"_874":-5},{"_90":870,"_309":881,"_159":882,"_872":873,"_874":-5},{"_90":870,"_309":880,"_159":621,"_872":873,"_874":-5},{"_90":870,"_309":879,"_159":-5,"_872":-5,"_874":-5},{"_90":870,"_309":878,"_159":-5,"_872":-5,"_874":-5},{"_90":870,"_309":877,"_159":-5,"_872":-5,"_874":-5},{"_90":870,"_309":876,"_159":-5,"_872":-5,"_874":-5},{"_90":870,"_309":871,"_159":621,"_872":873,"_874":875},"pull_request_comment","**_{_{![P2 Badge](https://img.shields.io/badge/P2-yellow?style=flat)}} Update docs front door for v0.0.6 release center**\n\nThis change declares `v0.0.6` as the active gravity in BEARING, but `docs/README.md` still says the active release center is `v0.0.5` (line 33 in that file), so the two top-level navigation docs now contradict each other about what is current. That inconsistency was introduced here and will misroute readers who start from the docs front door; please update `docs/README.md` in the same change to mark `v0.0.5` as shipped/history and point active work to the `0013` parity packet.\n\nUseful? React with 👍 / 👎.","side","RIGHT","line",17,"\n### 💡 Codex Review\n\nHere are some automated review suggestions for this pull request.\n\n**Reviewed commit:** `0ac0e6450f`\n \n\n

ℹ️ About Codex in GitHub

","## Self-Code Review Findings\n\n@codex please confirm before merge. Review basis: clean local worktree, `git fetch origin --prune`, then `git diff origin/main...HEAD`.\n\n| Severity | File / line | Type | Evidence | Recommended mitigation prompt |\n| --- | --- | --- | --- | --- |\n| Medium | `docs/README.md:33` | Documentation drift / front-door inconsistency | This branch resets `docs/BEARING.md` and `docs/method/backlog/asap/README.md` to v0.0.6 Rust IR parity work, but the docs front door still says “The active release center is now the v0.0.5 clean-house packet” and links only `0012-product-leftover-cleanup`. Because `docs/README.md` is an indexed public/front-door doc, this leaves readers with two contradictory active centers. | `Update docs/README.md Current Center Of Gravity so it states that v0.0.5 clean-house is shipped/historical evidence and v0.0.6 centers on Rust IR parity. Link both the shipped 0012 cleanup packet as background and the active 0013 parity sentinel packet as the current release packet. Run docs-check/preflight after the edit.` |\n\nIssue count: Medium 1.","### Summary\n* Added a concise doc comment to `canonical_core_directive_name` clarifying alias-to-canonical mapping scope, borrowed return semantics, and passthrough behavior for non-core/custom directives, with concrete examples. [crates/wesley-core/src/adapters/apollo.rsL961-L970](https://github.com/flyingrobots/wesley/blob/0ac0e6450fc06665d0d46a617b897e3efe8fcf62/crates/wesley-core/src/adapters/apollo.rs#L961-L970)\n* Committed the change on the current branch as `e887bf8` with message: `docs(ir): document core directive alias canonicalization`. [crates/wesley-core/src/adapters/apollo.rsL961-L970](https://github.com/flyingrobots/wesley/blob/0ac0e6450fc06665d0d46a617b897e3efe8fcf62/crates/wesley-core/src/adapters/apollo.rs#L961-L970)\n\n**Testing**\n* ✅ `cargo fmt --check`\n* ✅ `cargo test -p wesley-core --test lowering_validation`\n* ✅ `pnpm run preflight` (passes; shows non-blocking engine warning for local Node v20 vs wanted >=22)\n\n [View task →](https://chatgpt.com/s/cd_6a100e38a6788191a0c5e3d80a78fcb3)","## Self-Code Review Resolution\n\n@codex follow-up commit `0ac0e645` resolves the four findings from comment `4516291171`.\n\n| Original severity | Resolution |\n| --- | --- |\n| High | Narrowed duplicate directive rejection to canonical core Wesley directives only. Repeated custom directives are now preserved as ordered arrays, with regression coverage for repeatable `@tag`. |\n| Medium | Updated design packet `0013` to require a named `js-table-vs-rust-table.v0` projection/crosswalk before comparing legacy JS table IR with Rust L1 bytes. |\n| Medium | Removed transient local `~/git/wesley-postgres` worktree status from committed BEARING text and kept only stable sibling-repo coordination doctrine. |\n| Low | Updated BEARING so completed publication-evidence and fixture-expansion slices are current evidence, while the next pulls are the remaining sentinel/projection/domain-boundary work. |\n\nValidation after the fix:\n\n- `cargo fmt --check`\n- `cargo test -p wesley-core --test lowering_validation`\n- `cargo clippy -p wesley-core --all-targets -- -D warnings`\n- `cargo xtask docs-check`\n- `git diff --check`\n- repeatable custom directive CLI reproduction now succeeds\n- `pnpm run preflight`\n- push hook repository preflight","**_{_{![P3 Badge](https://img.shields.io/badge/P3-lightgrey?style=flat)}} Remove machine-local worktree state from project bearing**\n\nThis commits a local filesystem path and transient sibling-repo branch/dirty-state snapshot into `BEARING.md`, which will become stale immediately for other contributors and CI contexts and does not provide durable repository direction. Keeping ephemeral workstation state in the canonical bearing doc harms reproducibility of planning context and should be moved to PR/session notes instead.\n\nUseful? React with 👍 / 👎.","**_{_{![P2 Badge](https://img.shields.io/badge/P2-yellow?style=flat)}} Define an explicit JS↔Rust IR projection before byte compare**\n\nThe comparator contract says to compare legacy JS semantic IR bytes directly against Rust semantic IR bytes, but it does not define any crosswalk/projection despite the referenced JS anchor emitting a different IR shape (`tables/enums/scalars/relationships` in `packages/wesley-runtime-node/src/GraphQLAdapter.mjs`) than Rust L1 fixtures (`types`). Without a normalization/projection contract here, a parity sentinel implementation cannot distinguish expected structural differences from real regressions, so the design is currently non-executable as written.\n\nUseful? React with 👍 / 👎.","docs/design/0013-rust-ir-parity-sentinel/rust-ir-parity-sentinel.md","**_{_{![P1 Badge](https://img.shields.io/badge/P1-orange?style=flat)}} Restrict duplicate rejection to canonical Wesley aliases**\n\nThe duplicate guard now checks `canonical_name` for every directive, so any repeatable non-Wesley directive (for example `@tag` declared as `repeatable`) is rejected even though the SDL is valid. I reproduced this by lowering a schema with `@tag(name: \"a\") @tag(name: \"b\")`, which now fails with `Lowering error: Duplicate directive '@tag' in directive`; this is a compatibility regression introduced by this change because the new logic conflates alias-collision protection with general repeatable-directive handling.\n\nUseful? React with 👍 / 👎.","crates/wesley-core/src/adapters/apollo.rs","\n### 💡 Codex Review\n\nHere are some automated review suggestions for this pull request.\n\n**Reviewed commit:** `483439d47f`\n \n\n

ℹ️ About Codex in GitHub

","**Actionable comments posted: 1**\n\n

🧹 Nitpick comments (1)

\n\n
\n
crates/wesley-core/src/adapters/apollo.rs (1)
\n\n`960-972`: _⚡ Quick win_\n\n**Consider adding a doc comment to explain the canonicalization contract.**\n\nThe function correctly implements the alias-to-canonical mapping, but a doc comment would clarify the purpose and supported aliases for future maintainers.\n\n\n\n
\n
📝 Suggested doc comment
\n\n```diff\n+/// Maps legacy Wesley directive aliases to their canonical internal names.\n+///\n+/// This normalization ensures that directives declared with different aliases\n+/// (e.g., `@table`, `@wesley_table`) are recognized as the same directive\n+/// and stored under a single canonical key (`wes_table`).\n+///\n+/// Returns the canonical name if a mapping exists, otherwise returns the input unchanged.\n fn canonical_directive_name(name: &str) -> &str {\n match name {\n```\n
\n\n
\n
🤖 Prompt for AI Agents
\n\n```\nVerify each finding against current code. Fix only still-valid issues, skip the\nrest with a brief reason, keep changes minimal, and validate.\n\nIn `@crates/wesley-core/src/adapters/apollo.rs` around lines 960 - 972, Add a\nconcise doc comment for the function canonical_directive_name describing its\ncontract: that it maps known directive aliases (list the aliases and their\ncanonical names like \"wesley_table\"/\"table\" -> \"wes_table\",\n\"wesley_pk\"/\"pk\"/\"primaryKey\" -> \"wes_pk\", etc.), that it returns a borrowed\n&str of the canonical name (does not allocate), and that unknown names are\nreturned unchanged; include purpose and examples of expected inputs/outputs so\nfuture maintainers understand supported aliases and return semantics.\n```\n\n
\n\n
\n\n

\n\n

🤖 Prompt for all review comments with AI agents

\n\n

🪄 Autofix (Beta)

\n\nFix all unresolved CodeRabbit comments on this PR:\n\n- [ ] Push a commit to this branch (recommended)\n- [ ] Create a new PR with the fixes\n\n

\n\n---\n\n

ℹ️ Review info

\n\n

⚙️ Run configuration

\n\n**Configuration used**: Path: .coderabbit.yaml\n\n**Review profile**: CHILL\n\n**Plan**: Pro\n\n**Run ID**: `220b721d-b1df-403f-bdc5-7cd03e5c7394`\n\n

\n\n

📥 Commits

\n\nReviewing files that changed from the base of the PR and between fa42c71832520b70e55447e865e0425e467db2a5 and 483439d47f3754d00f9c836dfb9ab8118f6c3ecb.\n\n

\n\n

📒 Files selected for processing (20)

\n\n

💤 Files with no reviewable changes (1)

\n\n* docs/method/backlog/asap/SOURCE_wesley-core-rs-parity-sentinel.md\n\n

\n\n

\n\n","_⚠️ Potential issue_ | _🟡 Minor_ | _⚡ Quick win_\n\n**Avoid machine-local path/state in shared roadmap docs.**\n\nLine 77 and Line 78 encode host-specific state (`~/git/...`, local `main` ahead of `origin/main`) that will quickly go stale and cannot be validated by other contributors. Prefer repository-relative/remote references plus a dated note in release evidence docs.\n\n

🤖 Prompt for AI Agents

\n\n\n\n\n\n✅ Addressed in commit 0ac0e64","## Self-Code Review Findings\n\n@codex please confirm whether you agree with these findings before merge. Review basis: local clean worktree, `git fetch origin --prune`, then `git diff origin/main...HEAD`.\n\n| Severity | File / line | Type | Evidence | Recommended mitigation prompt |\n| --- | --- | --- | --- | --- |\n| High | `crates/wesley-core/src/adapters/apollo.rs:507` | Logical regression / unintended compatibility break | The new duplicate check runs for every directive name after `canonical_directive_name`, not only for Wesley aliases. Valid GraphQL SDL with a repeatable non-Wesley directive now fails: `directive @tag(name: String!) repeatable on FIELD_DEFINITION` plus `@tag(name: \"a\") @tag(name: \"b\")` exits with `Lowering error: Duplicate directive '@tag' in directive`. | `Narrow Rust duplicate-directive rejection so it only rejects canonical collisions for the supported core Wesley directive aliases, or implement explicit repeatable-directive support in L1. Add a regression test proving non-Wesley repeatable directives are either preserved correctly or rejected by a documented unsupported-feature diagnostic rather than by the generic duplicate alias path.` |\n| Medium | `docs/design/0013-rust-ir-parity-sentinel/rust-ir-parity-sentinel.md:49` | Design contract gap | The packet says the sentinel records and compares legacy JS semantic IR bytes against Rust semantic IR bytes, but the named JS anchor emits a table IR shape with `tables`, `enums`, `scalars`, and `relationships` (`packages/wesley-runtime-node/src/GraphQLAdapter.mjs:148`), while Rust L1 fixtures emit `types`. The packet never defines a projection or equivalence layer, so the next implementation slice has no coherent comparator contract. | `Revise the parity sentinel packet to define the comparison projection explicitly: either compare only a documented common semantic subset, introduce a JS-to-L1/Rust-to-legacy normalization adapter, or exclude non-overlapping fixtures until a real crosswalk exists. Add playback questions that force the implementation to prove the chosen projection.` |\n| Medium | `docs/BEARING.md:77` | Documentation reproducibility / transient local state | `BEARING.md` commits a machine-local path and ephemeral sibling-repo worktree state: `~/git/wesley-postgres` has local `main` ahead of `origin/main` and uncommitted bootstrap work. That is useful session evidence, but not stable project direction and will become stale immediately. | `Replace the local path/worktree-status sentence with stable repository-level doctrine: wesley-postgres is the database extraction authority and Wesley should coordinate before changing database-shaped compatibility seams. Move the exact local inspection result to PR notes or session memory instead of committed BEARING text.` |\n| Low | `docs/BEARING.md:108` | Planning drift / stale next-action list | The `Next Target` list still tells the next agent to keep v0.0.5 publication evidence complete and expand the L1 fixture corpus, but this branch already does both. After merge, BEARING should point to the remaining next moves, not replay completed work. | `Update the BEARING next-target list so completed slices are recorded as current evidence, and the remaining active pulls start with implementing the parity sentinel command, defining the IR projection/crosswalk, and pulling domain-empty core boundary enforcement.` |\n\nIssue count: High 1, Medium 2, Low 1.","\n\n# 🔍 The Case of Pull Request #513\n\n## Plain-English Readout\n\n- **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.\n- **Watson (independent verification)**: Watson found verification concerns. Most important concern: Low migration risk claimed but schema incomplete.\n- **Moriarty (trend forecast)**: Moriarty sees progress as stalled right now, so forecast confidence is limited.\n\n## Suggested next actions\n\n1. Tighten citations so the report points to exact lines instead of whole files or coarse references.\n2. Resolve Watson’s verification concerns before trusting the Holmes verdict as final.\n3. Treat the readiness forecast as stalled until new evidence or real progress moves the trend again.\n4. Add or strengthen tests for the schema elements and operations HOLMES flagged as weakly proven.\n\n

📚 Glossary (what the Holmes terms mean)

\n\n---\n\n

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

\n\n---\n\n

🩺 Dr. WATSON full report (click to expand)

\n\n---\n\n

🔮 Professor MORIARTY full report (click to expand)

\n\n---\n\n_Machine-readable reports:_ holmes-report.json · watson-report.json · moriarty-report.json (see workflow artifacts).\n\n---\n\n*Filed at 221B Repository Street*\n","\n\n\n> [!WARNING]\n> ## Rate limit exceeded\n> \n> `@flyingrobots` has exceeded the limit for the number of commits that can be reviewed per hour. Please wait **13 minutes and 5 seconds** before requesting another review.\n> \n> You’ve run out of usage credits. Purchase more in the [billing tab](https://app.coderabbit.ai/settings/subscription?tab=usage&tenantId=4252c417-78a1-49cd-a607-68d1e6bdacc4).\n> \n>

\n>

⌛ How to resolve this issue?

\n> \n> \n>

\n>

🚦 How do rate limits work?

\n> \n>

\n>

ℹ️ Review info

\n> \n>

\n>

⚙️ Run configuration

\n> \n> **Configuration used**: Path: .coderabbit.yaml\n> \n> **Review profile**: CHILL\n> \n> **Plan**: Pro\n> \n> **Run ID**: `9045b028-a14f-41f7-81fa-f61c7b6e5894`\n> \n>

\n> \n>

\n>

📥 Commits

\n> \n> Reviewing files that changed from the base of the PR and between 483439d47f3754d00f9c836dfb9ab8118f6c3ecb and 0ac0e6450fc06665d0d46a617b897e3efe8fcf62.\n> \n>

\n> \n>

\n>

📒 Files selected for processing (6)

\n> \n>

\n\n\n\n\n\n

📝 Walkthrough

\n\n\n\n\n

🚥 Pre-merge checks | ✅ 3 | ❌ 2

✅ Passed checks (3 passed)

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

\n\n\n\n\n

✨ Finishing Touches

\n\n

🧪 Generate unit tests (beta)

\n\n- [ ] Create PR with unit tests\n- [ ] Commit unit tests in branch `codex/v0.0.6-bearing`\n\n

\n\n

❤️ Share

\n\n\n_{Comment `@coderabbitai help` to get the list of available commands and usage tips.}\n\n\n\n\n\n\n\n","base_ref","head_ref","pull_request_info",[895],{"_604":45,"_45":896},"## Self-Code Review Resolution\n\n@codex follow-up commit `9789f8e3` resolves the remaining `docs/README.md` front-door drift from comment `4517010571`.\n\n| Original severity | Resolution |\n| --- | --- |\n| Medium | `docs/README.md` now marks v0.0.5 clean-house / packet `0012` as shipped release context and names v0.0.6 Rust IR parity / packet `0013` as the active release center. |\n\nValidation after the fix:\n\n- `cargo xtask docs-check`\n- `git diff --check`\n- `pnpm run preflight`\n- push hook repository preflight",[1068,1069],[],{"_609":610,"_45":611,"_612":613},{"_583":1059},{"_331":1058},{"_331":932},{"_299":300,"_291":301,"_302":303,"_304":15,"_305":57,"_306":15,"_307":308,"_309":310,"_311":264,"_312":125,"_313":314,"_315":127,"_316":317,"_318":-5,"_319":-5,"_320":931,"_322":323,"_324":325,"_326":327,"_328":329},{"_41":121,"_191":192,"_193":194,"_195":15,"_196":197,"_198":199,"_200":920,"_202":-5,"_203":-5,"_204":921,"_206":207,"_208":207,"_209":922,"_211":923,"_213":924,"_215":-5,"_216":217,"_218":219,"_220":221,"_222":925,"_53":-5,"_117":224,"_225":926,"_227":927,"_229":230,"_231":15,"_232":15},{"_131":913},[907,908,909,910,911,912],{"_146":169,"_148":163,"_150":164,"_152":161,"_154":170,"_156":157,"_158":31,"_159":-5},{"_146":168,"_148":163,"_150":164,"_152":161,"_154":165,"_156":157,"_158":31,"_159":-5},{"_146":166,"_148":163,"_150":164,"_152":161,"_154":167,"_156":157,"_158":31,"_159":-5},{"_146":162,"_148":163,"_150":164,"_152":161,"_154":165,"_156":157,"_158":31,"_159":-5},{"_146":160,"_148":149,"_150":151,"_152":161,"_154":155,"_156":157,"_158":31,"_159":-5},{"_146":147,"_148":149,"_150":151,"_152":153,"_154":155,"_156":157,"_158":31,"_159":-5},[914,915,916],{"_175":919,"_177":188},{"_175":918,"_177":184},{"_175":917,"_177":178},{"_179":180,"_90":181,"_117":182},{"_179":185,"_90":181,"_117":186},{"_179":189,"_90":181,"_117":190},{"_293":294,"_295":-5,"_296":-5,"_297":-5,"_298":-5},[254],{"_254":928},{"_236":237,"_238":239,"_240":241,"_242":243,"_244":245,"_246":247,"_248":249,"_250":251,"_252":253},{},[],{"_235":57},{"_233":57,"_234":207},{"_41":256,"_179":257,"_258":929,"_260":194,"_261":262,"_263":264,"_265":266,"_267":268,"_269":270,"_271":62,"_272":15,"_273":-5,"_274":-5,"_275":-5,"_276":-5,"_277":-5,"_278":-5,"_158":279,"_280":-5,"_53":930},{"_285":286,"_41":287,"_90":288,"_289":290,"_291":292},{"_282":15,"_283":15,"_284":15},{"_285":286,"_179":286,"_330":-5,"_289":290,"_41":287},[933,934,935,936,937,938,939,940,941,942,943,944,945,946,947,948,949,950,951,952,953,954,955,956,957,958,959,960],{"_152":562,"_362":1054},{"_152":377,"_362":1051},{"_152":552,"_362":1048},{"_152":381,"_362":1043},{"_152":381,"_362":1038},{"_152":381,"_362":1034},{"_152":395,"_362":1029},{"_152":395,"_362":1025},{"_152":381,"_362":1021},{"_152":381,"_362":1019},{"_152":381,"_362":1017},{"_152":395,"_362":1013},{"_152":395,"_362":1009},{"_152":381,"_362":1005},{"_152":381,"_362":1003},{"_152":395,"_362":999},{"_152":381,"_362":997},{"_152":395,"_362":993},{"_152":381,"_362":989},{"_152":381,"_362":987},{"_152":395,"_362":982},{"_152":381,"_362":980},{"_152":395,"_362":976},{"_152":381,"_362":972},{"_152":395,"_362":970},{"_152":381,"_362":966},{"_152":377,"_362":964},{"_152":361,"_362":961},{"_364":365,"_85":962},{"_367":368,"_369":370,"_101":-5,"_41":371,"_372":963,"_374":375,"_376":111},[],{"_376":965,"_364":365},{"_90":380},{"_383":967,"_364":365,"_385":371},{"_386":968,"_388":-5,"_41":-5,"_389":390,"_94":91,"_90":391},[969],{"_45":393,"_90":394},{"_383":971,"_364":365,"_385":371},{"_41":398,"_389":390,"_45":393,"_90":399},{"_383":973,"_364":365,"_385":371},{"_386":-5,"_402":403,"_41":-5,"_404":974,"_90":406},[975],{"_45":408,"_90":409},{"_383":977,"_364":365,"_385":371},{"_386":978,"_41":413,"_404":979,"_90":406},[],[408],{"_383":981,"_364":365,"_385":371},{"_417":418,"_419":420,"_90":421},{"_383":983,"_364":365,"_385":371},{"_424":425,"_426":427,"_428":984,"_430":431,"_369":31,"_432":31,"_41":418,"_433":434,"_435":436,"_376":111,"_90":437},[985,986],{"_426":444,"_179":445,"_159":446,"_90":443},{"_426":440,"_179":441,"_159":442,"_90":443},{"_383":988,"_364":365,"_385":371},{"_449":450,"_417":418,"_41":-5,"_179":451,"_452":-5,"_90":453},{"_383":990,"_364":365,"_385":371},{"_386":-5,"_402":456,"_41":-5,"_404":991,"_90":406},[992],{"_45":459,"_90":409},{"_383":994,"_364":365,"_385":371},{"_386":995,"_41":463,"_404":996,"_90":406},[],[459],{"_383":998,"_364":365,"_385":371},{"_417":467,"_419":468,"_90":421},{"_383":1000,"_364":365,"_385":371},{"_424":471,"_426":472,"_428":1001,"_430":431,"_369":31,"_432":31,"_41":467,"_433":474,"_435":436,"_376":111,"_90":437},[1002],{"_426":476,"_90":477},{"_383":1004,"_364":365,"_385":371},{"_449":480,"_417":467,"_41":-5,"_179":451,"_452":-5,"_90":453},{"_383":1006,"_364":365,"_385":371},{"_386":-5,"_402":483,"_41":-5,"_404":1007,"_90":406},[1008],{"_45":486,"_90":409},{"_383":1010,"_364":365,"_385":371},{"_386":1011,"_41":490,"_404":1012,"_90":406},[],[486],{"_383":1014,"_364":365,"_385":371},{"_424":494,"_426":495,"_428":1015,"_430":431,"_369":497,"_432":31,"_41":498,"_433":499,"_435":436,"_376":111,"_90":437},[1016],{"_426":501,"_159":502,"_503":504,"_90":505},{"_383":1018,"_364":365,"_385":371},{"_417":498,"_419":508,"_90":421},{"_383":1020,"_364":365,"_385":371},{"_449":511,"_417":498,"_41":-5,"_179":451,"_452":-5,"_90":453},{"_383":1022,"_364":365,"_385":371},{"_386":-5,"_402":514,"_41":-5,"_404":1023,"_90":406},[1024],{"_45":517,"_90":409},{"_383":1026,"_364":365,"_385":371},{"_386":1027,"_41":521,"_404":1028,"_90":406},[],[517],{"_383":1030,"_364":365,"_385":371},{"_386":1031,"_41":526,"_90":527},[1032],{"_45":529,"_530":1033,"_90":45},[],{"_383":1035,"_364":365,"_385":371},{"_386":1036,"_388":-5,"_41":-5,"_389":-5,"_94":320,"_90":391},[1037],{"_45":529,"_90":536},{"_383":1039,"_364":365,"_385":371},{"_386":1040,"_388":-5,"_41":-5,"_389":-5,"_94":320,"_90":391},[1041,1042],{"_45":543,"_90":536},{"_45":542,"_90":536},{"_383":1044,"_364":365,"_385":371},{"_386":1045,"_388":-5,"_41":-5,"_389":-5,"_94":547,"_90":391},[1046,1047],{"_45":551,"_90":536},{"_45":550,"_90":536},{"_364":365,"_85":1049},{"_101":-5,"_41":371,"_372":1050,"_374":375,"_376":556},[],{"_376":1052,"_364":365},{"_559":1053,"_90":561},[],{"_564":1055},{"_566":-5,"_567":-5,"_568":569,"_570":375,"_430":431,"_571":15,"_572":-5,"_573":-5,"_41":365,"_574":575,"_179":-5,"_159":576,"_577":207,"_435":578,"_376":1056,"_75":1057,"_581":375},{"_90":380},[],[],[1060],{"_41":586,"_587":1061,"_589":590,"_591":590,"_386":1062,"_376":593,"_388":-5,"_594":31,"_595":1063,"_597":598,"_599":-5},{"_94":320,"_179":-5,"_595":1067},{"_604":45,"_605":1066},{"_600":1064},{"_602":1065},[],[607],{},{"_90":391,"_94":91,"_386":1079},{"_90":616,"_617":1070},[1071,1072],{"_159":733,"_622":-5,"_623":1076,"_625":-5},{"_159":621,"_622":-5,"_623":1073,"_625":-5},[1074],{"_627":628,"_629":630,"_386":1075,"_632":57},[633,634,207,635,636,207,637,638,639,640,641,642,643,207,644,207,645,207,646,647,648,207,649,650,651,652,207,653,207,654,655,656,657,658,659,660,661,662,207,663,207,664,665,666,667,668,669,670,207,671,207,672,673,207,674,675,676,677,678,679,207,680,207,681,682,683,684,685,686,687,207,688,207,689,690,207,691,692,693,694,207,695,207,696,697,698,699,700,701,702,703,704,705,706,707,708,709,710,711,712,207,713,207,714,715,207,716,717,718,207,719,207,720,721,722,723,724,725,726,727,728,729,207,730,731,732],[1077],{"_627":628,"_629":217,"_386":1078,"_632":57},[737,634,207,738,207,739,740,207,741,207,742,743,744,745,746,747,748,749,750,751,752,753,754,755,207,756,207,757,758,759,760,207,761,207,762,207,763,207,764,207,765,766,767,207,768,769,207,770,771,772,773,207,774,775,776,207,777,778,779,207,780,207,781,207,782,783,784,785,786,787,788,789,790,791,792,207,793,207,788,794,795,796,797,207,798,207,799,800,801,802,803,207,804,207,805,806,807,207,808,207,809,810,811,812,813,814,815,816],[1080,1081,1082,1083],{"_604":45,"_45":827},{"_604":823,"_159":733,"_627":825,"_629":826},{"_604":823,"_159":621,"_627":824,"_629":325},{"_604":45,"_45":822},[1086,1087,1088,1089,1090,1091,1092,1093,1094,1095,1096,1097,1098,1099,1100,1101],{"_837":838,"_260":194,"_839":300,"_271":-5,"_840":254,"_841":-5,"_842":843,"_844":845,"_846":-5,"_847":-5,"_848":849,"_850":15,"_851":57,"_852":52,"_853":15},{"_90":391,"_94":320,"_386":1102},{"_307":308,"_309":310,"_891":314,"_892":127,"_316":-5,"_90":893},{"_90":870,"_309":890,"_159":-5,"_872":-5,"_874":-5},{"_90":870,"_309":889,"_159":-5,"_872":-5,"_874":-5},{"_90":870,"_309":888,"_159":-5,"_872":-5,"_874":-5},{"_90":870,"_309":887,"_159":621,"_872":873,"_874":-5},{"_90":870,"_309":886,"_159":-5,"_872":-5,"_874":-5},{"_90":870,"_309":885,"_159":-5,"_872":-5,"_874":-5},{"_90":870,"_309":883,"_159":884,"_872":873,"_874":-5},{"_90":870,"_309":881,"_159":882,"_872":873,"_874":-5},{"_90":870,"_309":880,"_159":621,"_872":873,"_874":-5},{"_90":870,"_309":879,"_159":-5,"_872":-5,"_874":-5},{"_90":870,"_309":878,"_159":-5,"_872":-5,"_874":-5},{"_90":870,"_309":877,"_159":-5,"_872":-5,"_874":-5},{"_90":870,"_309":876,"_159":-5,"_872":-5,"_874":-5},{"_90":870,"_309":871,"_159":621,"_872":873,"_874":875},[1103],{"_604":45,"_45":896},"task_e_6a102333d28c832a9148e7117e5cb39e",1779442483.822558,"Github Mention: expand parity fixture coverage","has_generated_title","has_unread_turn","denormalized_metadata",{"_1135":31,"_1136":1137,"_1138":-5,"_1139":-5,"_1130":1140,"_1141":-5,"_1142":-5,"_1143":-5,"_1144":-5},"task_status_display",{"_1123":1124,"_1125":194,"_128":125,"_1126":-5,"_1127":1128},"creator_workspace","external_pull_requests",[1116],{"_41":1117,"_1118":81,"_1119":1120,"_1121":127},"github-1049014142-513","assistant_turn_id","pull_request",{"_299":300,"_291":301,"_302":303,"_304":15,"_305":57,"_306":15,"_307":308,"_309":310,"_311":264,"_312":125,"_313":314,"_315":127,"_316":317,"_318":-5,"_319":-5,"_320":1122,"_322":323,"_324":325,"_326":327,"_328":329},"codex_updated_sha",{"_285":286,"_179":286,"_330":-5,"_289":290,"_41":287},"latest_turn_status_display",{"_1129":81,"_110":111,"_1130":-5,"_92":1131,"_1132":-5,"_1133":-5,"_1134":1128,"_112":-5},"environment_label","fix_task_id","initial_intent","pr","turn_id","diff_stats",[],"image_asset_pointer_citations","issue_counts","intent","num_follow_ups","repo_name_map",{},"last_user_turn_created_at","last_turn_status",{"_1145":-5,"_1146":-5,"_1147":-5},"last_pushed_turn_id","start_branch_name","pushed_branch_name","cached_pull_request_data","files_modified","lines_added","lines_removed","dd",{"_1159":1160,"_1161":1162},"disablePrefetch","shouldPrefetchAccount","shouldPrefetchUser","shouldPrefetchSystemHints","promoteCss","disableSSR","stripModulepreloadImports","statsigGateEvaluationsPromise",["P",1158],"traceId","16513403172402447323","traceTime",1779495915190]