docs(qa): add 2026 Q4 commitments and tasks

content/qa/ift/2026q4-nim-libp2p-testing.md

@@ -0,0 +1,54 @@
+---
+title: Nim Libp2p Testing
+tags:
+  - "2026q4"
+  - "qa"
+  - "ift"
+draft: false
+description: Add dial ranking and backoff coverage and maintain nim-libp2p test reliability.
+---
+
+`ift-ts:qa:ift:2026q4-nim-libp2p-testing`
+
+## Description
+
+Continue nim-libp2p QA with coverage for opt-in dial ranking and backoffs carried over from Q3.
+Maintain existing tests as the library evolves and investigate regressions and flaky scenarios.
+
+## Task List
+
+### Opt-in Dial Ranking and Backoffs Testing
+
+* fully qualified name: `ift-ts:qa:ift:2026q4-nim-libp2p-testing:opt-in-dial-ranking-and-backoffs`
+* owner: radek
+* status: not started
+* start-date: 2026/10/01
+* end-date: 2026/12/31
+
+#### Description
+
+Implement tests for opt-in dial ranking and backoff behavior.
+Cover address and transport preference, concurrent dial cancellation, failed-address backoffs, and compatibility when the feature is disabled, in coordination with the P2P team.
+
+#### Deliverables
+
+- PRs adding unit and integration tests for dial ranking and backoffs.
+- Tracked defects and coverage gaps found during validation.
+
+### Maintenance
+
+* fully qualified name: `ift-ts:qa:ift:2026q4-nim-libp2p-testing:maintenance`
+* owner: radek
+* status: not started
+* start-date: 2026/10/01
+* end-date: 2026/12/31
+
+#### Description
+
+Provide ongoing QA maintenance for nim-libp2p, including regression fixes, flaky-test investigation, and test updates required by upstream changes.
+Handle issue-driven validation that does not require a separate feature-specific task.
+
+#### Deliverables
+
+- PRs maintaining tests and resolving failures or flaky scenarios.
+- Regression findings and verification results linked to tracked issues.

content/qa/index.md

@@ -8,6 +8,27 @@ tags:
 
 [[qa/preview|Roadmap Preview]]
 
+## 2026q4 `ift-ts:qa:`
+---
+
+### `ift`
+* [[qa/ift/2026q4-nim-libp2p-testing|nim-libp2p-testing ]]
+
+### `status:`
+* [[qa/status/2026q4-status-go-functional-testing|status-go-functional-testing ]]
+* [[qa/status/2026q4-status-qa-desktop|status-qa-desktop ]]
+* [[qa/status/2026q4-status-qa-mobile|status-qa-mobile ]]
+
+### `logos:`
+* [[qa/logos/2026q4-logos-basecamp|logos-basecamp ]]
+* [[qa/logos/2026q4-logos-core|logos-core ]]
+* [[qa/logos/2026q4-rfp-lambda-prizes-qa|rfp-lambda-prizes-qa ]]
+* [[qa/logos/2026q4-lez-fuzz-testing|lez-fuzz-testing ]]
+* [[qa/logos/2026q4-lez-sequencing|lez-sequencing ]]
+* [[qa/logos/2026q4-messaging-testing|messaging-testing ]]
+* [[qa/logos/2026q4-source-code-level-qa|source-code-level-qa ]]
+* [[qa/logos/2026q4-specs|specs ]]
+
 ## 2026q3 `ift-ts:qa:`
 ---
 

content/qa/logos/2026q4-lez-fuzz-testing.md

@@ -0,0 +1,38 @@
+---
+title: Logos LEZ Fuzz Testing
+tags:
+  - "2026q4"
+  - "qa"
+  - "logos"
+draft: false
+description: Maintain LEZ fuzz targets, corpus automation, and CI reliability as the implementation evolves.
+---
+
+`ift-ts:qa:logos:2026q4-lez-fuzz-testing`
+
+## Description
+
+Continue maintaining the LEZ fuzz testing framework in Q4.
+Keep targets compatible with upstream changes and preserve useful corpus handling, automated execution, and regression coverage.
+
+## Task List
+
+### Framework maintenance
+
+* fully qualified name: `ift-ts:qa:logos:2026q4-lez-fuzz-testing:framework-maintenance`
+* owner: Roman
+* status: not started
+* start-date: 2026/10/01
+* end-date: 2026/12/31
+
+#### Description
+
+- Maintain existing fuzz targets as LEZ code and interfaces change.
+- Extend or adjust targets for newly exposed execution paths, invariants, or regressions.
+- Maintain corpus update automation and CI execution, documenting infrastructure constraints when they arise.
+
+#### Deliverables
+
+- PRs maintaining or extending fuzz targets and regression coverage.
+- Corpus automation and CI maintenance changes.
+- Tracked findings and documented execution or infrastructure gaps.

