- New diary module: For, Bootstrap, Setup, SetVerbosity, Reset, Close, ParseConfig
- Proxy component handler safe in package vars; styled console handler in bonfire's palette
- Daily writer: one file per day, 0640, lazy open, retention, disables itself on open failure
- Every channel leaf wrapped by sunscreen.Wrap; stack via slog.NewMultiHandler
- bonfire: ColorMode, Palette, DefaultPalette, DetectProfile (lipgloss v2, colorprofile)
- Generated main runs diary.Bootstrap first and diary.Setup after compass.Load
- Ignore /storage/ and /examples/hello/storage/
- Decision note: lipgloss, bubbletea, bubbles, huh, fang v2 and colorprofile, fang used narrowly, own diary console handler, stdlib daily writer
- STACK.md Supporting Libraries rows for the six modules
- sociallogin: TestRegistry, TestNormalizeFrontendCallback,
TestNormalizeReturnTo, TestCodes, TestEmailVerified, TestGothProviders,
TestErrorMessages
- docker: the eighteen Postgres-backed plugin unit tests, TestNOAuth,
TestRegisterComplete and TestStateCookie among them
- TestPullConcurrent: 64 concurrent Pulls of one key, one winner, 20 rounds,
on memory and miniredis
- TestPullExpired: an expired value is never returned and is gone afterwards
- TestPullPrefixIsolation: Pull touches only its own <prefix>cache:<key>
- TestPullDocker: the same on redis:7-alpine (GETDEL)
- scripts/check-phase19.5.sh: go, userplugin, sociallogin, demo, bm,
fonoteka, docker and docs stages across six repositories
- go test -json detector fails on a failed, skipped, missing or zero test;
vitest detector requires oauth.test.ts and refuses skips
- additive user-plugin check against 4c5d3b8 and no updates/ change (D-22)
- --self-test proves the detectors and the docker NOT RUN rule
sm-sociallogin-plugin mounted in sm-demo-app and sm-bm-app (Microsoft 365
with the frontend callback, consent and link-ticket views), fonoteka.go
pinned to sm-user-plugin v0.1.4. User setup for the Entra registration;
one unrelated fonoteka route-inventory failure deferred.
- sm-sociallogin-plugin v0.1.0 (private repo), pinned to summercms v0.3.1
and sm-user-plugin v0.1.4, all pushed and tagged in D-21 order
- v0.3.1 changelog posted after the User-Agent fix (fix-ua)
The layers read NUXT_CACHE_PURGE_TOKEN and strip the purge keys from
nuxt-site-config; demo.summercms.io and summercms.io/changelog run the
fixed builds with rotated tokens (check-live ok, 0 purge keys live).
