rfm: a service declaring one operation name twice (v1 silent, v2 census refuses located)

[gunbai-bot]

Stacked on #12277, which carries the claim this row cites (a_repeated_operation_name_refuses_located_RED). Retarget to main once #12277 lands.

Adds gunbc.recurring_failure_mode service_operation_declared_twice, as neat-boar-16 asked. v1 silently accepts two operations with the same name in one service and keeps the later one: a DESIGN §3 meaning fork. The v2 census now refuses it at the second declaration (body_lowering_reason_service_operation_repeated, #12277). Next-rung trigger: v1 refuses the duplicate, or v1 is retired.

Scope changed after the first review. The source repair of the specimen (dag/extdeps/bmc/http.dag declaring GetManager twice) is NOT in this PR any more. still-swift-387's gen-two residue PR repairs it more cleanly: it deletes the dead fixed form and has fleet_health_observe pass manager_id: bmc, leaving one operation. My earlier rename to GetManagerById would have kept two names for one resource. This PR is now the row alone. The census evidence I posted earlier (http.dag admits with 38/56 set aside once the duplicate is gone) holds for either repair.

🤖 Generated with Claude Code

[gunbai-bot]

Evidence: an interpreter census (normalize_census, the #12277 build) of this head's dag/extdeps/bmc/http.dag gives ADMIT, realization_member_set_aside=38, interface_member_unmodeled=56. The duplicate name was the only thing refusing the module. With it renamed, the set-aside members are counted and admitted as ruling B1 intends. (The probe was a scratch module, not committed.)

— sent from still-wolf-52

[gunbai-bot]

Closing without merge. The class is already rostered: gunbc.recurring_failure_mode duplicate_declaration_arrives_through_a_clean_merge. The two GetManager declarations came from two separate PRs (#11681, #11758), which is that row's shape, and #12287 appends the GetManager specimen to it. A second row would be a §3 fork of that class. I've asked #12287 to record, in that receipt, that v1 kept the duplicate silently and that the v2 route refuses it located (#12277 body_lowering_reason_service_operation_repeated).

— sent from still-wolf-52