Repository navigation
fix(www): tighten CPD demo copy for Cuban share - #1451
Merged
Merged
Conversation
Add independent/non-affiliation disclaimer, replace named-provider BAA example with non-BAA vs BAA-covered wording, align compaction to ~950× with labeled MCP vs raw HTTP sizes, date the $5.41 cash price, and soften WORM dual-write to planned. Co-authored-by: Daniel Smith <danielsmithdevelopment@gmail.com>
WORM dual-write is already production-ready behind CLAWQL_WORM_ENABLED=1; the prior "planned" soften was incorrect. Restore an accurate step-7 claim and enable sqlite clawql-audit dual-write in the CPD gateway smoke with an /entries assertion so the live path proves it. Co-authored-by: Daniel Smith <danielsmithdevelopment@gmail.com>
…ests Distinguish tamper-evident dual-write (sqlite/postgres + hash chain) from storage WORM. PutObject now sends Content-MD5, IfNoneMatch, and optional Object Lock COMPLIANCE/GOVERNANCE retention. Probes assert the original version body is unchanged after overwrite, plain delete only adds a delete marker, and DeleteObject(VersionId) of a locked version is refused. MinIO integration tests (governance + 1-day compliance) run in CI; R2 is documented as not supporting the S3 Object Lock API. CPD demo copy matches. Co-authored-by: Daniel Smith <danielsmithdevelopment@gmail.com>
actionlint/shellcheck SC2034 on the clawql-audit MinIO readiness loop. Co-authored-by: Daniel Smith <danielsmithdevelopment@gmail.com>
Satisfy @typescript-eslint/no-this-alias by destructuring instance fields instead of const self = this. Co-authored-by: Daniel Smith <danielsmithdevelopment@gmail.com>
Docker Hub denies minio/minio pulls; use the published quay.io tag so the clawql-audit Object Lock integration job can start. Co-authored-by: Daniel Smith <danielsmithdevelopment@gmail.com>
Co-authored-by: Daniel Smith <danielsmithdevelopment@gmail.com>
Docker Hub no longer serves minio/minio and quay.io/minio pulls are unauthorized on this runner. Gate unit/simulator tests first, then use localstack/localstack:4.3.0 for live S3 Object Lock integration. Co-authored-by: Daniel Smith <danielsmithdevelopment@gmail.com>
Co-authored-by: Daniel Smith <danielsmithdevelopment@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Cuban-share copy fixes on
/demo/cost-plus-drugs, plus a real S3 Object Lock storage-WORM path inclawql-audit(with the tamper-evident vs WORM distinction spelled correctly).Demo page copy
$5.41 as of Oct 30, 2026clawql-audit Object Lock
Content-MD5+IfNoneMatch: *+ optionalObjectLockMode/ObjectLockRetainUntilDateDeleteObject(VersionId)refusedCLAWQL_WORM_S3_OBJECT_LOCK=compliance|governance|0,_DAYS,_VERIFY_OBJECT_LOCKTest plan
vitestclawql-audit: 37 passed, MinIO IT skipped locally (no Docker), runs in CI