Skip to content

fix(ci): FIXES PREEXISTING CI FAILURES IN MAIN — hypothesis dep + dead docs link#128

Open
cryptoxdog wants to merge 1 commit into
mainfrom
fix/ci-baseline-residuals
Open

fix(ci): FIXES PREEXISTING CI FAILURES IN MAIN — hypothesis dep + dead docs link#128
cryptoxdog wants to merge 1 commit into
mainfrom
fix/ci-baseline-residuals

Conversation

@cryptoxdog

Copy link
Copy Markdown
Collaborator

FIXES PREEXISTING CI FAILURES IN MAIN

Tightly scoped follow-on to the #125/#126 CI-foundation remediation. Two one-line fixes for content defects that exist on main today and were exposed once the CI gates began running and enforcing. Neither defect was introduced by #125/#126; both were deliberately excluded from those PRs' transactional file allowlists.

Fix 1 — Contract Enforcement: missing hypothesis dependency

  • Symptom: ModuleNotFoundError: No module named 'hypothesis' while collecting tests/property/test_gates_property.py and tests/property/test_scoring_property.py.
  • Root cause: hypothesis is declared only in the Poetry dev group of pyproject.toml (^6.100.0), but CI installs via pip install -r requirements-ci.txt -r requirements.txt, neither of which lists it. The property tests have existed since PR feat: Wave 5 — Correctness Tooling & Verification (seL4 proof infrastructure) #64; the gate simply never ran until its trigger was fixed.
  • Fix: add hypothesis>=6.100,<7 to the Testing section of requirements-ci.txt (matches the existing pyproject.toml constraint — no resolver conflict).

Fix 2 — Docs-Code Sync: dead link in docs/DEPLOYMENT.md

  • Symptom: "Check Markdown Links" fails on docs/DEPLOYMENT.md:157../iac/README.md.
  • Root cause: no iac/ directory exists in the repository; the link references infrastructure-as-code content that was never committed.
  • Fix: remove the dead "Infrastructure as Code" list item. The two sibling links (docker-compose.prod.yml, Dockerfile.prod) were verified to resolve and are kept.

Verification performed

Check Result
pip install -r requirements-ci.txt -r requirements.txt (CI-equivalent) clean
PYTHONPATH=. pytest tests/property/ -q 11 passed
Relative-link check over docs/**/*.md (mirrors Docs-Code Sync step) 0 broken links

Scope

2 files, +1/-1 lines. No runtime code touched. Diagnosis context: combo-audit finding CL-011 (truthful CI baseline / CEG-00 scope).

- Add hypothesis>=6.100,<7 to requirements-ci.txt: tests/property/ requires
  hypothesis, declared only in the Poetry dev group; CI installs via
  requirements files, so Contract Enforcement test collection fails on main.
- Remove dead link docs/DEPLOYMENT.md -> ../iac/README.md (no iac/ directory
  exists), which fails Docs-Code Sync 'Check Markdown Links' on main.

Both defects pre-date the PR #125/#126 CI-foundation remediation and were
exposed once the gates began running. Verified locally: tests/property/
passes (11 tests), docs relative-link check clean.
@cursor

cursor Bot commented Jul 22, 2026

Copy link
Copy Markdown

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

@github-actions

Copy link
Copy Markdown

PR size is within recommended limits

Copy link
Copy Markdown
Collaborator Author

CI status note (remediator): this branch is cut from main, so its checks run main's pre-remediation workflow definitions. Every failing check here reproduces a defect that already exists on main and is fixed on the #125/#126 branches (lint findings, docs-code-sync.yml:85 ${link./} bad-substitution crash, PacketEnvelope/terminology and Cypher-sanitization content violations). The Test Suite job — the gate this PR's hypothesis fix targets — was skipped because upstream needs: jobs failed first; it was verified locally instead (tests/property/ 11 passed with pip install -r requirements-ci.txt -r requirements.txt).

Merge-order dependency: land #125#126 first (or merge their workflow fixes to main), then this PR's checks will exercise the fixed gates and go green. This PR intentionally stays 2 files / +1−1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant