#2847 gatorwalk-factory: a tracker-side check that a factory definition fits its bound tracker

Follow-up to #2795, which binds a tracker instance to each factory and has validate check only that the instance's model type matches the definition's tracker kind.

Change

Add a read method on the tracker adapters (shared, in _lib/tracker/core/tracker_methods.ts) that takes a factory name, reads the factory's definition, and checks it against this tracker instance:

• every stage tracker.status key maps to a status this tracker has (its statuses argument, with the adapter's defaults, e.g. the Lab's map);
• a definition that declares stage tracker.entries is bound to a tracker with the history capability, or the check says the entries will be published as comments.

It lives on the tracker side because the engine cannot import the Lab's default status map across the seam (Seth, 2026-09-30, in #2795's plan review). Today a mismatch surfaces only when publish skips an unreachable status.

Done when

• The check refuses a definition whose stage names a status key the bound tracker lacks, naming the stage and key, and passes the bundled examples with their trackers.
• The driving skill's setup runs it after the factory's validate.