Repository navigation
[Bug] Align quality CI core and smoke fixture identities #518
Description
Observed failure
The existing modules quality matrix fails on a planning-only PR. No runtime, dependency declarations, workflows or tests were changed by that PR.
- Python 3.11 and 3.13 reject the declared immutable core dependency
==0.55.4against the paired checkout installed as0.55.10intest_declared_core_dependency_supplies_registry_handoff. - Python 3.12 stops in the existing runtime discovery smoke with
Smoke fixture identity does not match the reviewed commit. - Current modules
devis593656f675eaf4954b609aca51aa6504367dc02e; the affected workflow, declaration and test inputs match that base. This is deterministic environment/fixture drift, not a reason to relax their checks or retry jobs as flakes.
Evidence
- Planning PR: docs(code-review): plan project-aware local review reset #517
- Python 3.11: https://github.com/nold-ai/specfact-cli-modules/actions/runs/38958180468/job/117168732462
- Python 3.12: https://github.com/nold-ai/specfact-cli-modules/actions/runs/38958180468/job/117168732463
- Python 3.13: https://github.com/nold-ai/specfact-cli-modules/actions/runs/38958180468/job/117168732709
- The next planning head repeats the Python 3.12 fixture failure: https://github.com/nold-ai/specfact-cli-modules/actions/runs/38960712322/job/117174901260
Bounded maintenance outcome
- Reconcile the intended immutable installed core dependency with the supported CI pairing semantics using a dedicated change and observed failing-first tests.
- Prepare the smoke fixture at its reviewed immutable identity through existing supported setup.
- Preserve dependency constraints, fixture integrity, signature/security gates and required test coverage; demonstrate the Python 3.11/3.12/3.13 matrix on the final inputs.
- Keep the local-review architecture/planning PRs free of runtime implementation, dependency upgrades and CI/proof-policy changes.
This issue tracks current CI maintenance independently of the planned capsule hard cut. It does not reopen capsule feature delivery, change C15 ownership, change the replacement stories' native prerequisite graph, authorize implementation, or establish merge readiness. Core's frozen MCP advisory remains independently tracked in nold-ai/specfact-cli#747.
Metadata
Metadata
Assignees
Type
Projects
- Status
Activity
djm81 commentedon Oct 16, 2026
The final reviewed planning head
0b5fea0057afb570c3c512da2ab7c59c8aec488brepeats both failures in the current matrix. This confirms the blocker remains after planning review convergence.test_declared_core_dependency_supplies_registry_handoffwithassert '==0.55.4' == '==0.55.10'.The repair must preserve the immutable development-core contract, the intended paired-core compatibility check and exact clean smoke-fixture verification. Separate these CI inputs where necessary. Do not weaken the equality assertion or fixture verifier to make #517 green. The affected inputs remain identical to base
dev, so retrying these failures cannot resolve the mismatch. The planning PR retains its reviewed head and contains no CI or runtime implementation.djm81 commentedon Oct 16, 2026
The owner explicitly authorized implementation in a separate maintenance PR on 16 October 2026. Work is isolated on
codex/ci-fixture-identitiesfrom currentdev593656f6. The replacement planning heads #517 and core #770 stay unchanged.The bounded correction keeps paired core for command, lint, contract and six-launcher smoke checks. The full suite selects its declared immutable core 0.55.4 through a step-scoped checkout, so its existing exact-version assertion remains unchanged. Smoke checks use the paired core's exact locked clean modules fixture. No dependency declaration, fixture verifier, signature gate, coverage gate, runtime implementation or protected assurance policy changes are included. Spec deltas and failing regression evidence precede the workflow correction.