critical System graph security Secrets conf 1.00 Possible secret in README.md

Detected pattern matching generic_api_key. Rotate the credential and move to a secret manager.

README.md:179

high System graph security Agent instructions conf 1.00 Agent instruction/config may expose a secret: .claude/commands/check-health.md

Agent-facing files are routinely pasted into LLM/tool contexts. Move literal tokens, keys, and passwords into a secret manager or document them as placeholders only.

.claude/commands/check-health.md:22 SecretsClaude instruction

high System graph security Agent instructions conf 1.00 Agent instruction/config may expose a secret: .claude/skills/re-lease-count/SKILL.md

Agent-facing files are routinely pasted into LLM/tool contexts. Move literal tokens, keys, and passwords into a secret manager or document them as placeholders only.

.claude/skills/re-lease-count/SKILL.md:44 SecretsClaude instruction

high System graph quality Integrity conf 1.00 Blocking `requests.post(...)` inside `async def ocr_financial` — api/routers/ocr.py:99

Sync I/O inside an async function blocks the event loop. While `requests.post(...)` is running, *all* other coroutines on this loop are paused — silent throughput collapse under concurrency. Use the async equivalent (`httpx.AsyncClient`, `asyncio.sleep`, `aiofiles`) or wrap with `await asyncio.to_t…

api/routers/ocr.py:99 Sync io in asyncPerformance

high System graph security auth conf 1.00 FastAPI DELETE `delete_case_record` without auth dependency — mobile_app/api.py:1361

`@router.delete` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.

mobile_app/api.py:1361 securityAuth fastapi unauth mutation

high System graph security auth conf 1.00 FastAPI PATCH `update_case_result` without auth dependency — mobile_app/api.py:1344

`@router.patch` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.

mobile_app/api.py:1344 securityAuth fastapi unauth mutation

high System graph security auth conf 1.00 FastAPI POST `advisor_strategy` without auth dependency — mobile_app/api.py:1367

`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.

mobile_app/api.py:1367 securityAuth fastapi unauth mutation

high System graph security auth conf 1.00 FastAPI POST `chat` without auth dependency — mobile_app/api.py:1399

`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.

mobile_app/api.py:1399 securityAuth fastapi unauth mutation

high System graph security auth conf 1.00 FastAPI POST `forecast` without auth dependency — backend.py:200

`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.

backend.py:200 securityAuth fastapi unauth mutation

high System graph security auth conf 1.00 FastAPI POST `gunshi_stream_proxy` without auth dependency — mobile_app/api.py:1430

`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.

mobile_app/api.py:1430 securityAuth fastapi unauth mutation

high System graph security auth conf 1.00 FastAPI POST `ocr_financial` without auth dependency — api/routers/ocr.py:66

`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.

api/routers/ocr.py:66 securityAuth fastapi unauth mutation

high System graph security auth conf 1.00 FastAPI POST `predict` without auth dependency — mobile_app/api.py:924

`@router.post` decorator with no `Depends(get_current_user)` or auth-shaped dependency in its signature. Mutating endpoints should require authentication unless explicitly public.

mobile_app/api.py:924 securityAuth fastapi unauth mutation

high System graph security auth conf 1.00 Flask mutation route `result` without `@login_required` — web/app.py:91

Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.

web/app.py:91 securityAuth flask unauth route

high System graph security security conf 1.00 Insecure pattern 'eval_used' in .claude/skills/security-and-hardening/SKILL.md:50

Found a known-risky pattern (eval_used). Review and replace if possible.

.claude/skills/security-and-hardening/SKILL.md:50 Eval used

high System graph security security conf 1.00 Insecure pattern 'eval_used' in pydeps/numpy/distutils/misc_util.py:157

Found a known-risky pattern (eval_used). Review and replace if possible.

pydeps/numpy/distutils/misc_util.py:157 Eval used

high System graph security security conf 1.00 Insecure pattern 'eval_used' in pydeps/numpy/f2py/auxfuncs.py:607