content/qa/logos/2026q4-lez-sequencing.md

@@ -0,0 +1,36 @@
+---
+title: Logos LEZ Sequencing
+tags:
+  - "2026q4"
+  - "qa"
+  - "logos"
+draft: false
+description: Complete the remaining planned Cucumber test coverage for Logos Execution Zone sequencing.
+---
+
+`ift-ts:qa:logos:2026q4-lez-sequencing`
+
+## Description
+
+Continue automated behavioral testing for Logos Execution Zone sequencing, building on the Cucumber scenarios introduced in Q3.
+At Q4 planning, 63 of the 128 planned tests remain to be written.
+
+## Task List
+
+### Cucumber tests
+
+* fully qualified name: `ift-ts:qa:logos:2026q4-lez-sequencing:cucumber-tests`
+* owner: Roman
+* status: not started
+* start-date: 2026/10/01
+* end-date: 2026/12/31
+
+#### Description
+
+Implement the remaining 63 tests from the 128-test LEZ sequencing plan.
+Continue coverage of sequencer registration and related sequencing behavior, adapting scenarios to implementation changes and recording defects or missing prerequisites.
+
+#### Deliverables
+
+- PRs implementing the remaining 63 planned Cucumber tests.
+- Updated coverage tracking and issues for sequencing defects or blocked scenarios.

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

@@ -0,0 +1,73 @@
+---
+title: Logos Basecamp QA
+tags:
+  - "2026q4"
+  - "qa"
+  - "logos"
+draft: false
+description: Expand Basecamp MCP coverage, validate releases, and maintain existing automated tests.
+---
+
+`ift-ts:qa:logos:2026q4-logos-basecamp`
+
+## Description
+
+Continue the Logos Basecamp MCP testing work from Q3, expanding automated UI integration coverage for preparation, installation navigation, and workspace application lifecycle behavior.
+At Q4 planning, 61 of the 78 planned tests remain to be written.
+Validate release artifacts and maintain the existing smoke, UI, sandbox, and doctest coverage as Basecamp evolves.
+
+## Task List
+
+### MCP tests
+
+* fully qualified name: `ift-ts:qa:logos:2026q4-logos-basecamp:mcp-tests`
+* owner: Roman
+* status: not started
+* start-date: 2026/10/01
+* end-date: 2026/12/31
+
+#### Description
+
+Implement the remaining 61 tests from the 78-test Basecamp MCP plan.
+Keep new scenarios compatible with the existing test framework and track any scope changes or blockers as Basecamp evolves.
+
+#### Deliverables
+
+- PRs implementing the remaining 61 planned MCP tests.
+- Updated coverage tracking and issues for defects or blocked scenarios found during implementation.
+
+### Release validation
+
+* fully qualified name: `ift-ts:qa:logos:2026q4-logos-basecamp:release-validation`
+* owner: TBD
+* status: not started
+* start-date: 2026/10/01
+* end-date: 2026/12/31
+
+#### Description
+
+Validate Basecamp release artifacts and confirm the application starts cleanly on supported platforms.
+Run release smoke checks, report defects and release risks, and verify fixes.
+
+#### Deliverables
+
+- Release validation checklists and test reports for the builds tested during Q4.
+- Tracked release defects and verification results.
+
+### Test coverage and maintenance
+
+* fully qualified name: `ift-ts:qa:logos:2026q4-logos-basecamp:maintenance`
+* owner: Roman
+* status: not started
+* start-date: 2026/10/01
+* end-date: 2026/12/31
+
+#### Description
+
+Maintain and extend Basecamp smoke, UI, sandbox, and doctest coverage as the project evolves.
+Investigate failing or flaky tests, adapt existing scenarios to application changes, and add regression coverage where needed.
+
+#### Deliverables
+
+- PRs maintaining the existing suites and adding targeted regression tests.
+- Tracked application or test-framework defects and verification results.

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

