fix(service): replace forbidden global Hono type augmentation with exported ServiceEnv

[rickylabs]

Why

The atomic JSR publish aborted at @netscript/service@0.0.1-alpha.2 (18/31 landed, then failed). This is root cause #3 — distinct from the relative-path escape fixed in #124 and the publish-loop bug fixed in #123.

JSR rejected the package with:

modifying global types is not allowed
file:///src/auth/hono-context.ts:10:16

deno publish --dry-run does not catch this — it is a server-side JSR check — so both local and CI dry-runs passed green while the real publish aborted. (Motivates the planned stronger internal preflight.)

hono-context.ts used declare module 'hono' { interface ContextVariableMap { … } } to globally augment every Hono app's context variables. JSR forbids ambient global-type modification in published packages.

What

• Remove the declare module 'hono' augmentation.
• Export ServiceVariables + ServiceEnv as the JSR-compliant opt-in — consumers type their app new Hono<ServiceEnv>() instead of relying on global pollution. Re-exported from @netscript/service/auth.
• Drop the three now-dead import './hono-context.ts' side-effect imports (types.ts, auth-middleware.ts, service-builder-impl.ts).

Behavior-identical for the package's own code: its plumbing already typed contexts as plain Context/MiddlewareHandler (env defaults to any), so c.get/set('principal'|'logger') resolve the same before and after. The test suite owns its own AuthTestEnv and never depended on the augmentation.

Validation

• deno check --unstable-kv ./mod.ts ./src/auth/mod.ts — clean
• deno test ./tests/ — 57 passed, 0 failed

After merge, re-firing publish.yml --ref main publishes the remaining 13 packages at 0.0.1-alpha.2 (the 18 already-live skip via JSR idempotency).

🤖 Generated with Claude Code