fix(ssg): pass SSG_CONTEXT to forGetInfoURLRequest

Summary

Pass SSG_CONTEXT to forGetInfoURLRequest fetch (in fetchRoutesContent) so that isSSGContext(c) returns true and disableSSG() works as intended.

await pool.run(() => app.fetch(forGetInfoURLRequest, { [SSG_CONTEXT]: true })) // Pass SSG_CONTEXT

Details

In fetchRoutesContent, SSG_CONTEXT is missing in the forGetInfoURLRequest fetch, while it is passed correctly in the replacedUrlParam fetch.

As a result, during the build process,

• isSSGContext(c) incorrectly returns false.
• disableSSG() falls back to next() instead of c.notFound().
• Execution leaks into middlewares/handlers.
• In Cloudflare Workers projects, c.env is undefined during the Vite build, causing the following errors in every route:

TypeError: Cannot read properties of undefined (reading 'ADMIN_PASSWORD')
TypeError: Cannot read properties of undefined (reading 'd1')

I had to add manual guards like if (!c.env) return next() or if (!c.env) return c.notFound() to every app.use() and app.get() that accesses c.env, which is what disableSSG() should be handling automatically.

With this fix, I verified that the errors above are resolved and the manual guards are no longer needed. All existing tests pass with this change.

To reproduce,

1. Add a middleware that reads c.env (e.g. basicAuth with c.env.ADMIN_PASSWORD)
2. Add a route handler with disableSSG() that accesses c.env bindings (e.g. c.env.d1)
3. Run vite build with @hono/vite-ssg or toSSG