chore(manifest): declare expertMonitors for fuzekeys-expert - #123
Merged
Conversation
Points governance-nightly drift detection at the split-stack paths the expert claims (FastAPI backend, React frontend, the PII Tokenizer LLM data-path, Alembic migrations, the Helm chart, and the OpenAPI contract) so a change there nudges/refreshes the expert instead of rotting silently. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session-Id: fe3aa738-cb24-4315-a29b-29834ddea892
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #123 +/- ##
=======================================
Coverage 41.06% 41.06%
=======================================
Files 81 81
Lines 6171 6171
Branches 250 252 +2
=======================================
Hits 2534 2534
Misses 3634 3634
Partials 3 3
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
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
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.
Why these paths
fuzekeys-expert(.claude/agents/fuzekeys-expert.md) describes FuzeKeys as a split-stack product: a Python/FastAPI + SQLAlchemy/Alembic backend, a React/TS frontend, and — most security-sensitive — thepii-tokenizer/LLM-data-path subsystem (Vault + Redis, tokenize-before-send invariant). It also documents the Helm-deployed MCP gateway driven bycontracts/openapi.yaml.Declared
expertMonitors, each tied to a specific claim in the expert doc:backend/— the FastAPI app, SQLAlchemy models, encryption/master-key boundaries the expert calls "load-bearing."frontend/— the React/TS/Tailwind client.pii-tokenizer/— the tokenize-before-send + Vault-encryption subsystem the expert flags as "the part to handle most carefully."backend/alembic/versions/— the DB migration history backing the SQLAlchemy models.deploy/helm/fuzekeys/— the chart Argo syncs (deployOnPush: true); the expert'sappVersion-bump / release-version-gate claims hinge on this.contracts/openapi.yaml— the spec that both the mcp-gateway pod and the mcp-maintainer agent validate against.These are the paths whose drift would make the expert's architecture claims wrong; not declared because they don't exist under the layout this repo actually uses (verified via
gh api repos/izzywdev/FuzeKeys/contents).What this does
governance-nightlyreads these paths and opens an auto-refresh PR on drift;publish-expert.yml'shint-expert-driftjob nudges a PR comment when a PR touches one of them. No other file changed.Co-Authored-By: Claude Opus 5 noreply@anthropic.com