Found a known-risky pattern (eval_used). Review and replace if possible.

pydeps/numpy/f2py/auxfuncs.py:607 Eval used

high System graph security security conf 1.00 Insecure pattern 'eval_used' in pydeps/numpy/f2py/capi_maps.py:157

Found a known-risky pattern (eval_used). Review and replace if possible.

pydeps/numpy/f2py/capi_maps.py:157 Eval used

high System graph security security conf 1.00 Insecure pattern 'eval_used' in pydeps/numpy/ma/timer_comparison.py:442

Found a known-risky pattern (eval_used). Review and replace if possible.

pydeps/numpy/ma/timer_comparison.py:442 Eval used

high System graph security security conf 1.00 Insecure pattern 'tls_verify_false' in pydeps/numpy/core/fromnumeric.py:3832

Found a known-risky pattern (tls_verify_false). Review and replace if possible.

pydeps/numpy/core/fromnumeric.py:3832 Tls verify false

high System graph security security conf 1.00 Insecure pattern 'tls_verify_false' in pydeps/numpy/core/multiarray.py:82

Found a known-risky pattern (tls_verify_false). Review and replace if possible.

pydeps/numpy/core/multiarray.py:82 Tls verify false

high System graph security security conf 1.00 Insecure pattern 'tls_verify_false' in pydeps/numpy/lib/ufunclike.py:18

Found a known-risky pattern (tls_verify_false). Review and replace if possible.

pydeps/numpy/lib/ufunclike.py:18 Tls verify false

medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — frontend/src/components/analysis/GunshiAdvice.tsx:857

Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html

Fq dangerous html

medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — frontend/src/components/analysis/ReportGenerator.tsx:150

Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html

Fq dangerous html

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — frontend/src/components/analysis/RealGraphs.tsx:58

Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.

runtime safetyRobustness

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — mobile_app/sw.js:38

Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.

runtime safetyRobustness

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/agents/security-checker.md

This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.

.claude/agents/security-checker.md VerificationClaude instruction

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/commands/analyze-logs.md

This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.

.claude/commands/analyze-logs.md VerificationClaude instruction

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/commands/analyze-variables.md

This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.

.claude/commands/analyze-variables.md VerificationClaude instruction

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/commands/asset-evaluation.md

This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.

.claude/commands/asset-evaluation.md VerificationClaude instruction

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/commands/audit-scores.md

This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.

.claude/commands/audit-scores.md VerificationClaude instruction

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/commands/batch-export.md

This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.

.claude/commands/batch-export.md VerificationClaude instruction

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/commands/build-check.md

This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.

.claude/commands/build-check.md VerificationClaude instruction

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/commands/case-similarity.md

This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.

.claude/commands/case-similarity.md VerificationClaude instruction

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/commands/check-data.md

This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.

.claude/commands/check-data.md VerificationClaude instruction

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/commands/check-health.md

This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.

.claude/commands/check-health.md VerificationClaude instruction

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/commands/explain-score.md

This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.

.claude/commands/explain-score.md VerificationClaude instruction

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/commands/financial-forecast.md

This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.

.claude/commands/financial-forecast.md VerificationClaude instruction

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/commands/generate-industry-brief.md

This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.

.claude/commands/generate-industry-brief.md VerificationClaude instruction

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/commands/generate-report.md

This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.

.claude/commands/generate-report.md VerificationClaude instruction

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/commands/optimize-coefficients.md

This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.

.claude/commands/optimize-coefficients.md VerificationClaude instruction

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/commands/quick-score.md

This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.

.claude/commands/quick-score.md VerificationClaude instruction

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/commands/validate-rules.md

This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.

.claude/commands/validate-rules.md VerificationClaude instruction

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/launch.json

This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.

.claude/launch.json VerificationClaude instruction

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/rules/workflow.md

This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.

.claude/rules/workflow.md VerificationClaude instruction

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/git-ship/SKILL.md

This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.

.claude/skills/git-ship/SKILL.md VerificationClaude instruction

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/skills/restart-api/SKILL.md

This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.