@@ -0,0 +1,53 @@
+---
+title: Logos Core QA
+tags:
+  - "2026q4"
+  - "qa"
+  - "logos"
+draft: false
+description: Validate Logos Core and establish automated testing foundations.
+---
+
+`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.
+
+## Task List
+
+### Evaluate and test Logos Core
+
+* fully qualified name: `ift-ts:qa:logos:2026q4-logos-core:evaluate`
+* owner: radek
+* status: not started
+* start-date: 2026/10/01
+* end-date: 2026/12/31
+
+#### Description
+
+- Review shipped scope for Logos Core and create a focused acceptance checklist.
+- Log defects and gaps with priority/severity and expected fixes or LIP clarifications.
+
+#### Deliverables
+
+- Test reports summarizing coverage, findings, and confidence level.
+- GitHub issues for discovered defects or specification mismatches.
+
+### Establish automated testing framework
+
+* fully qualified name: `ift-ts:qa:logos:2026q4-logos-core:automation-framework`
+* owner: radek
+* status: not started
+* start-date: 2026/10/01
+* end-date: 2026/12/31
+
+#### 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.
+
+#### Deliverables
+
+- PRs establishing or adapting the testing framework and CI execution.
+- Automated scenarios for the initial Logos Core feature set and stability checks.

content/qa/logos/2026q4-messaging-testing.md

@@ -0,0 +1,54 @@
+---
+title: Messaging Testing
+tags:
+  - "2026q4"
+  - "qa"
+  - "logos"
+draft: false
+description: Maintain messaging testing frameworks and continue migrating interop tests into Logos Delivery.
+---
+
+`ift-ts:qa:logos:2026q4-messaging-testing`
+
+## Description
+
+Continue improving messaging test reliability by maintaining existing frameworks and migrating the remaining interop tests into the Logos Delivery repository.
+Adapt tests to messaging component changes, address regressions, and keep coverage useful as the implementation evolves.
+
+## Task List
+
+### Interop migration
+
+* fully qualified name: `ift-ts:qa:logos:2026q4-messaging-testing:interop-migration`
+* owner: radek
+* status: not started
+* start-date: 2026/10/01
+* end-date: 2026/12/31
+
+#### Description
+
+Continue the Q3 migration of messaging interop tests into the Logos Delivery repository.
+Port the remaining scenarios to the repository's E2E workflow, preserve relevant protocol coverage, and resolve failures or gaps exposed by the migration.
+
+#### Deliverables
+
+- PRs migrating remaining interop scenarios and integrating them into the Logos Delivery test workflow.
+- Tracked regressions and remaining coverage gaps identified during migration.
+
+### Maintenance
+
+* fully qualified name: `ift-ts:qa:logos:2026q4-messaging-testing:maintenance`
+* owner: aya
+* status: not started
+* start-date: 2026/10/01
+* end-date: 2026/12/31
+
+#### Description
+
+Provide ongoing maintenance of messaging testing frameworks.
+Update tests for messaging component changes, investigate failing or flaky tests, address regressions, and make minor framework improvements needed to keep the suites reliable.
+
+#### Deliverables
+
+- PRs maintaining messaging tests, fixing failures, and improving framework reliability.
+- Tracked messaging or test-framework issues found during maintenance.

content/qa/logos/2026q4-rfp-lambda-prizes-qa.md

@@ -0,0 +1,56 @@
+---
+title: RFP and Lambda Prizes QA
+tags:
+  - "2026q4"
+  - "qa"
+  - "logos"
+draft: false
+description: Provide QA for Logos RFP deliverables and Lambda Prizes submissions against agreed requirements.
+---
+
+`ift-ts:qa:logos:2026q4-rfp-lambda-prizes-qa`
+
+## Description
+
+Support Logos RFP and Lambda Prizes work by evaluating delivered software against the relevant brief and agreed acceptance criteria.
+Define concrete testing scope with the program and project owners as deliverables become available, record defects and coverage gaps, and verify fixes.
+
+## Task List
+
+### RFP deliverables QA
+
+* fully qualified name: `ift-ts:qa:logos:2026q4-rfp-lambda-prizes-qa:rfp-qa`
+* owner: TBD
+* status: not started
+* start-date: 2026/10/01
+* end-date: 2026/12/31
+
+#### Description
+
+- Review the requirements and acceptance criteria for RFP deliverables selected for QA with the program owners.
+- Prepare a focused checklist and test delivered functionality, including integration with Logos components where relevant.
+- Report defects and missing requirements, verify fixes, and document remaining limitations for acceptance review.
+
+#### Deliverables
+
+- Acceptance checklists and test reports for the RFP deliverables reviewed during Q4.
+- Tracked defects, verification results, and remaining coverage gaps.
+
+### Lambda Prizes submissions QA
+
+* fully qualified name: `ift-ts:qa:logos:2026q4-rfp-lambda-prizes-qa:lambda-prizes-qa`
+* owner: TBD
+* status: not started
+* start-date: 2026/10/01
+* end-date: 2026/12/31
+
+#### Description
+
+- Agree the QA scope for selected Lambda Prizes submissions with the program owners using each submission's brief and requirements.
+- Reproduce setup and key user flows, test claimed functionality, and evaluate relevant Logos integrations.
+- Report defects and gaps, verify fixes when available, and provide testing evidence for the program's review.
+
+#### Deliverables
+
+- Test checklists and evaluation reports for the Lambda Prizes submissions reviewed during Q4.
+- Tracked defects, reproduction steps, and verification results.