PUBLISH WIKI NOT WORKING (It's giving a 404 not found error)

[Monica-mwangi]

When publishing the wiki publish url it gives an error of 404 not found

[koolamusic]

Investigation context for the assignee

Publish flow (end-to-end)

1. Publish action: POST /wikis/:id/publish (HTTP) or publish_wiki (MCP) calls core/src/services/publish.ts
2. What publish does: sets wikis.published = true, generates a publishedSlug (nanoid), records publishedOrigin (the origin URL the caller passes, e.g. https://your-domain.com)
3. Public URL shape: <publishedOrigin>/published/wiki/<publishedSlug>
4. Public route: GET /published/wiki/:nanoid at core/src/routes/published.ts. Looks up by publishedSlug WHERE published = true AND deleted_at IS NULL. Returns 404 if: wiki not found, or wiki has no content (never been regenned).
5. Route mounting: mounted at app.route('/published', publishedRoutes) in core/src/index.ts:216. No session middleware (public route).

Key files

• core/src/services/publish.ts (publish/unpublish logic, origin handling)
• core/src/routes/published.ts (public GET endpoint, the 404 source)
• core/src/routes/wikis.ts:681-709 (HTTP publish/unpublish endpoints)
• wiki/src/components/wiki/WikiEntityArticle.tsx:288-350 (frontend publish state + URL construction from publishedOrigin)

Most likely root causes (ordered by probability)

1. Wiki has no content (never regenned). published.ts:36 returns 404 when !wiki.content. A wiki that's published before its first regen has content = null. Fix: either block publish until content exists (publish.ts already returns 'Cannot publish a wiki with no content' at wikis.ts:696, but check if the MCP path has the same guard), or show a "wiki is published but content is pending" page.

2. publishedOrigin mismatch. The origin recorded at publish time (stored in wikis.published_origin) drives the share URL the frontend renders. If the server runs behind Railway's proxy and the origin resolves to *.up.railway.app instead of the custom domain (or vice versa), the user clicks a URL that hits a different host or path. Check: SELECT published_origin, published_slug FROM wikis WHERE published = true on the affected instance.

3. URL path mismatch. The public route is at /published/wiki/:nanoid. If the frontend constructs the URL as /p/:nanoid or /wiki/:slug/public or any other shape, it won't match the route. Check: what URL does the frontend actually render in the share-link UI? Trace from WikiEntityArticle.tsx where publishedOrigin and publishedSlug are used.

4. publishedSlug not generated. If the publish operation completes but publishedSlug is null or empty, the lookup at /published/wiki/null returns 404. Check: SELECT lookup_key, published, published_slug FROM wikis WHERE published = true on the affected instance.

5. Proxy or CORS stripping the path. Railway, Cloudflare, or another proxy between the user and the server might rewrite /published/wiki/... before it hits the Hono router. Check the Railway service logs for the actual request path received.

Steps to reproduce

1. Start the stack (pnpm --filter @robin/core dev + env PORT=8080 pnpm --filter @robin/wiki dev)
2. Create a wiki with content (must have at least one fragment attached and one successful regen so wikis.content is non-null)
3. Publish via API: curl -X POST http://localhost:3000/wikis/<id>/publish -H 'Authorization: Bearer <token>'
4. Note the publishedSlug in the response
5. Try to access: curl http://localhost:3000/published/wiki/<publishedSlug>
6. If 404: check SELECT published, published_slug, content IS NOT NULL as has_content FROM wikis WHERE lookup_key = '<id>'

Quick DB diagnostic

SELECT
  lookup_key,
  name,
  published,
  published_slug,
  published_origin,
  published_at,
  content IS NOT NULL AS has_content,
  last_rebuilt_at
FROM wikis
WHERE published = true;

If has_content = false for any published wiki, that's the 404 source. The wiki was published before its first regen completed.

[koolamusic]

@Monica-mwangi I need you to take a look at this report as per #382