docs(qa): expand Q4 Logos Core testing commitments

content/qa/logos/2026q4-logos-core.md

@@ -5,14 +5,15 @@ tags:
   - "qa"
   - "logos"
 draft: false
-description: Validate Logos Core and establish automated testing foundations.
+description: Consolidate Logos Core test coverage and automate Delivery, RLN, and service-discovery integration scenarios.
 ---
 
 `ift-ts:qa:logos:2026q4-logos-core`
 
 ## Description
 
 Continue the Logos Core QA scope from Q3: evaluate stability, feature completeness, and integration risks, and establish automated coverage that can run in CI.
+Compare existing QA, end-to-end, and Doc Test coverage before extending it, reuse maintained harnesses, and remove confirmed duplication while preserving unique checks.
 
 ## Task List
 
@@ -34,6 +35,33 @@ Continue the Logos Core QA scope from Q3: evaluate stability, feature completene
 - Test reports summarizing coverage, findings, and confidence level.
 - GitHub issues for discovered defects or specification mismatches.
 
+### Analyze and consolidate testing coverage
+
+* fully qualified name: `ift-ts:qa:logos:2026q4-logos-core:coverage-analysis`
+* owner: florin
+* status: not started
+* start-date: 2026/10/01
+* end-date: 2026/12/31
+
+#### Description
+
+Inventory existing QA, end-to-end, UI, and Doc Test coverage across Logos Core and its messaging integrations.
+Compare scenarios and assertions, execution environments, platform support, CI frequency, ownership, and maintenance needs.
+Identify gaps and duplicate checks, then agree which suites to retain, extend, consolidate, or retire before expanding automation.
+
+Use these references as starting points:
+
+- [Chat module PR #76 and its Doc Test results](https://github.com/logos-co/logos-chat-module/pull/76).
+- [Logos Chat UI](https://github.com/logos-co/logos-chat-ui).
+- [Logos Delivery test harness](https://github.com/logos-co/logos-delivery-test-harness); confirm repository location/access before completing the inventory.
+- [Logos RLN end-to-end tests](https://github.com/logos-co/logos-rln-e2e).
+
+#### Deliverables
+
+- Coverage matrix linking scenarios and assertions to repositories, test layers, environments, owners, and CI jobs.
+- Agreed retain/extend/consolidate/retire decisions, with unique coverage preserved before duplicate tests are removed.
+- Prioritized implementation issues for missing coverage, maintenance gaps, and remaining public-network dependencies.
+
 ### Establish automated testing framework
 
 * fully qualified name: `ift-ts:qa:logos:2026q4-logos-core:automation-framework`
@@ -44,10 +72,67 @@ Continue the Logos Core QA scope from Q3: evaluate stability, feature completene
 
 #### Description
 
-- Select or adapt a harness suitable for Logos Core, including test runner, fixtures, and environment orchestration.
-- Implement automated scenarios covering the initial feature set and stability checks, and integrate their execution into CI.
+- Use the coverage-analysis findings to select or adapt maintained harnesses, including test runners, fixtures, and environment orchestration.
+- Reuse existing local execution support and provision controlled Logos Delivery fleets and required services for scenarios that still depend on public networks.
+- Automate setup, readiness checks, execution, teardown, and collection of diagnostic artifacts.
+- Integrate selected coverage into PR or nightly CI and consolidate confirmed duplicate checks without losing unique assertions.
 
 #### Deliverables
 
 - PRs establishing or adapting the testing framework and CI execution.
-- Automated scenarios for the initial Logos Core feature set and stability checks.
+- Documented, repeatable local and CI execution with controlled environments and diagnostic artifacts.
+- Consolidation PRs implementing the agreed coverage decisions while preserving unique checks.
+
+### Delivery module integration testing
+
+* fully qualified name: `ift-ts:qa:logos:2026q4-logos-core:delivery-module`
+* owner: TBD
+* status: not started
+* start-date: 2026/10/01
+* end-date: 2026/12/31
+
+#### Description
+
+Extend automated coverage of the Delivery module within Logos Core using the harnesses selected through the coverage review.
+Cover module initialization, peer connectivity, and message delivery between controlled instances, reusing existing scenarios where they already cover the required behavior.
+
+#### Deliverables
+
+- Reviewed Delivery integration scenario checklist and PRs closing identified coverage gaps.
+- Repeatable CI runs with assertions, diagnostic artifacts, and tracked integration defects.
+
+### RLN integration testing
+
+* fully qualified name: `ift-ts:qa:logos:2026q4-logos-core:rln-integration`
+* owner: TBD
+* status: not started
+* start-date: 2026/10/01
+* end-date: 2026/12/31
+
+#### Description
+
+Validate RLN integration with Logos Core and Delivery, building on existing RLN end-to-end scenarios and local execution support.
+Review coverage of registration, valid proof acceptance, invalid proof rejection, and rate-limit behavior, then automate the missing integration checks in controlled environments.
+
+#### Deliverables
+
+- RLN integration coverage checklist mapped to existing tests and agreed gaps.
+- PRs adding missing integration checks and repeatable CI execution, with tracked defects and failure artifacts.
+
+### Service discovery integration testing
+
+* fully qualified name: `ift-ts:qa:logos:2026q4-logos-core:service-discovery`
+* owner: TBD
+* status: not started
+* start-date: 2026/10/01
+* end-date: 2026/12/31
+
+#### Description
+
+Add automated service-discovery coverage through the Logos Core peer-to-peer module.
+Agree expected behavior with the implementation team and cover service discovery and subsequent connectivity in controlled multi-peer environments, including agreed failure and recovery cases.
+
+#### Deliverables
+
+- Reviewed service-discovery scenario checklist covering normal behavior and agreed failure/recovery cases.
+- Automated integration scenarios running in CI, with reproducible reports and tracked regressions.