Merge develop into the release branch to cut the next RC: QQQ 4.1.0-RC.26 / qbit-build-parent 2.2.1 alignment plus the stand-in replacements (core APIs instead of expired STAND-IN markers).
Conflicts resolved: the release <revision> is kept so the release build publishes the next RC; the legacy CircleCI / orb files are taken from develop. The tree is otherwise identical to develop.
Merge develop into the release branch to cut the next RC: QQQ 4.1.0-RC.26 / qbit-build-parent 2.2.1 alignment plus the stand-in replacements (core APIs instead of expired STAND-IN markers).
Conflicts resolved: the release `<revision>` is kept so the release build publishes the next RC; the legacy CircleCI / orb files are taken from develop. The tree is otherwise identical to develop.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Replace the platform-ci release callers with one caller of
KofTwentyTwo/ci-workflows maven.yaml (qqq-orb port).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Replace the CrmHealthChecks STAND-IN (qqq#1199) adapter onto the
qqq-middleware-health HealthIndicator with checks registered in the QQQ
4.1 core HealthChecksMetaData registry (crm.email, crm.sequence_lag,
crm.lead_score). The core HealthRunner schedules them and runs each as
the core system user. Drop the optional qqq-middleware-health dependency.
Also keep the lead-score incremental watermark at millisecond precision
to match modifyDate, fixing PlatformReuseTest skipping a same-millisecond
change on a warm JVM.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Keeps the release revision (0.2.0-RC.6) so the release build publishes
the next RC; legacy CircleCI/orb config taken from develop.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Merge develop into the release branch to cut the next RC: QQQ 4.1.0-RC.26 / qbit-build-parent 2.2.1 alignment plus the stand-in replacements (core APIs instead of expired STAND-IN markers).
Conflicts resolved: the release
<revision>is kept so the release build publishes the next RC; the legacy CircleCI / orb files are taken from develop. The tree is otherwise identical to develop.🤖 Generated with Claude Code