Skip to content

Tracking: Operational Hardening #8

@Delqhi

Description

@Delqhi

Umbrella tracking issue for the operational-hardening plan (see docs/plans/operational-hardening.md, added in #7). No new features — CI, release, packaging, and consistency work.

Workstreams

  • WS1 — Continuous Integration (per repo): .github/workflows/ci.yml on push/PR, Python 3.11/3.12/3.13 matrix, pip install -e . + pytest -q, green check required to merge.
  • WS2 — Lint & format gate: adopt ruff (shared config) via dev extra, add ruff check . + ruff format --check . CI job, fix violations per repo.
  • WS3 — Release & packaging: release.yml on tag v* building sdist+wheel via python -m build; verify pyproject.toml metadata; document SemVer policy. (depends on WS1)
  • WS4 — Cross-repo consistency check: scripts/check_consistency.py in Bundle asserting version/CLI/MCP-tool parity; wire into CI (warn → block). (depends on WS1)
  • WS5 — Dev bootstrap: scripts/dev_install.sh + scripts/run_all_tests.sh for two-command fresh setup + test. (depends on WS1)

Sequencing: WS1 & WS2 land first in parallel per repo; WS3/WS4/WS5 follow.

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentationdxenhancementNew feature or request

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions