Add .fips-template.yaml manifests for agent-loop and workflow#162
Merged
Conversation
Declares which paths in each template are template-managed (offered as patches by `fips-agents patch`) and which belong to the user. The CLI reads this file from the comparison root after cloning, before computing drift in `fips-agents patch check`. Both manifests carry the same categories the CLI currently has hardcoded for agent / workflow project types (chart, docs, build, claude, evals) plus the never_patch list, with two adjustments the CLI fallback misses: - `build` includes `.containerignore` and `.gitignore`. Both ship in the templates and are template-managed; without the manifest, changes to them never surface in `patch check`. Loader behavior is described in fips-agents/fips-agents-cli#45 — when a manifest is absent, malformed, or declares an unsupported schema_version, the CLI falls back to its built-in category set, so this change is non-breaking for older CLI installs. Assisted-by: Claude Code (Opus 4.7)
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.
Companion PR to fips-agents/fips-agents-cli#48 (the CLI loader). After both merge, drift in this template's files surfaces in `fips-agents patch check` without needing a CLI release — the manifest is the source of truth.
What
Adds `.fips-template.yaml` at:
Both manifests declare `schema_version: 1` and a `patch:` block with five categories — `chart`, `docs`, `build`, `claude`, `evals` — plus a 16-entry `never_patch` list separating template-managed files from user-authored ones.
What changes vs. the CLI's hardcoded fallback
The categories largely mirror the CLI's `AGENT_FILE_CATEGORIES` constants, with two intentional additions to `build`:
Everything else matches the constants 1-to-1 (after fips-agents/fips-agents-cli#43 + #46 land).
Compatibility
Older CLI installs that don't know about `.fips-template.yaml` will simply ignore the file — nothing breaks. The CLI loader (fips-agents/fips-agents-cli#48) falls back to its hardcoded categories when the manifest is absent, malformed, or uses an unknown `schema_version`. So this PR is safe to land before, after, or independently of the CLI PR stack.
Test plan