James MaesandClaude Sonnet 5.5
63245b14e0
One reviewable integration on current develop 7d61f29e. It starts from
feat/record-files-standalone (attachment lifecycle, upload journal, retention
SPI; descends from develop) and adds the owner stack content from
feature/collab, feature/collab-int-20261029, feature/field-values-1196,
feature/presence-recovery-1300, test/presence-capacity-1302 and the
fix/attachment-transactions-1289 / fix/mywork-query-bounds-1291 work, plus
KOF22 adaptations: CollaborationQBitConfig.attachmentLifecycle,
CollaborationRecords.insertActivity/query(transaction), ActivityWriter source
feature routing, and the Redis/fixture tests.
Build: develop CI files are preserved. pom.xml only adds the Redis API
guardrail allow-list and an optional qbit-redis dependency; the core and
qbit-redis versions stay on the canonical SNAPSHOT lines with markers to repin
after the core and redis integration PRs are published (order CORE -> REDIS ->
COLLAB). No PRIVATE or feature-snapshot coordinate is introduced. Not yet
compiled: it needs the core integration artifact (virtual-field providers).
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
3.0 KiB
Coordinated collaboration integration candidate
This branch combines the current heads of the attachment, My Work, presence recovery, virtual-field and capacity PRs. It is a qualification candidate, not a published release or a deployed host.
| PR | Included source |
|---|---|
| #45 attachment settlement | dc65a826ce362416d55d91136fa39225f4a7cf94 |
| #46 bounded My Work | cdcf7ee36509c7a1fc6f22fa864209eb80a6ff34 |
| #47 presence recovery | 776ebe3fcb6492881bc9d7ec3f6ca6adfa320200 |
| #48 contributed field values | 1da538cf43ba1ed80e3f8fd599729b5691563cbf |
| #49 capacity qualification | 56a8b760d9c1a1862cb11e80fad07cf5cdc20b3a |
All five heads are ancestors of integration commit
44a89d77b1ad3a39d26c512ada78af0884872013. The stacked My Work and capacity
branches did not contain the latest heads of their base PRs, so those base
heads were merged explicitly as well. No production source was rewritten during
integration. The core prerequisite remains
4.1.0-virtual-field-values-1196-cc3981bb3-SNAPSHOT. The candidate now selects
published Redis 0.1.0-redis-integration-20261029-551f1d5-SNAPSHOT after native
publisher job42 succeeded and independent timestamped POM/JAR downloads matched
their declared version and repository checksums. The timestamp is
20261029.165102-1; JAR SHA256 is
385f69c5d84362dbab40a3044261fb9820e25126785d7f22901121302e6ce076.
The caller and manifest both select released kingsrook/qqq-orb@0.8. The
canonical validator extracted from released 0.8.32 and CircleCI schema validation
pass; no unpublished orb changes are used.
Local ./mvnw.cmd verify -Dqqq.mywork.load=true ran 238 tests with no skips, but
reported three failures and four errors. Failures include Redis command read
timeouts/rejoin assertions and PostgreSQL connection I/O during the attachment
fixture. Docker Desktop's published-port path has independently exhibited
300–900 ms replies after idle, compared with 0–58 ms on a direct Docker network.
This observation is not proof of every failure's cause. No timeout, assertion,
security boundary, or quality gate was weakened. Native hosted Linux results
are required before publication; the local run is not a passing gate.
Native CircleCI job192 subsequently passed the full verification at integration
head 02085baff928c374e3b0d77367fbcc8182f81f93; CodeQL also passed. Those checks
used the earlier Redis pin. The new published Redis pin above requires its own
current-head native verification before this collaboration artifact is published.
Use an explicit short feature branch (feature/collab-int-20261029) and dry-run
the released version calculator: generated help-bundle versions must remain at
most 50 characters. The longer collaboration-integration-20261029 name would
produce 57 characters and is not a valid publication route.
The successful earlier combined-source checks remain historical evidence only. Host TLS/ACL, actual identity/proxy/provider acceptance, maintenance/restore enforcement, artifact publication, and deployment are separate gates.