canon + feat: E-KEEP-AR-REMOVE-ORM + compile_graph_ruby (the Rails CompiledClass keystone)

[AdaWorldAPI]

Summary

Two commits, one arc — the canon correction and the first concrete brick it names.

1. canon: E-KEEP-AR-REMOVE-ORM — append-only EPIPHANIES.md entry recording an operator correction: the consumer "open-heart operation" keeps ActiveRecord and removes the ORM. A prior session read it backwards as "castrate the hand-rolled Rails ActiveRecord betrayal." Wrong: KEEP the AR pattern (class = record + behavior — literally what OGAR's Class/ClassView is; OGAR = Open Graph Active Record, named after AR in OpenProject); REMOVE the ORM (hand-rolled persistence plumbing — op-db SQL/FromRow, op-api row→DTO); WIRE pure AR on Rails directly onto the OGAR graph, no ORM intermediary. Plus Redmine-as-root (fieldview/erb → classview/askama) and a guard against re-inversion.

2. feat(ogar-from-ruff): compile_graph_ruby — the keystone gap the canon entry names: a Rails-correct sibling of compile_graph_python. Same shape (mint_graph::<P> + per-class facet resolution), but routes through the existing lift_model_graph (Language::Ruby) instead of lift_model_graph_python — pure operator-reuse, no new lift, and project_odoo_fields is correctly never invoked for Rails (it would double-count).

Proves the convergence claim in code: compile_graph_ruby::<OpenProjectPort> on a WorkPackage graph and compile_graph_ruby::<RedminePort> on an Issue graph mint to the same low-u16 concept (0x0102 project_work_item) and different high-u16 render prefixes (0x0001 vs 0x0007) — one canonical concept, two render skins, machine-checked rather than asserted.

Drive-by fix: 3 pre-existing Function{...} literal constructions (emit.rs, mint.rs's account_move fixture, lib.rs) broke against the already-merged ruff#38 (writes/calls fields) because this crate's ruff_spo_triplet dep floats on branch=main. Added ..Default::default() to each — no behavior change, restores compilation.

Test Plan

Standalone probe workspace (path-dep ogar-vocab + ogar-from-ruff, git-dep ruff branch=main) — the OGAR workspace itself can't resolve in-sandbox (ogar-adapter-surrealql's surrealdb-ast git dep 403s), the same pattern prior PRs (#131/#132/#136/#138/#141) used.

• 44/44 tests pass (3 new — compile_graph_ruby_stamps_language_ruby_not_python, openproject_work_package_compiles_to_project_work_item_rail_class, openproject_and_redmine_compile_to_the_same_concept_different_render_skin — + 41 pre-existing, unbroken by the drive-by fix).
• cargo clippy -p ogar-from-ruff --no-deps -D warnings clean at the pinned 1.95.0 toolchain. (ogar-vocab itself has pre-existing, unrelated clippy debt from never being --workspace-gated — same root cause as the surrealdb-ast 403 — out of scope here.)
• cargo doc -p ogar-from-ruff --no-deps — doc-links resolve; the 4 pre-existing warnings are in emit.rs, unrelated to this change.

🤖 Generated with Claude Code

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 76dbc8b2e2

ℹ️ About Codex in GitHub

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

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

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

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

[chatgpt-codex-connector]

Add the required Scope line to this epiphany

The .claude/AGENTS.md instructions for this log require each EPIPHANIES entry to have ## ... plus a **Status:** line, a **Scope:** line, body, and **Cross-ref:**; this new entry goes directly from Status to the correction text. Please add the missing Scope line so the append-only log keeps the documented structure future agents are told to rely on.

Useful? React with 👍 / 👎.