Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "b5v07"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Batch 5 of v0.7 (b5v07).
Reviews: W1-W3 wave reviews, fix rounds fx1-fx4s, whole-branch final review per feature with adversarial probes, final fix round fx5. Strings approved by Nikola 2026-11-09/10. Local verification at
fd503ccc: build, vet, gofmt clean; internal/api, cmd/cairnd and internal/storage/versions full; touched packages; deploy, config, webcheck, audit; web suite 2393/2393; all 69 a11y files ok.wazero v1.12.0 already keys every compile-cache entry by content: fileCacheKey = sha256(Module.ID, "WAZEVO", CPU features) with Module.ID the sha256 of the WASM bytes and flags, and each entry's header carries the wazero version (another version is stale and deleted). A different pdfium.wasm or wazero can never load an old native entry, so hashing go-pdfium's embedded module through a linkname into its internal package bought nothing. Marker "cairn pdfium compile cache 3": go-pdfium and wazero "path version sum" lines from the build info ("<path> unknown" when absent), GOOS/GOARCH and runtime.Version(); it only empties the folder when the build changes. cacheMarker cannot fail any more (the "wasm" refusal reason is gone). Tests: the embedded-module test is replaced by TestCompileCacheMarkerBuildChangeCcm6405 (a new go-pdfium version empties the folder; missing build info keeps the cache on). Docs: CHANGELOG v0.6.405 Fixes, configuration-reference, security-standards, ARCHITECTURE.PurgeGuard.RequireSession (internal/api/purgeguard1104.go) refuses every permanent delete that is not a browser session with the caller's own cookie: 403 needs-session, purge-refused audit (trash, admin tier), WARN once a minute per device or account+client, red bell device-purge-refused via notify.AddOrCount (added once a day per device, per account for account passwords; counted after) and so the security mail KDevicePurgeRefused. DELETE /api/v1/trash/{id} asks it first; TrashAPI.purge takes a PurgeOK; the AST sweep test holds every purge primitive caller to the token. trash.OriginOf names the entry for the audit event. Existing test rigs that purge through the route now send their session's own cookie and wire a guard.