terraphim / terraphim/homebrew-terraphim
[MP5b] Repair and validate Terraphim formulas from release BOM
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 0
- Forks
- 0
- Avg merge
- 6h 10m
- Merged PRs (30d)
- 1
Description
Goal
Repair all Terraphim formulas from the signed release BOM and own the tap-native validation matrix.
Contract
- Consume generator output from
terraphim-aiMP5a; do not hand-edit versions or hashes independently. - Require non-empty 64-hex SHA-256 values matching exact
assets[]entries for server, agent, and grep on every advertised platform. - Install per-binary Homebrew receipts under each resolved formula prefix:
share/terraphim/package-manager.d/terraphim_servershare/terraphim/package-manager.d/terraphim-agentshare/terraphim/package-manager.d/terraphim-grep
- Formula changes arrive by PR/outbox after the central release; no direct atomic tap push is claimed.
Acceptance
brew audit --strictpasses.- macOS and Linuxbrew install, version, payload-hash, receipt, zero-updater-network/write, upgrade, and uninstall tests pass for advertised assets.
- Empty, stale, duplicate, wrong-platform, or mismatched hashes fail CI.
- Reprocessing the same manifest yields byte-identical formulas.
Depends on central staging/BOM work: https://git.terraphim.cloud/terraphim/terraphim-ai/issues/3336 and https://git.terraphim.cloud/terraphim/terraphim-ai/issues/3338. Generator/outbox: https://git.terraphim.cloud/terraphim/terraphim-ai/issues/3381.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the linked central staging/BOM issues and generator/outbox issue, then run brew audit --strict against the generated formulas. Check the three receipt paths named in the contract and validate the advertised assets against the acceptance matrix. Done means deterministic formulas and passing install, hash, receipt, updater, upgrade, and uninstall checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- build-system, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100