docs(taxonomy): correct resync module's account of its own callers

[jfrench9]

Summary

Docstring-only correction to robosystems/operations/taxonomy_block/resync.py. No behavior change.

The module docstring claimed an admin CLI surface (just admin … taxonomy resync) and an auto-propagate-on-publish hook wrapped resync_tenant / resync_all_tenants. Neither exists — there is no taxonomy group under robosystems/admin/commands/, and both wrappers have zero callers.

What actually propagates

resync_library_into_tenant — the lower-level function — called directly from extensions migrations:

Migration	Package	Note
0022_metrics	rs-metric	initial seed
0023_metrics_m2	rs-metric	grown in place — the amend path, not just additive
0024_forecast	rs-driver	initial seed

Each reseeds public from the baked JSON-LD artifact via 0002's three seed passes, then fans a package-pinned resync across for_each_tenant_schema under the 0016 SET LOCAL robosystems.library_resync GUC.

Why it's worth a commit

Both facts were mis-read straight from the docstring during a planning pass:

1. The propagation machinery is proven in production, not unbuilt-and-unused — so a taxonomy change ships to tenants today by authoring a migration modeled on 0023.
2. Because every migration so far pinned a single package, rs-gaap core has never been re-propagated to a provisioned tenant. That is the real remaining gap, and it wasn't visible from the code's own description of itself.

The wrappers are kept deliberately — they remain the intended seam for a future operator entrypoint (a Dagster job; an admin CLI is unsuitable here because just admin runs on the host and the reseed reads the artifact from disk, so a prod invocation would seed the shared public library from the operator's local checkout).

Test plan

• uv run ruff check — clean
• uv run ruff format --check — clean
• No executable lines touched; diff is entirely within the module docstring

🤖 Generated with Claude Code