.claude/skills/restart-api/SKILL.md VerificationClaude instruction

medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data

A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.

Mock dataCritical flowGenerated repo pattern

medium System graph cicd CI/CD security conf 1.00 GitHub Actions workflow grants broad write permissions

CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.

.github/workflows/ledger-sync.yml CI/CD securitySupply chainGithub actions

medium System graph security security conf 1.00 Insecure pattern 'cors_wildcard' in backend.py:39

Found a known-risky pattern (cors_wildcard). Review and replace if possible.

backend.py:39 Cors wildcard

medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in frontend/src/components/analysis/GunshiAdvice.tsx:857

Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.

frontend/src/components/analysis/GunshiAdvice.tsx:857 Dangerous innerhtml

medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in frontend/src/components/analysis/ReportGenerator.tsx:150

Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.

frontend/src/components/analysis/ReportGenerator.tsx:150 Dangerous innerhtml

medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in scripts/lease_system_gap_analyzer.py:265

Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.

scripts/lease_system_gap_analyzer.py:265 Dangerous innerhtml

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in .claude/skills/security-and-hardening/SKILL.md:97

Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.

.claude/skills/security-and-hardening/SKILL.md:97 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in frontend/src/app/similar/page.tsx:134

Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.

frontend/src/app/similar/page.tsx:134 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in mobile_app/index.html:1599

Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.

mobile_app/index.html:1599 Direct innerhtml assignment

medium System graph security security conf 1.00 Insecure pattern 'subprocess_shell_true' in pydeps/numpy/distutils/lib2def.py:62

Found a known-risky pattern (subprocess_shell_true). Review and replace if possible.

pydeps/numpy/distutils/lib2def.py:62 Subprocess shell true

medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — check_integrity.py:234

`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.

runtime safetyRobustness

medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — components/mahalanobis_3d.py:140

`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.

runtime safetyRobustness

medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — lease_intelligence_consultation.py:190

`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.

runtime safetyRobustness

medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — mahalanobis_ui.py:46

`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.

runtime safetyRobustness

medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — pydeps/numpy/distutils/command/config.py:474

