feat(release): add deployment manifest commands

[Shubhank-Jonnada]

Closes #61

Depends on no other pipeline PR and should merge first.

Summary

• add release-plan for safe manual selection by repository path
• add release-changes to select only new integrations or integrations whose semantic version increased from a supplied Git commit
• emit schema 3 manifests with release kind, current and previous commit SHAs, workflow provenance, repository path, package type, byte size, and SHA-256
• use the top-level integration folder as the durable repository identity and reject deprecated source_id configuration
• enforce autohive-integrations-sdk>=1.0.2 during packaging, including --skip-validate
• retain explicit preserve, zip, and container package-type requests

Flow

flowchart LR
  A[Previous master SHA] --> B[release-changes]
  C[Current checkout] --> B
  B --> D{New path or version bump?}
  D -->|No| E[No release]
  D -->|Yes| F[Selected repository paths]
  F --> G[Package with SDK floor]
  G --> H[Schema 3 SHA-256 manifest]

Loading

Testing

• uv run pytest -q (180 passed, 18 skipped)
• changed source and test lint passed with Ruff
• real package smoke test produced and verified a 295-entry archive containing autohive_integrations_sdk
• release-changes selected only microsoft365 for the latest version-bump range in the integrations repository

Rollout

1. Merge this PR.
2. Publish immutable HiveUp tag 2.5.0 from the merge commit.
3. Replace the temporary branch reference in integrations PR #441 with 2.5.0.

[Shubhank-Jonnada]

@codex review

[chatgpt-codex-connector]

To use Codex here, create a Codex account and connect to github.

[autohive-ai-beta]

Verdict	Errors	Warnings	Suggestions
Reviewed	0	1	0

Reviewed

Summary

PR adds hiveup release-plan/release-manifest commands and a new release.py module that resolves a safe integration selection and writes a checksummed deployment manifest with GitHub provenance; version bumped to 2.5.0 throughout. Static review of the diff and the checked-out repo found the logic sound overall (path/identity validation, duplicate detection, and safe selection resolution all check out), but dynamic test execution wasn't possible because pip install -e . failed offline on the private autohive-integrations-sdk dependency, so tests/test_release.py could not be run in this environment.

Observations

• Both new CLI commands only catch ReleaseManifestError (cli.py lines ~310, ~344); any other exception raised from release.py (e.g. a nonexistent --repository-root, which raises FileNotFoundError from iterdir()) will surface as a raw Python traceback instead of the clean, exit-code-2 error UX the rest of the command demonstrates. Consider validating/normalizing inputs earlier or widening the except clause at the CLI boundary.

---

Review powered by Autohive

[TheRealAgentK]

Approved. No blocking correctness findings in the release selection, manifest generation, SDK-floor enforcement, packaging, or version-bump changes. Verified the reviewed head with 217 passing tooling tests and all five companion workflow-selection tests. The history-recovery finding on integrations PR #441 belongs to that workflow and does not block this tooling PR.