10B. Pin what a container set after boot really does (just tests)

[nikolaystrikhar]

What: tests for Absorber::boot(), the collaborator accessors and the plugins_loaded steps when Config::set_container() is called after boot.

Usage: none — the behaviour is unchanged. What changes is that the warning on boot() is now a behaviour the suite holds: the hooks keep the container boot closed over, the accessors answer for the replacement, and a second boot() binds nothing into it.

Why this way:

A warning only a docblock makes is a warning nothing enforces. Two live containers is the failure mode a host hits by wiring set_container() from a service provider, and until now the suite would have stayed green through any change to which half resolves from where.

Asserted by loading a sub-plugin and reading Absorber::all(), not by counting resolutions. The damage is not that two containers exist — it is that the load pass works while the registry a host can reach reports nothing, with no report in between, which is exactly what a host would go debugging.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Enterprise

Run ID: 855b7ed1-6720-4257-82fc-07724d59e780

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

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