Capture accumulated application, UI, CLI, regression tests and design documentation changes, including task project mapping and default CalDAV list naming. Keep deployment data, backups, local credentials and build artifacts out of Git. Move the Compose enrollment token to an ignored local environment file.
36 KiB
September 2026 execution ledger
User direction: continue the remaining roadmap in priority order; defer extremely complex/high-risk changes with explicit prerequisites. Preserve existing identity and deployments. This ledger separates completed slices from unresolved gates.
Active batch
Japanese design consolidation and Wiki publication (2026-09-19)
- Added a 22-chapter Japanese handbook plus index, separating current behavior, proposals, unresolved choices and historical claims. Original source documents remain unchanged in identity/location; a source inventory maps them to chapters.
- Expanded Organizer/tasks/tickets, calendar/contacts/DAV, RSS/FreshRSS/newsboat, IMAP capture and incremental HTML editing proposals with identities, authority, conflict/retention behavior, delivery slices and acceptance fixtures. No new external integration or connector is enabled by this design work.
- Reviewed primary RFC and FreshRSS/newsboat documentation; runtime/client compatibility remains a prerequisite, not a claimed implementation.
tools/design-exportrenders with the application Markdown renderer, validates internal chapter links and emits source/payload hashes. Tests cover tables, chapter count, bad links and staging overwrite refusal.- Uploaded 23 new
jaPage revisions through the trusted local data CLI tohttps://pages.anya.jp/lab/pageswiki-dev/; destination was empty beforehand. Read-back comparison and manifest/DB hash checks passed for all 23 payloads. Receipt:publication-ja-2026-09-19.json. Existing English sources are retained. - Anonymous HTTPS access still redirects to login. No publication/authorization
settings, external credentials, application runtime or deployment were changed.
go test ./...and diff checks passed.
Scoped automatic publication and compact blog index (2026-09-19)
- Added explicitly confirmed Street/Spot automatic publication, live revision and publisher-authority checks, inherited manual-approval boundaries, ACL/alias exclusions, and versioned impact previews. Existing settings stay unchanged; no production locality is opted in by this deployment. See automatic publication for limits and remaining work.
- Blog/diary and projected public indexes use compact date/title tables. The month selector sits above the sidebar calendar; authenticated row actions remain accessible through labelled icons. Existing post editing and public article navigation are preserved.
- Full Go tests, vet and diff checks passed. Opt-in Chromium coverage passed for automatic publication, City governance, periodicals and public projection.
- Follow-up: month input, apply and reset form a single compact row; SVG buttons have localized tooltips/accessibility labels. Desktop/mobile browser tests enforce single-line controls and placement above the calendar.
- Pre-migration online backups of both databases passed quick checks under
/home/anya/.cache/pageswiki-backups/pre-auto-publication-kv0VzP/. - Deployed app2 then app with image
sha256:8ca7973bb12126ba2291dc9e6e1c9a4c5faad77ff92b56cf4f79ee69e9620523. Both instances responded successfully with zero restarts; app is healthy. Public HTTPS serves the compact index and three RSS embedded article bodies; both databases still contain zero automatic-publication rules. Production mobile rendering confirms the one-line month controls. Anonymous source editing still redirects to login. - Future tasks/tickets, organizer/DAV, mail ingestion and HTML editing ideas are recorded in design backlog, not implemented in this batch. Full WYSIWYG remains an explicit undecided design choice.
Full-content RSS, standalone composition and X sharing (2026-09-19)
- RSS
content:encodeduses the inert HTML pipeline, namespace-aware XML/CDATA, absolute public article/image/anchor URLs and exact live Revision rechecks. Limits: 20 articles, 1MiB input/article, 8MiB total HTML, 5s generation; HEAD skips body work. RSS-reader copies cannot be remotely recalled after unpublishing. - Added authenticated GET-only
/v/blog/-/newand/v/diary/-/new, themed responsive forms backed by the existing atomic posts API. Projection targets redirect to the configured source composer. No GET creates content; disabled plugins return 404. - Post completion offers X Web Intent with title and registered projection-domain URL; multiple eligible Domains are selectable. Invalid/disabled/cross-Campus projections are excluded, and pending publication is explicitly warned/confirmed. No external posting occurs without user action; no OAuth secrets or new grants.
- Added namespace/CDATA, absolute link, unsafe HTML, composition route and share- domain/prefix regressions; Chromium covers standalone posting and sharing controls at desktop/mobile widths without navigating to X or creating production content.
- Full Go tests, vet, JS syntax, diff check and opt-in Chromium suites passed.
Deployed app2 then app with image
sha256:f51dadce7481b480bdd924ad65d050e6d9570a37081c91a7cd5562394d9be4bc. HTTPS RSS returned 200 with three embedded public HTML bodies and the content namespace; article returned 200 with target-domain OGP URL; both new-entry routes redirected anonymous requests to login (303). app healthy, both containers running with zero restarts. No production article creation or X posting was performed.
Dedicated public blog articles and RSS (2026-09-19)
- Dedicated diary/blog Domains now project approved source article bodies at
/YYYY/MM/DD[/keyword]. Header/browser title use target Domain branding; article pages keep month calendar, other entries that month and older/newer navigation. Known public article links in sanitized bodies are remapped to the target host. - Registered titles explicitly inherit the Page's live publication status. This changes the earlier h1-only index contract at the user's request. Private category, author and registration date are still omitted; dates derive from approved Paths. No registration table writes, grant changes or migration are needed.
/rss.xmlemits RSS 2.0 with up to 20 public titles, target-domain links/GUIDs and Revision timestamps. HTML advertises the feed. No private metadata or body copies in RSS; no shared HTTP caching. Subscriber-retained copies cannot be revoked.- Full Go tests, vet, diff check and Chromium tests at 1440/390 px passed. Tests cover keyword routes, domain title, escaped registration titles, sanitized body, previous/ next links, feed XML, private entries, edited-revision revocation and both auth modes.
- Remaining: Atom, excerpts/covers, publication approval of other metadata, cross- instance projection and SSO. Non-public embedded assets do not gain public access.
- Deployed app2 then app with
sha256:2a9743aadf687dedb7465b6e9c22f313818aa59fe341a94c5c6ec82c139386cf. Anonymous HTTPS index,/2026/09/17and/rss.xmlall returned 200 (one published entry); parent editor still returned login 303. Confirmed registered Japanese title, sanitized body, blog Domain header and calendar in/tmp/pageswiki-blog-article-review-0919.png. app healthy; publication count remains one and enforcing config unchanged. No production content/config writes were made by this task; current Object count is 1456 (live instance continues background work).
Public diary/blog projection index (2026-09-17)
- Root cause: configured projection views always required a session, even with approved publications in the source prefix. Added anonymous root/month/day views in enforcing and legacy target modes, using only the source's live publication manifest. Source authorization mode must remain enforcing.
- Dates derive from approved Paths; headings from approved HTML, bounded to 64KiB for at most 20 displayed and 8 recent entries. No private article metadata, categories, authors, editor dialogs or unrelated navigation is exposed.
- No grants, auth modes, schema or content changed. Body links remain on the source host. Source disablement, invalid credentials and publication revocation fail closed. Registration metadata approval and same-host body projection remain TODO.
- Validation: full
go test ./...,go vet ./..., JS syntax, diff check and existing Chromium periodical flow passed. New tests cover both target modes, private registration metadata, unapproved Paths, invalid credentials and edited revisions. - app2 then app deployed with image
sha256:36f5fba8a86db9ed6ea94872400bc86745c6499e3c09b49c11896303a953d86f. Anonymous HTTPS root/day views on blog.pages.anya.jp returned 200 with exactly one approved article; source article returned 200, parent editor and invalid credentials returned login 303. Browser screenshot checked at/tmp/pageswiki-public-blog-review.png. app healthy, both running without restarts. Object/publication counts remained 1455/1; authorization configuration unchanged.
Domain entry dialog CSS correction (2026-09-17)
- Root cause: the modal was nested in a dense administration table cell. Broad
descendant selectors made forms inline-flex, help paragraphs inline, and controls
inherit compact table sizing. Previously the browser test checked
openbut not actual geometry (a hidden panel ancestor could still conceal the dialog). - Moved modals outside tables and panels into the body. Added isolated responsive fields, block help text, themed controls, toggle labels, sticky header/close button, background scroll lock, accessible dialog title and CSS cache-version update.
- New Chromium regression checks at 1440/390 px with Light/Nanoha Dark: visible
viewport bounds, no horizontal overflow or overlapping controls, form/help display,
sticky close button and close/reopen. Screenshots inspected under
/tmp/pageswiki-domain-entry-review/. Existing periodical browser flow, full Go tests, vet and diff check passed. - UI-only release; no schema/content/permission changes or database restore.
app2 then app updated to
sha256:d2cb4a02e780790294245e60a394e6046be1f3160bc9e4186c0daf7f9a8a4369. Both health endpoints responded, zero restarts; served config.css matches source.
Local diary/blog projection deployment (2026-09-17)
- First slice: same-Campus, local-placement metadata projection, source-prefix filtering and source+destination read policies; no copied content. Article/body/edit links open the source Domain. No anonymous, cross-instance or host-preserving body projection yet. Local projection settings are not in federation manifests.
- Backup directory
/home/anya/.cache/pageswiki-backups/pre-periodical-projection-aw54pH/: app.sqlite and app2.sqlite, private permissions, both quick_check OK. - app2 then app deployed with image
sha256:e44fbb1a55f7eef4a4c4fec08a87efa8bc7e592f222c99090930c95590d435cf. Main DB initialization briefly left the listener unavailable during restart; final app health=healthy, app2 health endpoint OK, zero restarts, public HTTPS=200. Running template contains the domain-projection settings forms. - Full tests, vet, diff check, focused race and desktop/mobile Chromium passed. Fixture tests cover no-copy behavior, source ACL denial/revocation, prefix filter, source links, target write rejection, self/cycle/cross-Campus rejection and remote source fail-closed behavior.
- Production Objects=1454, publication entries=4, matching pre-update counts. No production projection bindings were created automatically; user chooses source.
Diary/blog and Domain entry deployment (2026-09-17)
-
User explicitly authorized backup and deployment. Online SQLite backups:
/home/anya/.cache/pageswiki-backups/pre-domain-entry-6a73yw/app.sqliteandapp2.sqlite, directory private / files 0600; bothPRAGMA quick_check=ok. -
Deployed accumulated date-path navigation, atomic article composer, Domain entry-settings gear/dialog and signed manifest v2 to app2 first, then app.
-
Continued implementation: signed manifest capability proof in enrollment; unknown/legacy approved peers block entry-setting updates with 409 and UI guidance. The check covers all approved Campus peers because they share a Campus manifest.
-
Final running image on both instances:
sha256:0dbcb4aacbc924855f0b686a859bd10c7932eea9d1736fc9f4be9a6337b694ae. app healthy, app2 running, zero restarts; Host-routed health checks both OK.https://pages.anya.jp/returned 200. Served periodicals.js hash matches source. Running template includesdata-domain-entry-open; authenticated gear/modal and posting interactions were exercised in isolated Chromium fixtures, not by creating production administrator sessions. -
Actual approved ext-node enrollment reports manifest_version=2. Old pending fingerprint remains pending; no approval or identity changes were made.
-
Main DB before/after: 1454 Objects and 4 publication entries. No entry settings, article content, user roles or publication grants were changed during deployment.
-
Tests: full
go test ./..., vet, diff check, browser fixtures at desktop/mobile, capability proof validation, legacy downgrade detection, incompatible-peer rejection, signed manifest integrity/rollback and focused race tests passed. -
Remaining: anonymous metadata/calendar publication approval, Domain-create form integration, entry-control release/GC, apply ACK/freshness and journal/outbox delivery.
-
Diary/blog initial built-ins — 2026-09-16.
content.diaryandcontent.blogprovide Domain-scoped, default-disabled settings, Page UUID metadata, calendar/recent entries, category/month/mine filters, and register/edit/unregister dialogs. Canonical content and revisions stay in ordinary Pages. Metadata writes reserve SQLite's writer before live membership, Path binding, grant/Locality and version checks; own-user Wiki authority matches the semantic editor. Metadata journal commits atomically; unregister/re-register generations prevent ABA replay. Private metadata is not exposed anonymously; Page publication behavior is unchanged. Atomic new-post composition, public metadata approval/feeds, comments and tDiary import remain explicit follow-ups. Full Go suite PASS (Server 12.417 s), focused race PASS (Server 5.745 s, Store 1.790 s), vet/JS syntax/diff checks PASS; combined config, public navigation, governance and diary/blog Chromium PASS (9.332 s). PC/mobile screenshots inspected under/tmp/pageswiki-periodicals-review/. DB-only backups at/home/anya/.cache/pageswiki-backups/pre-periodicals-drFK6Ljf/are mode 0600; both quick_check results areok. Backups use low-priority I/O. Rebuilt image:sha256:9948aca99fa03eb43dda06a03ae59a680cad3d5b5284fd6c2217e09d69f75c22. Deployed to both nodes: local Host-routed health checks returnok, zero restarts, served JS matches source. Both have all three additive tables and zero enabled instances. Main anonymous root remains 200; diary/blog require login (303) and unauthenticated metadata APIs return 401. Managed legacy-mode diary also requires login. Existing main objects (1,448), publication manifest (one) and approved entries (four) remain unchanged; no plugin was enabled and no article was registered in production during verification. -
Public children view controls now match the authenticated icon order and sizing (
▦,☷,≡), with localized tooltips/accessible labels and retained active state. Desktop/mobile Chromium PASS (1.948 s), focused navigation tests PASS (0.454 s), JS syntax and diff checks PASS. Rebuilt image:sha256:35b1fd0e0c291e42769b81dd50a53d237b94071431387c41b289d692a578e2b7. -
Anonymous navigation usability — 2026-09-16 23:19 JST. Added public root/virtual-parent directory landings and read-only
/v/browser/{path}; separate Page/child-folder links, compact responsive header and direct City exits. Public tree now supports all/per-folder expand/collapse, name/Path filtering and arrow/Home/End navigation. Component sorting keeps/a/xbefore/a-bfor correct branch operations. Children requests are capped at three concurrent fetches, cancellable and timed out, with generation-safe retries and view-only session preference. Initial directory/pagination links and macro fallback links work without JavaScript. Full Go suite PASS (Server 12.387 s), vet/JS syntax/diff checks PASS; focused race suite PASS (Server 7.287 s); broad Chromium suite PASS (19.837 s), including anonymous navigation at 1440 px and 390 px. Screenshots inspected:/tmp/pageswiki-public-navigation-review/public-navigation-{1440,390}.png. Tests cover failure/retry, view switching, hierarchy prefix collisions, pagination/exclusions, private-parent body suppression, bad credentials, mutation denial and warm-cache revocation. See contract. Both nodes rebuilt/deployed withsha256:cf75c402c04cb185e1c7965480c35b352e2182c857af9367e7b3dfa672a68597. Both local Host-routed health endpoints returnok, zero restarts; managed home returns 200. Main anonymous root/browser/tree/children/City return 200 (approximately 1–21 ms in local checks); protected autoplan remains 401. Public directory headers retain private/no-store and inert CSP. Served JS/CSS hashes match source on both nodes. No new schema migration; existing main publication remains one manifest/four entries and its governance, topology, binding, hash and head checks pass. No approvals or production content were changed; no public TLS ingress change or verification is claimed. -
Permission-aware public navigation — 2026-09-16 22:44 JST. Ordinary approved Pages now offer asynchronous children, structural breadcrumbs, read-only tree and filtered City Map; remove the public download control. Navigation-free presentation remains a future share-URL concern. Cached data uses SQLite mutation generations; authenticated membership/ACL decisions are evaluated per request. City reload/retry discards previous authorized labels before revalidation. See navigation contract. Full Go suite PASS (Server 9.335 s), vet, JS syntax and diff checks PASS; broad Chromium suite PASS (16.670 s); focused navigation/ACL/publication race tests PASS (Server 7.529 s, Store 14.706 s). Coverage includes warm-cache publication withdrawal and group removal without data-cache invalidation. DB-only SQLite backups in
/home/anya/.cache/pageswiki-backups/pre-public-navigation-FMqnj5pu/are 0600; both quick_check results areok. Both nodes rebuilt/deployed withsha256:aade0a87dbdd0966c92908836dda57f5d5a3440028cb2181194104c8ede9f9ae. Host-routed local health checks returnok, both running with zero restarts; managed home returns 200. Main anonymous tree/children/City HTML/map API return 200 (approximately 1–18 ms in the local smoke check), while autoplan remains 401. Tree response is private/no-store with inert CSP; main served JS hashes match source. Additive navigation schema has 45 invalidation triggers on each node. Existing main publication records remain one manifest/four entries; managed records remain zero. No publication was activated or revoked by this deployment. Public TLS ingress was not changed or certified by local checks. -
Document hierarchical approval requirements and approver Inbox delivery. Approval design defines inherited required floors, immutable review subjects, live reviewer authorization, transactional outbox/retry and recipient-private notifications. AP-1 through AP-6 remain unchecked implementation work; this design does not enable a new workflow.
-
Named user/group locality read or read/write permissions, stable subject identity resolution, superior-cap/authority-rank restriction preservation, next-request membership checks, Object alias caps and SQLite namespace fences. Explicit bounded anonymous current-revision approval/withdrawal now serves a separate inert semantic Viewer and streaming raw-media path with safe OGP. Per-scope publication generations prevent replaying pre-revocation consent. See scope, operational limitations and follow-ups. Whole Go suite passes (Server 10.176 s, Store 4.560 s), focused race suite passes (Server 6.206 s, Store 1.013 s), and approval/governance Chromium checks pass (1.994 s); the broader browser suite passed (27.547 s). Source-Domain restrictions also clamp exceptional foreign Object grants; a regression verifies that these exceptions cannot bypass the new ACLs. Vet, JS syntax and diff checks pass. SQLite backups (DB only) are under
/home/anya/.cache/pageswiki-backups/pre-locality-access-lpnkGqwV/, mode 0600; both pass quick_check. Both existing nodes deployed assha256:4a797ee34ef0c0fe0d48cea891a943393f0f722f07c192879f61b5dc3456ba9d. Host-routed local health checks returnok, both running with zero restarts. Served governance JS hashes match the workspace on both listeners. All five new access/publication tables exist and remain empty on both DBs: no production restriction or public approval was created. Main anonymous home remains 303, managed legacy home 200; anonymous access/publication administration requests are denied (main 401, managed 403). Managed public TLS/vhost remains the previously recorded infrastructure caveat; these are local listener checks. -
Quartier/Spot co-owner appointments, Domain/local publication-cap drafts, epoch/topology concurrency checks and in-transaction membership/authority revalidation; local before/after audit and Japanese/English modal settings. Includes bounded appointment-authorized member lookup. Full impact reports, structural mutation fences and anonymous publication remain pending; existing production visibility is unchanged. See governance contract. Verification: full Go suite (Server 8.584 s, Store 4.015 s), focused race tests (Server 2.698 s, Store 1.015 s), combined City/governance/search/HTML Chromium regressions (16.275 s), vet, JS syntax and diff checks pass. Pre-migration SQLite backups (DB only, not a complete DR package) are under
/home/anya/.cache/pageswiki-backups/pre-governance-aNwngqHe/, mode 0600. Both backups passPRAGMA quick_check. Both existing app nodes deployed assha256:dc6960ba1b01800b08351f660d20848dcca0e0f7f382fe18e362d93f7171d147. Local Host-routed health checks returnok, zero restarts; all four additive governance tables exist on both DBs, with no owners/policies automatically inserted. Served governance JS hashes match the workspace on both nodes. Anonymous governance requests are denied (main 401, managed 403); main home still redirects to login (303). No production owner appointment or public policy change was made as a smoke test. Existing managed public TLS caveat remains; these are local listener/Host checks, not a TLS infrastructure fix. -
P0 inert HTML display boundary across semantic/home/profile/object/history/ preview/print and HTML/Markdown Editor previews; canonical content unchanged. Application nonce CSP, forged macro-hook stripping, escaped failure fallback, bounded/cancellable City macro reads, and ACL-checked sandboxed diagram cache. See precise policy and compatibility. Owner/public APIs and new anonymous access remain disabled/pending. Final full Go suite passes (Server 7.866 s), focused race tests pass (Server 4.247 s, Store 1.057 s), and final HTML/PDF/archive/editor/bookmark Chromium tests pass (14.006 s). Broader City/search/login Chromium checks also passed (27.590 s).
go vet, editor JS syntax and diff checks pass. Read-only compatibility sampling was limited to 500 HTML revisions; it was not a complete Path audit. Deployed both existing nodes assha256:41cd97c7705b8be6b1bf763aee7678c5d510878d5ec6d78aa3b3792a7eb32517. Both local Host-routed/healthendpoints returnok, zero restarts; managed home returns 200 with nonce CSP, nosniff, private/no-store andX-PagesWiki-HTML-Policy: inert-v1. Main anonymous home still redirects to login (303). Both served Editor scripts match workspace SHA-256. No schema migration, production document rewrite, visibility change or TLS change. Managed public TLS/vhost caveat from the earlier social-card check remains outside this deployment; these checks do not claim public HTTPS there works. -
OGP/X cards for existing public semantic Page/home/City HTML, bounded canonical text extraction, configured-host canonical/image URLs, original image-document cards and an application-owned cached PNG fallback. No crawler auth bypass, external image fetch, schema migration or visibility change. Private/enforcing HTML suppresses metadata and adds noindex. See social card policy. Full Go suite (Server 6.818 s), social race tests (2.434 s), City/search Chromium checks (3.846 s), vet and diff checks pass. No claim of actual X post/card display; no post was sent. Deployed both nodes as
sha256:a16fa6cbe8a3a6b5141d7d29de0e6faef67989285a9983b2ffa306d4e016b75c; both health endpoints returnok, zero restarts. Managed-host anonymous home includes HTTPS OGP/card URLs, image HEAD returns 200/image/png (7,327 bytes), mainpages.anya.jpstill redirects anonymous crawlers (303). The common image is also reachable through public HTTPS; its 1200×630 output was visually inspected. No private production Page was made public for this test. External caveat:https://wiki.extpages.anya.jp/and its image fail TLS withunrecognized name; managed-host checks above used its local app listener with the configured Host. Public HTTPS image success was onpages.anya.jp. Fix the managed FQDN's TLS/vhost before expecting external cards there. -
City named-reference follow-up: qualified Street URLs, shared links, explicit UUID locality search, ancestor-aware lightweight details and literal Page links in both the map and inspector. No schema/data migration required. Whole-map loading is also deferred out of simple City breadcrumb macros. Verification: full Go suite, City/search browser regressions (including repeated Street names and three initial-focus levels),
go vetand JS syntax checks pass. City/search race tests also pass (Store 35.000 s, Server 7.391 s); the combined Chromium suite passes in 13.166 s. The HTML trust gate and broader CITY-A–D work remain open. Deployment: both existing app nodes rebuilt/recreated assha256:8e53fec5c485ed5763bf44705cfdf4071d04f2b8932dca038148eedda26f4c42. Both health endpoints returnok, zero restarts; main unauthenticated City request redirects (303), managed-host search returns 200 under its existing policy. Served City map/estate scripts match workspace SHA-256 hashes. -
OIDC issuer JWKS signatures, claim validation, bounded discovery/key cache; one-use browser state and collision-safe external account linking.
-
Bounded SMTP delivery, safe headers/mailboxes, live account checks.
-
Campus-admin inheritance revocation, provenance and local-right preservation.
-
Recursive Path mutations: transactional authorized snapshots and literal prefixes.
-
Browser mutation CSRF protection and explicit credential precedence/logout; browser/API purpose prefixes and atomic active-session checks.
-
Object authority scope and atomic creation provenance; safe all-alias purge.
-
Signed manifest allocation/application/checkpoint atomicity and authority guards.
-
City map/detail/Page list read filtering and private response caching policy.
-
Batch/request-scoped read authorization to reduce listing query amplification.
-
PDF/archive metadata scheduler projections with persistent bounded cache.
-
City generator Worker and directional keyboard navigation.
-
Search results: compact overview, full Page Path, matching-text excerpts and safe keyword highlighting; retain list/detail/thumbnail integration and read ACLs.
-
Object/Revision metadata pagination and localized history navigation.
-
Literal URL encoding in children list/detail/icon projections.
-
City one-connection-safe read snapshot and literal boundary lookup/health.
-
Atomic bounded zombie GC and Domain-provenance-scoped HTTP administration.
-
Integrated Go/browser tests, rebuild, and both instance health checks.
Update this list only after the corresponding implementation and verification. The broad phase checkboxes stay open when only a bounded slice has landed.
Focused implementations, constraints and regressions are linked from Implementation status.
Verification and deployment
Completed 2026-09-14 01:43 JST. All source changes were frozen before rebuilding; later edits only recorded the final outcomes in design documents.
- Final
GOMAXPROCS=2 GOCACHE=/tmp/pageswiki-go-cache go test ./... -count=1: PASS for all packages (server 5.947 s, store 3.105 s). - Targeted server/store
-racecovering authentication, inheritance, recursive/Object integrity, federation, GC, City and metadata projections: PASS (server 21.774 s, store 38.202 s). Independent focused race runs also covered search, pagination and the final deterministic GC regression fixture. - Opt-in Chromium: 13 suites PASS (48.544 s), covering real HttpOnly-cookie
login/logout, City normal/popup/mobile and Worker/navigation, search in all
three modes, PDF/archive/comic metadata, settings, execution monitor,
bookmark/Vim settings UI and editor/home. This does not validate the paused
vim.wasm runtime. Artifacts:
/tmp/pageswiki-hardening-final. go vet ./...andgit diff --check: PASS.- Before schema migration, online SQLite backups of both nodes completed with
PRAGMA quick_check=ok. Directory:/home/anya/.cache/pageswiki-backups/pre-hardening-20260914-1wH8jcKm/.app.sqliteandapp2.sqliteare mode0600; their containing directory is private. These are DB snapshots, not complete Document-store/key DR backups. docker compose build appanddocker compose up -d --no-deps app app2: PASS. Both containers run imagesha256:dc0ac3305c6a6abb42d84e56c8291cabc9c582a421f4ce91ca4276b123735ad2, with no restart loop. Both local/healthendpoints returnok.- Main-instance search CSS and City Worker client hashes match the working
files; managed-instance search CSS matches too when using its configured Host.
https://pages.anya.jp/and the protected main search route return the expected unauthenticated303; the managed Domain search route returns200under its existing read configuration. A foreign-Origin unsafe request is rejected with403. No production account credentials were used.
Browser behavior tests used isolated fixture databases, not production content. Live external OIDC/SMTP provider credentials and production multi-user flows were not exercised; protocol, denial and concurrency coverage used test fixtures.
Search timeout follow-up — 2026-09-14 03:47 JST
The user reported a search timeout after the initial deployment. Read-only production-data investigation found a Path-first repeated FTS scan and unbounded snippet input work, neither represented by the original small fixtures. Corrected the join order, rowid excerpt lookup, per-document/total snippet input budgets and optional 400 ms enrichment deadline. Results survive snippet-only timeouts; genuine search failures now have localized, non-leaking retry UI. See evidence and remaining search limits.
- Full Go suite PASS (server 6.869 s, store 3.511 s); search
-racePASS (server 2.967 s, store 8.063 s); Chromium search PASS (0.740 s);go vet ./...andgit diff --checkPASS. - Added query-plan assertions, a 600-Page/1,200-Revision regression, Unicode byte-budget/alias tests, deadline/error tests and large-body UI coverage.
- Read-only diagnostics against the existing main DB passed twice, with representative search processing times around 72–506 ms. No production account credentials or Page content were output or changed.
- Rebuilt/deployed both app nodes with image
sha256:0f10da866a03167da7811ddc88f66d6a65bd27aae17557c824a9f7b5071b88a8. Both/healthendpoints returnok, no restart loop, search CSS matches source on both configured hosts. No schema/index migration was needed.
City-first search and filters — 2026-09-14 04:05 JST
Added permission-filtered, metadata-only Quartier/Street/Spot results above Pages. Added a compact options disclosure for MIME/suffix categories, a single extension, and creation/update calendar-date ranges. Options persist in the GET URL and retry link. File-specific filters exclude City metadata; date filters apply to both. City/Page queries share the existing deadline and do not load the full City graph. See search contracts.
- Full Go suite PASS (server 6.746 s, store 3.470 s); combined search/City
-racePASS (server 4.288 s, store 10.257 s). Added filtered-query plan coverage also passed in the final Store search race run (18.373 s). - Chromium desktop/mobile (1440/390 px) PASS, including real City results,
safe links, match highlights, preserved filters, all Page view modes and
separation from file multi-selection. Final run: 1.173 s. Screenshots:
/tmp/pageswiki-search-city-final/search-results-desktop.pngandsearch-results-mobile.png.go vet ./...andgit diff --checkPASS. - Read-only main-DB verification: representative keyword search 79–515 ms, filter-only cases 1–6 ms, City metadata 2 ms. These are Store timings, not authenticated production HTTP measurements. No schema migration is needed.
- Both app nodes rebuilt/deployed with image
sha256:1f6d64c354e940c0941db9914a836f47e7285ac962a9c68f9b6cebcddd2e0dc3. Both/healthendpoints returnok, zero restarts, source CSS hashes match each configured host. Protected public search returns the expected303without credentials; managed-node filter-only search returns200under its existing read configuration.
Deliberate high-risk deferrals
- Executable authored-HTML compatibility is not supported. Normal HTML now uses the inert projection boundary; any future executable mode requires separate origin/capability approval and isolation tests. Public locality ACLs and owner governance still require transaction/cache revocation gates. See policy and acceptance tests.
- HA/LB writable metadata, controller DR promotion and distributed job leases: need a selected replication strategy, fencing, key custody and fault drills.
- Untrusted third-party code/plugin execution and native application launch: need isolated runtime, signature/capability lifecycle and a separate helper trust model; existing hosted editor integrations remain supported.
- Production S3/SSHFS/WebDAV/MWDB/Karton/SNMP/LDAP integrations: implement only after endpoint/credential policy and test services are available. No fabricated live integration claims or unrequested credential/infra provisioning.
- Broad notifications/inbox, comments, diary/tDiary import, rankings and external search: retain the existing detailed contracts; gate on transactional activity provenance, privacy/retention and authorization. Small prerequisites may land first, without claiming those product features complete.
- vim.wasm runtime remains explicitly on hold from the earlier user instruction.
These are not removed from the roadmap. Lower-risk outstanding items that do not fit this batch remain unchecked, with the next sequence recorded at handoff.
Next implementation sequence
- Complete locality Page/alias/dependency impact reports and structural mutation fencing on the implemented owner/draft-policy foundation. Require fresh activation consent and endpoint/cache revocation coverage before anonymous access; never silently activate saved drafts.
- Complete mutation authority/version fencing and local/external account ownership lifecycle, then remaining endpoint/adapter denial audits.
- Add shallow, paginated City projections and transactional mutation outbox / reconciliation provenance; retain manual curation when deriving from URLs.
- Replace remaining full directory aggregates and historical/raw-HTML FTS work with current-only bounded projections; add cancellation-aware streaming or immutable-hash clone operations for large binary changes.
- Resume activity/notification and trusted system-extension product slices after those authority and event-provenance prerequisites. Keep HA/DR and external-service provisioning behind their separately documented decisions.