Pre-v1 readiness foundation

[adirothbuilds]

Description

This PR clears the pre-1.0 readiness backlog except the final v1 RC gate (#133). It adds the public docs/policy surface, ADRs, maintainer and repository checklists, bounded property tests, local benchmark baseline artifacts, release integrity generation, and sequential free-tier friendly workflows.

Closes #144, #151, #152, #153, #154, #155, #156, #157, #158, #159, #160, #161, #162, #163, #164, #165, #166, #167, #168.

Type of Change

• bug - Bug fix; creates a patch release.
• feature - Feature or stabilization work intended for the current beta minor line; creates a patch release before 1.0.
• feature-minor - Real feature intended to advance the beta minor line; creates a minor release before 1.0.
• breaking - Breaking beta change; creates a minor release before 1.0.
• docs - Documentation-only change; no release.
• refactor - Non-functional cleanup or refactor; no release.
• test - Test-only change; no release.

What Changed

• Adds canonical docs ownership, ADRs, production/API/release/compatibility/roadmap docs, governance, dependency policy, vulnerability response, architecture/security boundary, logging operations, repository settings, CI policy, release runbook, and release verification pages.
• Replaces duplicated meta contributing content with a pointer and adds root CONTRIBUTING/SUPPORT entry points.
• Adds bounded Hypothesis property tests for protocol primitives, SSH messages, and SFTP message boundaries.
• Adds Docker-backed local benchmark baseline JSON artifact generation and a release integrity generator for hashes/SBOM-style artifact metadata.
• Restructures PR, compatibility, release, property, and benchmark workflows to reduce free-tier runner contention and run release gates sequentially.
• Moves release version bumps into protected release-version PRs and publishes only after that release PR is merged.

Repository Settings Applied

Outside this branch, repository settings were aligned with #152:

• Wiki disabled.
• Homepage set to https://spindlex.readthedocs.io/.
• Secret scanning enabled.

How Has This Been Tested?

• Unit Tests: .venv/bin/python -m pytest tests -m "not integration and not real_server and not slow and not performance" -q
• Unit Tests: .venv/bin/python -m pytest tests/protocol/test_property_protocol_boundaries.py tests/scripts/test_release_helpers.py tests/scripts/test_generate_release_integrity.py tests/scripts/test_track_workflow_failure.py -q
• Lint: .venv/bin/ruff check spindlex tests scripts
• Format: .venv/bin/ruff format --check spindlex tests scripts
• Type Check: .venv/bin/mypy spindlex
• Docs: .venv/bin/python -m mkdocs build --strict
• Workflow Lint: $HOME/go/bin/actionlint
• Script Compile: .venv/bin/python -m py_compile scripts/*.py
• Whitespace: git diff --check

Notes

The local benchmark script was smoke-invoked, but this machine's Docker daemon was not running, so the Docker-backed benchmark execution itself could not complete locally. The script now reports that failure clearly and is wired to run in GitHub Actions where Docker is available.

[codecov-commenter]

⚠️ Please install the to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 736e0c2a1d

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 3701294c3c

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".