fix: require nimbuscms/nimbus at runtime, not only in development

[DanMat]

Two fixes and a new test class, from the core audit.

The packaging bug

  "require": {
      "php": ">=8.2",
      "ext-mbstring": "*",
+     "nimbuscms/nimbus": "dev-main"
  },
  "require-dev": {
      "phpstan/phpstan": "^2.2",
-     "phpunit/phpunit": "^11.0",
-     "nimbuscms/nimbus": "dev-main"
+     "phpunit/phpunit": "^11.0"
  }

This package's production classes implement Plugin, PluginContext, FieldType and Field. With core in require-dev, Composer would install this package without checking a compatible Nimbus was present — and the failure would show up as a class-not-found at boot rather than a resolution error at install time, which is much harder to diagnose.

The registrar API

Adopts the narrowed capability from nimbus#18:

- $context->fieldTypes()->register(new MarkdownFieldType(), self::ID);
+ $context->fieldTypes()->register(new MarkdownFieldType());

The loader binds the provider id now. A plugin that could name its own provider could name someone else's — and since rollback is provider-scoped, that was a way to get another provider's types removed.

PackageIntegrationTest

MarkdownFieldTypeTest proves the field behaves correctly when handed a value. This proves something different and easier to get wrong: that a real Composer installation of this package is discovered by Nimbus's own loader, using this package's real manifest, and registers with nobody editing core.

Everything is the genuine article — the installed composer.json, the real PluginLoader, the real FieldTypeRegistry. Only the path to installed.json is synthesised, because Composer writes that file about the root project and this package is the root when its own tests run.

Covers: manifest declares core at runtime and is typed nimbuscms-plugin · discovery registers into the shared registry under this plugin's id · core types untouched · disabling leaves it unregistered with a non-failure diagnostic · with it disabled, write paths refuse the type while the admin still shows the stored source and blocks saves · re-enabling restores it · a second package cannot take this plugin's id.

[OK] No errors
OK (29 tests, 84 assertions)     # was 21

dev-main stays for now — the path to ^0.1 is tracked under Release & packaging in the core roadmap.

🤖 Generated with Claude Code