rebless(ruby): receiver-dot calls without parentheses are calls (gitgalaxy#3377)

[squid-protocol]

Re-bless owed by squid-protocol/gitgalaxy#3637 (label rosetta:rebless-owed, merged).

What changes

gitgalaxy#3637 gives Ruby its own calls_out family (CALLS_OUT_RUBY), so a receiver-dot call no longer needs parentheses. Three calls_out_to lists in data/ruby/expected_signals.json change:

file	probe	before	after
a.rb	probe_safety	[]	[freeze] (value.freeze)
b.rb	probe_telemetry	[info, error]	[logger, info, error] (Rails.logger.info(msg))
b.rb	probe_state	[push]	[push, pop] (items.pop)

Nothing planted moves. The manifest notes record the change.

Why these are right

• freeze and pop are already in docs/calls_out_truth.json's hand-derived periphery for ruby, which was written without the engine. The old engine simply missed them.
• logger is a genuine method call (Rails.logger returns the logger that .info is then called on), and it isn't on the forbidden list.

No ledger entry is added. This follows the gitgalaxy#3361 calls_out re-bless, which also changed calls_out_to with a manifest note only.

Verification (against the gitgalaxy#3637 engine)

• verify_language.py ruby: PASS, 88 assertions across 4 files.
• check_calls_out_truth.py ruby: PASS.
• na_check.py --ci, ledger_orphan_check.py --ci, ledger_issue_check.py --ci: clean.

Cross-repo

• Companion: fix(ruby): calls without parentheses, ?/! names, and methods owned by their class (#3377) gitgalaxy#3637. It has merged first, so verify.yml against engine main now carries the change.
• A run with engine_ref=pull/3637/head was also dispatched before I saw the merge.
• After this merges, bias-history.yml regenerates the bias report and chart and closes the "corpus owes a re-bless" drift for ruby.

🤖 Generated with Claude Code

https://claude.ai/code/session_01YAtpBfGGyBGGovitSVaM5Q