Skip to content

chore(manifest): declare expertMonitors for fuzekeys-expert - #123

Merged
izzywdev merged 1 commit into
masterfrom
chore/expert-monitors
Aug 31, 2026
Merged

chore(manifest): declare expertMonitors for fuzekeys-expert#123
izzywdev merged 1 commit into
masterfrom
chore/expert-monitors

Conversation

@izzywdev

Copy link
Copy Markdown
Owner

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 — the pii-tokenizer/ LLM-data-path subsystem (Vault + Redis, tokenize-before-send invariant). It also documents the Helm-deployed MCP gateway driven by contracts/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's appVersion-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-nightly reads these paths and opens an auto-refresh PR on drift; publish-expert.yml's hint-expert-drift job nudges a PR comment when a PR touches one of them. No other file changed.

Co-Authored-By: Claude Opus 5 noreply@anthropic.com

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
@github-actions
github-actions Bot enabled auto-merge (squash) August 31, 2026 14:43
@codecov

codecov Bot commented Aug 31, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 41.06%. Comparing base (8362dd2) to head (52ff03a).

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           
Flag Coverage Δ
backend 41.06% <ø> (ø)
frontend 41.06% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@izzywdev
izzywdev merged commit 1f45983 into master Aug 31, 2026
31 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant