|
Some checks failed
CD / Build and push images (push) Successful in 4m20s
CD / Deploy to Test (push) Successful in 9s
CI / Lint, typecheck, test (push) Failing after 4m38s
CI / Auth e2e pack (push) Has been skipped
CI / Import/export fidelity gate (push) Has been skipped
CI / Build container images (push) Has been skipped
CD / Smoke tests against Test (push) Successful in 1m20s
CD / Promote to Int (push) Has been cancelled
Following a phantom wikilink now ends with a way out instead of a dead end: when the pond resolved and the page 404s as plain not_found, the error screen offers creating the page in place. Title = the URL slug (the PhantomPagesView mechanic), so every wikilink pointing at the address resolves; the invalidated page query then mounts the editor on the same URL. The affordance is deliberately ungated like the sidebar's new-page button — the client cannot tell 'never existed' from 'not readable' (#60), and a reader's POST surfaces as the regular 403 banner. The page_trashed branch (#31) is untouched. Rides along: PhantomPagesView now also invalidates ['pond-links'] — the graph views kept showing a just-created target as a phantom. e2e pack create-missing-page.spec.ts (CI wiring lands with #119): author a phantom link, follow it, create, backlink proves resolution; reader path asserts the 403 banner and no editor mount. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| access.json | ||
| apiTokens.json | ||
| auth.json | ||
| comments.json | ||
| common.json | ||
| editor.json | ||
| errors.json | ||
| export.json | ||
| files.json | ||
| font.json | ||
| graph.json | ||
| import.json | ||
| labels.json | ||
| legal.json | ||
| links.json | ||
| mails.json | ||
| members.json | ||
| notifications.json | ||
| plugins.json | ||
| public.json | ||
| quotas.json | ||
| search.json | ||
| settings.json | ||
| setup.json | ||
| system.json | ||
| users.json | ||
| watches.json | ||