1.0.2

Fixes a permanent "update available" loop.

The manifest said 1.0.0 while the release was tagged v1.0.1. Tiger_Update_Checker compares the version recorded at install — which comes from module.json — against the newest GitHub release. So the update ran, applied v1.0.1 correctly, read the manifest, wrote back 1.0.0, and the checker went on offering v1.0.1 forever. The update could never satisfy itself.

Observed on dev-com as ref=v1.0.1 sitting alongside version=1.0.0.

• module.json bumped to 1.0.2 so it matches the tag
• Added the Version check workflow tiger-core has always had, which fails a tag build when the two disagree — the guard the module repos never got, which is why three drifted in the same batch

No code changes. Updating to 1.0.2 clears the loop.