Go HTTP statuses, scoped join points and a reusable route scanner

A smaller release that closes three gaps people hit when guarding real seams.

• go-http-status transform. A Go status constant name such as StatusTooManyRequests becomes its number, 429. Now the statuses a Go handler writes can be compared with the numeric statuses a client in another language expects. An unknown name never matches a number, so the guard fails instead of passing.
• within on a join point. A join point can read only the regions you name, for example the default block of a file that also documents an alternative value. Every match inside the region still counts, so a drifted copy cannot hide, and a region that is not found is an error.
• Reusable route scanner. The go-chi route enumerator that check uses is available to joint-kind plugins, so a plugin that needs the server's routes does not keep a second scanner.
• Docs: pin Crossweft in CI by the release commit, with the tag in a comment, because a tag can be moved.