`subprocess.check_output(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.

runtime safetyRobustness

medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — pydeps/numpy/distutils/exec_command.py:283

`subprocess.Popen(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.

runtime safetyRobustness

medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — pydeps/numpy/distutils/lib2def.py:66

`subprocess.Popen(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.

runtime safetyRobustness

medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — pydeps/numpy/distutils/mingw32ccompiler.py:221

`subprocess.check_output(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.

runtime safetyRobustness

medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — pydeps/numpy/distutils/misc_util.py:418

`subprocess.check_output(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.

runtime safetyRobustness

medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — pydeps/numpy/distutils/unixccompiler.py:66

`subprocess.check_output(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.

runtime safetyRobustness

medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — pydeps/numpy/f2py/_backends/_meson.py:167

`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.

runtime safetyRobustness

medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/apply_recipe.py:42

`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.

runtime safetyRobustness

medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/dispatch_log_to_obsidian.py:103

`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.

runtime safetyRobustness

medium System graph security Coverage conf 1.00 No auth library detected

The scanner did not find any standard auth library (JWT, OAuth, NextAuth, Auth0, etc.). The repo has auth/admin/session surface indicators, so auth may live in custom code, in a separate service, or be missing.

auth

medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected

Found 221 placeholder/mock markers across 70 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.

Mock dataIncompleteGenerated repo pattern

low System graph frontend Frontend quality conf 1.00 "active" state uses light bg in a dark theme — frontend/src/app/knowledge-space/page.tsx:1253

A ternary like `active ? 'bg-white' : '...'` (or bg-gray-100/200) on a dark theme produces jarring white pills. Use a dark-emphasized active state instead — border + ring or slightly brighter dark bg. Example: `active ? 'bg-gray-800 border-gray-500 ring-1 ring-blue-500/30' : '…'`. Why: P-E in CHEC…

Fq active light bg

low System graph quality Maintenance conf 1.00 207 TODO/FIXME markers

High count of TODO/FIXME/HACK markers — track them as issues so they're not forgotten.

low System graph quality Integrity conf 1.00 76 env vars used in code but missing from .env.example

Drift between code and config docs. The first few: `ABSOFT`, `ACCELERATE`, `ADVISOR_ENGINE`, `AI_ENGINE`, `ANYTHING_LLM_WORKSPACE`, `APPROVAL_LINE`, `ATLAS_VERSION`, `AURION_HOLD_SECONDS` + 68 more. Add them (with a placeholder/comment) to .env.example so onboarding doesn't break.

config drift

low System graph hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found

Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.

Deployment

low System graph quality Debug conf 1.00 Debug logging residue appears in source files

Found 1516 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.

CleanupRepo hardeningGenerated repo pattern

low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: node:20-bookworm-slim

Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.

Dockerfile:2 containersPinned dependencies

low System graph hardware Supply chain conf 1.00 2 occurrences Docker base image is tag-pinned but not digest-pinned: python:3.11-slim-bookworm

Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.

lines 12, 23

Dockerfile:12, 23 (2 hits)

containersPinned dependencies

low System graph security security conf 1.00 Insecure pattern 'debug_true' in pydeps/numpy/distutils/mingw32ccompiler.py:67

Found a known-risky pattern (debug_true). Review and replace if possible.

pydeps/numpy/distutils/mingw32ccompiler.py:67 Debug true

low System graph security security conf 1.00 Insecure pattern 'debug_true' in web/app.py:200

Found a known-risky pattern (debug_true). Review and replace if possible.

web/app.py:200 Debug true

low System graph quality Integrity conf 1.00 15 occurrences Near-duplicate function bodies in 2 places

Functions with the same first-5-line body hash: lease_logic_sumaho8.py:load_json_data, _archive/lease_logic_sumaho11.py:load_json_data This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why they're separate.

15 occurrences

repo-level (15 hits)

duplicatesduplication

low System graph quality Integrity conf 1.00 5 occurrences Near-duplicate function bodies in 3 places

Functions with the same first-5-line body hash: lease_logic_sumaho8.py:red_label, lease_logic_sumaho12.py:red_label, _archive/lease_logic_sumaho11.py:red_label This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document…

5 occurrences

repo-level (5 hits)

duplicatesduplication

low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `_build_shinsa_agent_prompt_v2` in components/agent_team.py:1546

Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.

old markerDead code

low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `_character_bc_old` in pydeps/numpy/f2py/tests/test_character.py:497

Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.

old markerDead code

low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `_sv_session_copy` in components/analysis_results.py:1046

Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.

old markerDead code

low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `_vr_session_copy` in components/agent_hub.py:1562

Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.

old markerDead code

low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `a_copy` in pydeps/numpy/core/tests/test_ufunc.py:1726

Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.

old markerDead code

low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `a_copy` in pydeps/numpy/lib/tests/test_function_base.py:258

Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.

old markerDead code

low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `arr_copy` in pydeps/numpy/core/tests/test_item_selection.py:113

Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.

old markerDead code

low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `ary_copy` in pydeps/numpy/core/_internal.py:428

Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.

old markerDead code

low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `assert_deprecated` in pydeps/numpy/core/tests/test_deprecations.py:52

Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.

old markerDead code

low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `is_deprecated` in pydeps/numpy/lib/tests/test__datasource.py:342

Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.

old markerDead code

low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `isintent_copy` in pydeps/numpy/f2py/auxfuncs.py:33

Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.

old markerDead code

low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `isintent_copy` in pydeps/numpy/f2py/rules.py:66

Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.

old markerDead code

low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `lbl_v1` in flet_aurion_wave.py:130

Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.

old markerDead code

low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `manual_auto_comment_v2` in components/ai_consultation.py:247

Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.

old markerDead code

low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `no_copy` in pydeps/numpy/core/tests/test_indexing.py:873

Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.

old markerDead code

low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `obj_copy` in pydeps/numpy/f2py/tests/test_array_from_pyobj.py:272

Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.

old markerDead code

low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `obsidian_backup` in scripts/check_system_health.py:88

Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.

old markerDead code

low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `OverriddenArrayOld` in pydeps/numpy/core/tests/test_umath.py:3609

Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.

old markerDead code

low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `plotly_3d_v1` in _archive/lease_logic_sumaho11.py:3369

Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.

old markerDead code

low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `pw_old` in auth_logic.py:239

Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.

old markerDead code

low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `removed_old` in scripts/backup_case_data.py:60

Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.

old markerDead code

low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `render_sidebar_backup` in components/sidebar.py:240

Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.

old markerDead code

low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `res_backup` in api/scoring_full.py:220

Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.

old markerDead code

low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `rf_new_customer_v1` in mobile_app/api.py:6

Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.

old markerDead code

low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `run_backup` in api/main.py:2755

Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.

old markerDead code

low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `run_backup` in backup_manager.py:32

Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.

old markerDead code

low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `run_backup` in components/batch_scoring.py:804

Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.

old markerDead code

low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `spread_predictor_v2` in frontend/src/app/help/page.tsx:298

Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.

old markerDead code

low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `spread_predictor_v2` in retraining_pipeline.py:63

Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.

old markerDead code

low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `spread_predictor_v2` in tests/spec_phase4/test_P4-003.py:123

Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.

old markerDead code

low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `test_asarray_copy` in pydeps/numpy/array_api/tests/test_creation_functions.py:40

Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.

old markerDead code

low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `test_copy` in pydeps/numpy/core/tests/test_multiarray.py:2257

Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.

old markerDead code

low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `test_copy` in pydeps/numpy/ma/tests/test_core.py:399

Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.

old markerDead code

low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `test_copy` in pydeps/numpy/polynomial/tests/test_classes.py:420

Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.

old markerDead code

low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `test_copy` in pydeps/numpy/polynomial/tests/test_polynomial.py:46

Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.

old markerDead code

low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `test_copy` in pydeps/numpy/polynomial/tests/test_symbol.py:155

Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.

old markerDead code

low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `test_deprecated` in pydeps/numpy/core/tests/test_array_coercion.py:843

Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.

old markerDead code

low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `test_drop_metadata_identity_and_copy` in pydeps/numpy/lib/tests/test_utils.py:222

Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.

old markerDead code

low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `test_iter_copy` in pydeps/numpy/core/tests/test_nditer.py:1347

Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.

old markerDead code

low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `test_random_integers_deprecated` in pydeps/numpy/random/tests/test_random.py:351

Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.

old markerDead code

low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `test_random_integers_deprecated` in pydeps/numpy/random/tests/test_randomstate.py:539

Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.

old markerDead code

low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `test_recarray_copy` in pydeps/numpy/core/tests/test_regression.py:561

Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.

old markerDead code

low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `test_rerank_prefers_curated_knowledge_over_news_and_sync_copy` in tests/test_knowledge_vector_store_rerank.py:17

Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.

old markerDead code

low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `test_reshape_copy` in pydeps/numpy/array_api/tests/test_manipulation_functions.py:25

Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.

old markerDead code

low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `test_returns_copy` in pydeps/numpy/core/tests/test_shape_base.py:229

Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.

old markerDead code

low System graph software Dead code conf 1.00 Possibly dead Python function: build_graph_context_for_prompt

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

novel_graph.py:555

low System graph software Dead code conf 1.00 Possibly dead Python function: collect_from_arxiv_async

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

mathematician_agent.py:1218

low System graph software Dead code conf 1.00 Possibly dead Python function: draw_header

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

screening_report.py:490

low System graph software Dead code conf 1.00 Possibly dead Python function: extract_improvement_suggestions

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

agent_crosstalk.py:408

low System graph software Dead code conf 1.00 Possibly dead Python function: find_item_by_code

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

expected_usage_period.py:72

low System graph software Dead code conf 1.00 Possibly dead Python function: generate_agent_crosstalk

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

agent_crosstalk.py:141

low System graph software Dead code conf 1.00 Possibly dead Python function: load_improvement_suggestions

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

agent_crosstalk.py:518

low System graph software Dead code conf 1.00 Possibly dead Python function: plot_benchmark_comparison

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

lease_logic_sumaho8.py:2050

low System graph software Dead code conf 1.00 Possibly dead Python function: plot_indicators_bar

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

lease_logic_sumaho8.py:2358

low System graph software Dead code conf 1.00 Possibly dead Python function: red_label

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

lease_logic_sumaho8.py:59

low System graph software Dead code conf 1.00 Possibly dead Python function: render_gunshi

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

shinsa_gunshi_ui.py:115

low System graph software Dead code conf 1.00 Possibly dead Python function: run_experiment_bayesian

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

mathematician_agent.py:510

low System graph software Dead code conf 1.00 Possibly dead Python function: run_experiment_granger

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

mathematician_agent.py:771

low System graph software Dead code conf 1.00 Possibly dead Python function: run_experiment_kalman

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

mathematician_agent.py:572

low System graph software Dead code conf 1.00 Possibly dead Python function: run_experiment_maxent

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

mathematician_agent.py:821

low System graph software Dead code conf 1.00 Possibly dead Python function: run_experiment_power_law

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

mathematician_agent.py:723

low System graph software Dead code conf 1.00 Possibly dead Python function: run_experiment_prospect_theory

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

mathematician_agent.py:626

low System graph software Dead code conf 1.00 Possibly dead Python function: run_experiment_survival

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

mathematician_agent.py:676

low System graph software Dead code conf 1.00 Possibly dead Python function: run_weekly_cycle_async

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

mathematician_agent.py:1170

low System graph quality Provenance conf 1.00 Shallow git history limits provenance confidence

The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.

Git historyGenerated repo pattern

low System graph quality Integrity conf 1.00 Stub function `domain` (body is just `pass`/`return`) — pydeps/numpy/polynomial/_polybase.py:116

Likely an AI scaffold that was never filled in. Remove or implement.

Empty handlerDead code

low System graph quality Integrity conf 1.00 Stub function `example` (body is just `pass`/`return`) — pydeps/numpy/_utils/__init__.py:20

Likely an AI scaffold that was never filled in. Remove or implement.

Empty handlerDead code

low System graph quality Integrity conf 1.00 Stub function `find_executables` (body is just `pass`/`return`) — pydeps/numpy/distutils/fcompiler/none.py:21

Likely an AI scaffold that was never filled in. Remove or implement.

Empty handlerDead code

low System graph quality Integrity conf 1.00 Stub function `find_executables` (body is just `pass`/`return`) — pydeps/numpy/distutils/fcompiler/vast.py:30

Likely an AI scaffold that was never filled in. Remove or implement.

Empty handlerDead code

low System graph quality Integrity conf 1.00 Stub function `local` (body is just `pass`/`return`) — pydeps/numpy/_utils/_pep440.py:186

Likely an AI scaffold that was never filled in. Remove or implement.

Empty handlerDead code

low System graph quality Integrity conf 1.00 Stub function `nop` (body is just `pass`/`return`) — pydeps/numpy/testing/_private/utils.py:1262

Likely an AI scaffold that was never filled in. Remove or implement.

Empty handlerDead code

low System graph api Wiring conf 1.00 Unused endpoint: DELETE /api/cases/operation/clear-all

`api/main.py` declares `DELETE /api/cases/operation/clear-all` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: DELETE /api/cases/{case_id}

`api/main.py` declares `DELETE /api/cases/{case_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /

`api/main.py` declares `GET /` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /api/analysis/contract_drivers

`api/main.py` declares `GET /api/analysis/contract_drivers` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /api/analysis/quantitative

`api/main.py` declares `GET /api/analysis/quantitative` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /api/asset/useful-life-all

`api/main.py` declares `GET /api/asset/useful-life-all` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /api/asset/useful-life-search

`api/main.py` declares `GET /api/asset/useful-life-search` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /api/batch/template

`api/main.py` declares `GET /api/batch/template` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /api/cases

`api/main.py` declares `GET /api/cases` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /api/cases/industry-winrate

`api/main.py` declares `GET /api/cases/industry-winrate` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /api/cases/pending

`api/main.py` declares `GET /api/cases/pending` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /api/cases/sales-dept-winrate

`api/main.py` declares `GET /api/cases/sales-dept-winrate` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /api/cases/{case_id}

`api/main.py` declares `GET /api/cases/{case_id}` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /api/dashboard/stats

`api/main.py` declares `GET /api/dashboard/stats` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /api/department/stats

`api/main.py` declares `GET /api/department/stats` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /api/improvement-pipeline/summary

`api/main.py` declares `GET /api/improvement-pipeline/summary` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /api/industry/stats

`api/main.py` declares `GET /api/industry/stats` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /api/knowledge/graph

`api/main.py` declares `GET /api/knowledge/graph` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /api/lease-news/brief

`api/main.py` declares `GET /api/lease-news/brief` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /api/lease-news/focus

`api/main.py` declares `GET /api/lease-news/focus` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /api/lease-system-gaps

`api/main.py` declares `GET /api/lease-system-gaps` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /api/payment/alerts

`api/main.py` declares `GET /api/payment/alerts` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /api/settings/corporate_number

`api/main.py` declares `GET /api/settings/corporate_number` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /api/similar/data

`api/main.py` declares `GET /api/similar/data` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /api/subsidies

`api/main.py` declares `GET /api/subsidies` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: GET /api/visual/data

`api/main.py` declares `GET /api/visual/data` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: PATCH /api/cases/{case_id}/result

`api/main.py` declares `PATCH /api/cases/{case_id}/result` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /api/analysis/qualitative

`api/main.py` declares `POST /api/analysis/qualitative` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /api/asset-finance/evaluate

`api/main.py` declares `POST /api/asset-finance/evaluate` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /api/asset-finance/obsidian-context

`api/main.py` declares `POST /api/asset-finance/obsidian-context` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /api/asset-finance/save-to-obsidian

`api/main.py` declares `POST /api/asset-finance/save-to-obsidian` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /api/asset-finance/similar-notes

`api/main.py` declares `POST /api/asset-finance/similar-notes` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /api/batch/save

`api/main.py` declares `POST /api/batch/save` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /api/batch/score

`api/main.py` declares `POST /api/batch/score` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /api/deal/closure-probability

`api/main.py` declares `POST /api/deal/closure-probability` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /api/forecast

`api/main.py` declares `POST /api/forecast` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /api/gunshi/advise

`api/main.py` declares `POST /api/gunshi/advise` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /api/improvement-log/dismiss

`api/main.py` declares `POST /api/improvement-log/dismiss` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /api/improvement-log/review

`api/main.py` declares `POST /api/improvement-log/review` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /api/industry/suggest

`api/main.py` declares `POST /api/industry/suggest` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /api/prompt-feedback/rules/register

`api/main.py` declares `POST /api/prompt-feedback/rules/register` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /api/score/calculate

`api/main.py` declares `POST /api/score/calculate` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /api/score/full

`api/main.py` declares `POST /api/score/full` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /api/settings/corporate_number

`api/main.py` declares `POST /api/settings/corporate_number` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /api/similar/inline

`api/main.py` declares `POST /api/similar/inline` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /api/timesfm/base_rate

`api/main.py` declares `POST /api/timesfm/base_rate` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /api/timesfm/base_rate_all

`api/main.py` declares `POST /api/timesfm/base_rate_all` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /api/timesfm/company_score

`api/main.py` declares `POST /api/timesfm/company_score` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /api/timesfm/final_rate

`api/main.py` declares `POST /api/timesfm/final_rate` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph api Wiring conf 1.00 Unused endpoint: POST /forecast

`backend.py` declares `POST /forecast` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

Unused endpoint

low System graph quality Complexity conf 1.00 Very large file: _archive/lease_logic_sumaho11.py (4805 lines)