feat(bin): add fleet usage harvester and harden launch permission posture - #1
Merged
Merged
Conversation
The mkdir that ensures data/ exists ran after the tmp-file write that already needs data/ to exist, so under set -e it could never protect a first harvest on a home whose data/ dir was absent. Move it ahead of the write.
…e spawn launch comments
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fork PR — validated via kunchenguid#3298
This opens the fleet usage harvester on the npayette84/firstmate fork (base
main) because the upstream PR kunchenguid#3298 targets a repository where merge rights are unavailable. kunchenguid#3298 stays open as the validated original.The branch head here is identical to kunchenguid#3298's validated head, which passed the full no-mistakes pipeline: automated review, tests, lint, and green CI (including a Greptile review round). Against this fork's
main, the diff is harvester-only — the launch-permission hardening named in the reused title is already present on this fork'smain, so it does not reappear in this diff.What it adds
bin/fm-usage-harvest.sh— appends exactly one JSON usage-ledger row per finished task; single owner of the ledger line schema.bin/fm-usage-report.sh— plain-text reader that consumes that ledger.bin/fm-teardown.sh— best-effort harvest hook that never blocks teardown.See kunchenguid#3298 for the complete validated intent and pipeline history.