chore(op-canon): drop Member/Membership drift pin after OGAR #113 merged

[AdaWorldAPI]

What

Closes the chain: OGAR #113 (merged) added ("Member", PROJECT_MEMBERSHIP) to OPENPROJECT_ALIASES alongside the existing Membership. The pinned drift test I planted in #56 was deliberately self-flipping (asserting class_id_of("Member") == None) so it'd fail the moment OGAR aligned the alias to the corpus name. That trigger fired; this is the drop.

// before — self-flipping pin (would fail now)
assert_eq!(class_id_of("Member"), None,
    "if this is now Some(_), OGAR aligned the alias — drop this pin");

// after — successor positive assertion (the convergence the pin set up)
assert_eq!(class_id_of("Member"),     Some(PROJECT_MEMBERSHIP));
assert_eq!(class_id_of("Membership"), Some(PROJECT_MEMBERSHIP));

The new test member_and_membership_both_resolve_after_ogar_113 pins that:

• Member resolves (OGAR #113 — canonical, matches the OpenProject corpus + Redmine)
• Membership still resolves (deprecated synonym kept for backcompat)
• Both equal each other → no vocab drift between OP corpus and port

The overlap drift guard (port_pull_agrees_with_the_snapshot) now covers Member too — no silent skip on that name anymore.

Scope

• Lockfile: cargo update -p ogar-vocab → OGAR main post-#113 (991450a). No other dep changes.
• One file: crates/op-canon/src/app.rs — replaces 1 test (the pin) with 1 test (the positive successor); the test count is unchanged.

Build

Toolchain 1.95. cargo test -p op-canon → 19 unit + 5 doctests pass. cargo fmt --check + cargo clippy --all-targets -- -D warnings clean.

Cross-refs

• OGAR #113 — the Member alias add that triggered this drop.
• This repo feat(op-canon): app module — pull OGAR via class (W0 / lance-graph#589 shape) #56 — where the pin was originally planted.
• This repo refactor(op-canon): re-export APP_PREFIX + render_classid from OGAR (one source of truth) #57 — where the re-export refactor consumed OGAR's typed surface.

---

Generated by Claude Code

[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.