Stale: the waves above are done, and the question about the scope of the beta is settled by its recommended option (b), by the standing rule to build the recommendation. The issues left on 1.0.0…
Still current on next at 162a2a3: no test checks the /metrics basic auth through the router. Ask: may TestMaintenanceModeKeepsOtherRoutes be extended to check that /metrics answers 401…
Checked against next at 162a2a3: the items still apply (the five request types remain; part of the unused surface is gone). Ask: which of these refactors should be built? Recommendation: none…
Still current on next at 162a2a3: the fetcher and magic accept SVG, orig of an input the processor cannot name is still saved as JPEG (formatFromString), and README.md now lists SVG…
Still current on next at 162a2a3: CacheConfig.CacheTTL is set from DefaultCacheTTL and never read. Decided as the recommended option, by the standing rule to build the recommendation:…
Ask: which of these do you want built before 1.0? Recommendation: all of them except dropping the totals tables (keep the lifetime figures), each as one reviewed PR on next in the order listed.…
The defect that held the tag on 2026-08-24 is fixed (sneak/webhooker#256), and the 1.0.0 milestone has no open issues. Ask: run webhooker in limited production yourself;…
Closed under your standing rule on recommendations: recovery stays engine-owned (option 1). Moving it into each target would copy the same scan into every target type for no gain today. The edge…
Decided by the fleet under your standing rule on recommendations: nothing in REPO_POLICIES.md governs TODO.md's sections, and the change is easy to undo. Option 1 it is. Completed Steps…
REPO_POLICIES.md already decides this, so it comes off your list. The schema lives in SQL files embedded in the binary under internal/db/migrations/: 000_migration.sql creates only the…
Review: changes needed.
README.md, the new paragraph on transaction names, says a request that matched no route has no pattern, so the hook withholds its name. That holds only for a path…
README.mdsection "HSTS": the last paragraph now says each header received over HTTPS replaces the storedmax-age, and names both ways to end the policy sooner: a shortHSTS_MAX_AGEsuch…
Fixed by the cap on parallel tests in sneak/pixa#235, on next as 162a2a3, as the cause found above says.
Model: opus-5-5