[recipes] Fix work-operating-model health endpoint routing

[eazene]

What

Fixes the health endpoint routing in the work-operating-model-activation recipe's MCP server.

Problem

The server registered its health check as app.get("/health"). Supabase mounts edge functions at /functions/v1/<name> and does not strip the function-name segment before handing the request to the function. Hono therefore sees the path as /work-operating-model-mcp/health, never /health — so the route misses and the request falls through to the app.all("*") catch-all, which enforces the MCP access key and returns 401 for what should be a public health check.

Fix

Move the health check into the app.all("*") catch-all as a prefix-agnostic suffix match (c.req.method === "GET" && c.req.path.endsWith("/health")), placed before the API-key gate so it stays public and works under any mount prefix. The absolute app.get("/health") route is removed. MCP request handling is unchanged.

Testing

Deployed to a live Supabase project and verified against the function URL:

• GET .../work-operating-model-mcp/health (no key) → 200 {"status":"ok",...}
• POST .../work-operating-model-mcp (no key) → 401 (MCP still gated)
• POST .../work-operating-model-mcp?key=... initialize → 200 with serverInfo (MCP unaffected)

🤖 Generated with Claude Code

https://claude.ai/code/session_01LxP7M99m4EF5Ve7rn3SNKH

[github-actions]

OB1 PR Gate

✅ Folder structure — All files are in allowed directories
✅ Required files — README.md and metadata.json found in all contribution folders
✅ Metadata valid — All metadata.json files passed JSON Schema validation
✅ No credentials — No API keys, tokens, or secrets detected
❌ SQL safety — SQL safety issues:

• recipes/work-operating-model-activation/schema.sql line 479: DELETE FROM without WHERE clause

✅ Category artifacts — Required file types present for each category
✅ PR format — Title follows [category] Description format
✅ No binary blobs — No oversized or binary files
✅ README completeness — All READMEs include Prerequisites, Steps, and Expected Outcome
✅ Contribution dependencies — All declared skill and primitive dependencies exist and are linked in README
✅ LLM clarity review — Covered by Claude PR Review workflow
✅ Remote MCP pattern — No local MCP server patterns detected — uses remote MCP correctly
✅ Tool audit link — Extensions/integrations link to the MCP Tool Audit guide
✅ Scope check — All changes are within the contribution folder(s)
✅ Internal links — All relative links in READMEs resolve to existing files

Result: 14/15 checks passed. Please fix the issues above and push again.

---

Post-Merge Tasks

These don't block merge — they're reminders for admins after this PR lands.

• Post in OB1 Discord #show-and-tell