[AdaWorldAPI]

Follow-up for work stranded by a merge into a non-default base.

AdaWorldAPI/ruff#92 ("AdaWorldAPI SPO/transcode layer, rebased onto current
upstream") merged into main-catchup-2026-07-20, not into main. That
branch never landed on main — it currently sits 11 ahead / 890 behind — so
every file #92 added reached main only if some later PR carried it.

What is actually stranded

Almost nothing, which is why this went unnoticed. Of the 131 files #92
added, 130 are present on main today — the seven ruff_*_spo crates,
ruff_spo_triplet, ruff_spo_address, ruff_cpp_codegen,
ruff_python_dto_check, the .claude/knowledge/ method docs, the harvester
examples, the AGENTS.md paragraph, the workspace wiring. All present.

One file is not: .claude/OGAR-POLYGLOT-AST-INTEGRATION.md (193 lines).

Why this is an accident, not a decision

The proof is on main itself. mkdocs.template.yml line 109 reads:

not_in_nav: |
  /rules/*
  /formatter/*
  /OGAR-POLYGLOT-AST-INTEGRATION.md

mkdocs.template.yml is one of the seven files #92 modified, and that
modification did reach main. So main has been carrying a nav-exclusion
rule for a document it does not contain, since 2026-07-20. The manifest edit
landed and the file it names did not — which is exactly the signature of a
file lost to the stranded merge, not one deliberately dropped.

There is also no replacement: main has no other OGAR / polyglot / AST design
doc under .claude/.

What this PR does

Restores the file verbatim from main-catchup-2026-07-20. Nothing edited,
nothing else touched.

It is an RFC — its own header says "Status: RFC / design contract. Not yet
implemented or compile-verified" — so this is a documentation recovery with
no code impact and no CI surface beyond the docs build, which already expects
the file by name.

What this PR does not do

It does not merge main-catchup-2026-07-20. That branch is 890 commits behind
main and its remaining 11 commits are the already-landed SPO layer under
different SHAs; merging it would be a large, pointless conflict resolution for
content main already has. If the branch is not needed for anything else it
can now be deleted.

🤖 Generated with Claude Code

https://claude.ai/code/session_01AGVLyRZNEKKBSfBDJfbY3V

Summary by CodeRabbit

• Documentation
  • Added an RFC describing a shared AST integration contract for Python, C++, C#, and Ruby.
  • Documents normalization through a common model graph, structural transpilation boundaries, and language-specific source generation.
  • Defines graph reconstruction, predicate registration, storage integration, validation gates, diagnostics, and planned C++ extraction/code-generation checks.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Essentials

Run ID: 889c5cad-8a03-4027-b900-c5b469186233

📥 Commits

Reviewing files that changed from the base of the PR and between b4ac142 and fffea6e.

📒 Files selected for processing (1)

• .claude/OGAR-POLYGLOT-AST-INTEGRATION.md

---

📝 Walkthrough

Walkthrough

The RFC defines a ModelGraph contract for Python, C++, C#, and Ruby AST integration. It specifies facets, triples, reassembly, frontend normalization, backend rendering, round-trip checks, Lance indexing, and structural transpilation boundaries.

Changes

Polyglot AST Integration

Layer / File(s)	Summary
ModelGraph and facet contract .claude/OGAR-POLYGLOT-AST-INTEGRATION.md	Defines the Phase-0 IR with Facet, Triple, typed tenants, canonical node layout, and capacity limits.
Frontend normalization and storage boundaries .claude/OGAR-POLYGLOT-AST-INTEGRATION.md	Documents predicate registration, general reassembly, frontend normalization, convergence checks, diagnostics, and Lance indexing constraints.
Backend rendering and implementation path .claude/OGAR-POLYGLOT-AST-INTEGRATION.md	Adds the LangBackend rendering contract, backend plans, source round-trip rules, and the C++ smoke-test path.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Poem

A rabbit reads each line,
The patch grows clear beneath the moon,
Small changes hop in place,
Tests guard the garden path,
Reviews bloom before the dawn.

---

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

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: serverGenReqId_91f50673-979d-49ff-87db-5fb13b382c25)

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.