Documentation follow-up to the multi-pattern presence feature (PR #232).
Task da2dd935 reviewed APPROVED at exact head 94c4617459 and squash-merged into the feature branch as d383373. Docs only: docs/ARCHITECTURE.md, design/ADMIN-SPEC.md (+ new 4.1 pattern editor), design/IMPLEMENTATION-ORDER.md, design/ENTITIES-AND-SERVICES.md, deploy/RUNBOOK.md (+ new 11 Upgrades and rollback). No code or test files. grep "zero or one" across docs/ design/ deploy/ returns 0; presence_schedules survives only in the rollback note describing the table migration 9 drops. The rollback procedure is documented but deliberately NOT rehearsed, and the runbook says so. The decision itself is recorded as D-016 in the project decision log (CTXD DECISIONS.MD v7).
Documentation follow-up to the multi-pattern presence feature (PR #232).
Task da2dd935 reviewed APPROVED at exact head 94c4617459b37b0f16230e4f38133441083f79b3 and squash-merged into the feature branch as d383373. Docs only: docs/ARCHITECTURE.md, design/ADMIN-SPEC.md (+ new 4.1 pattern editor), design/IMPLEMENTATION-ORDER.md, design/ENTITIES-AND-SERVICES.md, deploy/RUNBOOK.md (+ new 11 Upgrades and rollback). No code or test files. grep "zero or one" across docs/ design/ deploy/ returns 0; presence_schedules survives only in the rollback note describing the table migration 9 drops. The rollback procedure is documented but deliberately NOT rehearsed, and the runbook says so. The decision itself is recorded as D-016 in the project decision log (CTXD DECISIONS.MD v7).
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.
Documentation follow-up to the multi-pattern presence feature (PR #232).
Task da2dd935 reviewed APPROVED at exact head
94c4617459and squash-merged into the feature branch asd383373. Docs only: docs/ARCHITECTURE.md, design/ADMIN-SPEC.md (+ new 4.1 pattern editor), design/IMPLEMENTATION-ORDER.md, design/ENTITIES-AND-SERVICES.md, deploy/RUNBOOK.md (+ new 11 Upgrades and rollback). No code or test files. grep "zero or one" across docs/ design/ deploy/ returns 0; presence_schedules survives only in the rollback note describing the table migration 9 drops. The rollback procedure is documented but deliberately NOT rehearsed, and the runbook says so. The decision itself is recorded as D-016 in the project decision log (CTXD DECISIONS.MD v7).Independent Codex gpt-5.6-terra review completed for this exact commit.