@astrofoundry/pi-astro 0.34.0 → 0.34.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@astrofoundry/pi-astro",
-  "version": "0.34.0",
+  "version": "0.34.1",
   "description": "Personal pi customizations (extensions, subagents, skills, prompts, themes) for the pi coding agent.",
   "keywords": [
     "pi-package"

package/skills/edge/SKILL.md

@@ -13,7 +13,7 @@ Fetches `https://auth.37pla.net/.well-known/openid-configuration` through the VP
 
 ## `route-probe [name...]`
 
-HTTP status of the public routes of services on the Arcane VM, from Cortex through public DNS, the way users reach them: no credentials, no redirect followed. Without names it checks all of them: `supabase-auth-settings` (expects 401: it wants an API key), `supabase-jwks`, `supabase-openid`, `supabase-oauth-discovery`, `supabase-studio` (expects a redirect to the Pomerium sign-in), `grimoire-public`, `grimoire-public-health`, `mealie-public` (200). Each row has `httpCode`, `expected`, `ok`, `seconds`. A status says the route answered; it does not prove the application works or that a browser login succeeds. A failing route with a passing `probe` points at that service's route or container; ask `astro.identity` (Pomerium route) or `astro.arcane` (container) for their side.
+HTTP status of the public routes of services on the Arcane VM, from Cortex through public DNS, the way users reach them: no credentials, no redirect followed. Without names it checks all of them: `supabase-auth-settings` (expects 401: it wants an API key), `supabase-jwks`, `supabase-openid`, `supabase-oauth-discovery`, `supabase-studio` (expects a redirect to the Pomerium sign-in), `grimoire-public`, `grimoire-public-health` (200), `mealie-public` (expects a redirect to the Pomerium sign-in; checked 2026-10-19). `supabase-oauth-discovery` answered 404 on 2026-10-19: Supabase Auth serves that document only when its OAuth server is enabled, so a 404 is a configuration fact, not a route fault. Each row has `httpCode`, `expected`, `ok`, `seconds`. A status says the route answered; it does not prove the application works or that a browser login succeeds. A failing route with a passing `probe` points at that service's route or container; ask `astro.identity` (Pomerium route) or `astro.arcane` (container) for their side.
 
 ## `vps <command>`
 

package/specialists/edge/run.ts

@@ -88,7 +88,7 @@ export const PUBLIC_ROUTES: Readonly<Record<string, { url: string; expect: reado
     "supabase-studio": { url: "https://supabase-studio.37pla.net/", expect: [301, 302, 303, 307, 308] },
     "grimoire-public": { url: "https://cli.grimoire.monadeo.com/v1/auth/config", expect: [200] },
     "grimoire-public-health": { url: "https://cli.grimoire.monadeo.com/healthz", expect: [200] },
-    "mealie-public": { url: "https://mealie.37pla.net/api/recipes?page=1&perPage=1", expect: [200] },
+    "mealie-public": { url: "https://mealie.37pla.net/api/recipes?page=1&perPage=1", expect: [301, 302, 303, 307, 308] },
 };
 
 const HELP = `edge specialist (Frontdoor VPS through an IAP tunnel)

package/specialists/wrappers.test.ts

@@ -189,7 +189,7 @@ describe("edge wrapper", () => {
         const curl = async (args: string[]) => {
             seen.push(args);
             const url = args.at(-1) ?? "";
-            return { stdout: url.includes("/auth/v1/settings") ? "401 0.12" : url.includes("studio") ? "302 0.10" : "200 0.05", code: 0 };
+            return { stdout: url.includes("/auth/v1/settings") ? "401 0.12" : url.includes("studio") || url.includes("mealie") ? "302 0.10" : "200 0.05", code: 0 };
         };
         const all = await routeProbe([], curl);
         expect(all).toHaveLength(Object.keys(PUBLIC_ROUTES).length);