An unlisted page at /secret. Nothing in the app links to it, it has no nav
tab, and MobileNav's route-parity test now names it as an explicit exception
so an ordinary page still fails that test. It IS crawlable and is advertised
in the sitemap: "hidden" here means no button, not no index — a long,
specific mechanics page is worth the search traffic.
Every number on it was read out of the source or produced by RUNNING the
real function. A grimoire of plausible-sounding numbers would be worse than
none, because it would be believed. Four hand-rolled SVG figures (rarity by
moon phase, the passage ladder, the two twist curves) rather than a charting
dependency for four static pictures.
The best thing in it is a trap I did not know existed until I ran the code:
crossing over requires volatility strictly above 0.6, and favor shifts
volatility DOWN by up to 0.12 at mint. So a hunter at maximum favor pulls
spirits under the gate and locks themselves out of the largest reward in the
game — 25 essence and +0.08 favor. Verified directly: a spirit at volatility
0.65 is crossable at favor 0.0, and is not at +0.5 or +1.0. "Do not maximise
favor" is real, counter-intuitive, and follows from the source.
English only, as agreed — written as prose outside the i18n system rather
than several hundred translation keys, which keeps the en/es parity gate
meaningful for the actual UI.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The worst bug of the session. tests/conftest.py built its engine from
settings.database_url — the live database — and an autouse fixture calls
drop_all() before EVERY test. So every backend run silently annihilated the
real install: accounts, discovered spirits, Ghost Logs, devices, all of it.
Found it because /sitemap.xml listed zero entities minutes after I had
watched live séances mint real ones.
Tests now use TEST_DATABASE_URL, or `<configured-db>_test` derived from it,
and refuse to start at all if that ever resolves back to the production URL
— this box both serves the app and holds the repo, so "don't run tests in
prod" is not a workable guard.
Proven: inserted a canary row into production, ran 50 tests, canary
survived. Before this it would have been dropped.
Also in this commit:
SEO (routes/seo.py, lib/pageMeta.ts)
- Live /sitemap.xml generated from real entity rows, and /robots.txt, both
registered BEFORE the SPA catch-all or they'd be served index.html.
Crawlers are disallowed from /seance specifically because the open door
provisions a guest on arrival — a crawler would fill the users table with
wanderers who never existed.
- Per-route <title>, description, canonical and JSON-LD. The Codex is the
indexable asset here (every spirit is unique long-form prose) and all of
it previously shared one static title, so entities competed with each
other instead of ranking. Entities are marked up as fictional Persons so
a rich result can never imply a record of a real dead human.
- public_base_url setting: absolute URLs for crawlers can't be derived from
the request, since behind the tunnel the app only sees an internal host.
Camera channel, first half (lib/camera.ts, llm scry path)
- OllamaClient.generate() now accepts `images`; the configured chat model
(minicpm-v4.5:8b) is vision-capable, so the entity can speak about what
the seeker's camera actually shows. Verified against a synthetic room
image: it named the pale column and the small red cube, then misread them
as oak in a farmhouse parlor — real perception, in character.
- Frames are captured only on an explicit act, downscaled to 768px and
JPEG-compressed, never stored, and the prompt forbids describing faces or
guessing identity. CameraEye carries the same generation guard as the EVP
listener so closing during the permission prompt can't leave the camera
live after teardown.
338 backend tests pass; 375 frontend; i18n parity holds.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
