5 Commits

Include renames

Author	SHA1	Message	Date
james.maesandClaude Fable 5.2	0d989683eb	fix(postgres): accept full_page_writes = off on Amazon Aurora PostgreSQL only ... RecordFilesPostgres refused every Amazon Aurora PostgreSQL database: Aurora reports full_page_writes = off (measured on engine 17.9) and the parameter is not in the cluster parameter group, so it cannot be changed. Its storage layer does not write torn pages, so the protection that setting gives stock PostgreSQL is not needed there. The settings query now carries a twelfth column, to_regprocedure('aurora_version()') IS NOT NULL, which is true on Aurora and false on stock PostgreSQL without raising. full_page_writes = off is accepted only when that column is true. Stock PostgreSQL with full_page_writes = off is still refused, and fsync, synchronous_commit, the writable primary, version, UTC, READ COMMITTED, the lock_timeout bound and every owner-table check are unchanged on both. Tests: PostgresDurabilityRuleTest (pure rule, every build) and PostgresAuroraQualificationTest (opt-in, real PostgreSQL 17, Aurora simulated by a test-only aurora_version() function and ALTER SYSTEM full_page_writes). Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>	2026-11-09 20:29:19 -06:00
james.maes	cef1476d85	Merge pull request 'feat: allow host-controlled admission for captured files' (#1) from feat/captured-photo-admission-policy into develop	2026-11-06 16:43:26 +00:00
james.maesandClaude Fable 5.1	1cdd06098d	chore(release): prepare the first published release candidate 0.1.0-RC.1 ... Prepare, without cutting, the first artifact to be published from this repository through the shared ci-workflows Maven workflow (push of develop to release/0.1 publishes 0.1.0-RC.N to the Gitea Maven registry). Add CHANGELOG.md, rewrite docs/RELEASE-STATUS.md with the publication path, the first-RC steps, the dependency cohort and the relationship to the GG Forge development pin 0.1.0-forge.162af9a7b8cd-archive1, and update the README banner, Maven-publication section and known issues. Carry the two Forge test-only PostgreSQL fixture patches verbatim (FixtureEndpoint resolves the reachable container endpoint instead of 127.0.0.1; fixture health is reported after each intake case). Recover the "-archive1" delta: the only class that differs between Forge's 162af9a7b8 and 162af9a7b8cd-archive1 JARs is ArchiveSecurity, whose digest guard now tolerates insert/update/delete customizers and still refuses query/get/personalization customizers. Express that in source with a focused ArchiveTest case. Stop ignoring .gitea/ so the shared CI caller is tracked normally and mark the retired platform-ci caller reference as superseded. Verification: ./mvnw verify against Collaboration 53bd8f00 installed as 0.1.0-rf53bd8f00-SNAPSHOT: 284 tests, 0 failures, 0 errors, 58 skipped, Checkstyle clean. Opt-in PostgreSQL/MySQL suites: 64 run, two pre-existing failures (public QQQ 4.1.0-RC.21 lacks QBackendTransaction.supportsRollbackCallbacks; the physical-drift probe in PostgresRecordFilesTest), neither introduced here. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: James Maes <james@kof22.com>	2026-11-06 09:08:21 -06:00
james.maesandClaude Sonnet 5.5	3f08c584d0	feat: allow host-controlled admission for captured files ... Keep the default quarantine policy for ordinary uploads and captures without a provider-resolved device identity. Audit the selected policy without fabricating a release or review event. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>	2026-11-05 08:23:14 -06:00
3 people	162af9a7b8	chore: preserve paused QBit work and document remaining issues ... Save the current implementation and README, status, and known-issue documentation at the user-requested stop. No completed release or deployment is claimed. Co-Authored-By: Claude <noreply@anthropic.com> Co-Authored-By: GPT-6 Codex <noreply@openai.com>	2026-11-04 10:45:26 -06:00