Adopt offline tool revision and opt-in version check across ConfluenceBridge CLIs #2

Goal

Apply the shared, manually invoked source-currency convention to this Python toolbox where meaningful, without changing Confluence page-version/delta-sync behavior.

Work

• Identify the actual user-facing entrypoint(s) and a canonical tool/release version. Do not confuse Confluence content versions in its manifest with the source code's commit.
• Provide a fast offline version identity showing installed Git commit/branch/dirty (or PEP 610 if later packaged as a Git-URL tool), and a separate explicit version check [--branch ...] for this repository.
• Remote verification must compare immutable commits to the original GitHub branch, show up-to-date/behind/ahead/diverged/unknown, and never install/update or touch exports, credentials, browsers, or existing output archives.
• If this repo intentionally remains a collection of independent scripts instead of a single CLI, document a consistent top-level entrypoint or a narrowly scoped alternative before implementing; avoid a large packaging rewrite merely for this feature.
• Add tests for offline/network/error behavior.

Reusable contract: https://github.com/SomeSunlight/context-canon/blob/main/nodes/library/development-workflow/docs/version-provenance-python.md, pending implementation/review SomeSunlight/context-canon#132 and SomeSunlight/context-canon#130. Adopt a released/accepted Context Node through normal ContextCanon onboarding/source acceptance if and when the project uses ContextCanon; do not copy generated package state or treat a pending PR as accepted.