llm-mock-server 1.0.6 → 1.0.8

package/.desloppify/subagents/runs/20260315_185613/prompts/batch-7.md

@@ -1,94 +0,0 @@
-You are a focused subagent reviewer for a single holistic investigation batch.
-
-Repository root: /Users/suyash.x.srijan/Documents/Personal_Projects/llm-mock-server
-Blind packet: /Users/suyash.x.srijan/Documents/Personal_Projects/llm-mock-server/.desloppify/review_packet_blind.json
-Batch index: 7
-Batch name: Package Organization
-Batch dimensions: package_organization, high_level_elegance
-Batch rationale: file placement, directory boundaries, architectural layering
-
-Files assigned:
-- vitest.config.ts
-- src/cli-validators.ts
-- src/cli.ts
-- src/history.ts
-- test/cli-validators.test.ts
-- test/history.test.ts
-- test/loader.test.ts
-- src/formats/anthropic/index.ts
-- src/formats/anthropic/parse.ts
-- src/formats/anthropic/schema.ts
-- src/formats/request-helpers.ts
-- src/formats/serialize-helpers.ts
-- src/formats/openai/index.ts
-- src/formats/openai/parse.ts
-- src/formats/responses/index.ts
-- src/formats/responses/parse.ts
-
-Task requirements:
-1. Read the blind packet and follow `system_prompt` constraints exactly.
-1a. If previously flagged issues are listed above, use them as context for your review.
-    Verify whether each still applies to the current code. Do not re-report fixed or
-    wontfix issues. Use them as starting points to look deeper — inspect adjacent code
-    and related modules for defects the prior review may have missed.
-1c. Think structurally: when you spot multiple individual issues that share a common
-    root cause (missing abstraction, duplicated pattern, inconsistent convention),
-    explain the deeper structural issue in the finding, not just the surface symptom.
-    If the pattern is significant enough, report the structural issue as its own finding
-    with appropriate fix_scope ('multi_file_refactor' or 'architectural_change') and
-    use `root_cause_cluster` to connect related symptom findings together.
-2. Evaluate ONLY listed files and ONLY listed dimensions for this batch.
-3. Return 0-10 high-quality findings for this batch (empty array allowed).
-3a. Do not suppress real defects to keep scores high; report every material issue you can support with evidence.
-3b. Do not default to 100. Reserve 100 for genuinely exemplary evidence in this batch.
-4. Score/finding consistency is required: broader or more severe findings MUST lower dimension scores.
-4a. Any dimension scored below 85.0 MUST include explicit feedback: add at least one finding with the same `dimension` and a non-empty actionable `suggestion`.
-5. Every finding must include `related_files` with at least 2 files when possible.
-6. Every finding must include `dimension`, `identifier`, `summary`, `evidence`, `suggestion`, and `confidence`.
-7. Every finding must include `impact_scope` and `fix_scope`.
-8. Every scored dimension MUST include dimension_notes with concrete evidence.
-9. If a dimension score is >85.0, include `issues_preventing_higher_score` in dimension_notes.
-10. Use exactly one decimal place for every assessment and abstraction sub-axis score.
-9a. For package_organization, ground scoring in objective structure signals from `holistic_context.structure` (root_files fan_in/fan_out roles, directory_profiles, coupling_matrix). Prefer thresholded evidence (for example: fan_in < 5 for root stragglers, import-affinity > 60%, directories > 10 files with mixed concerns).
-9b. Suggestions must include a staged reorg plan (target folders, move order, and import-update/validation commands).
-11. Ignore prior chat context and any target-threshold assumptions.
-12. Do not edit repository files.
-13. Return ONLY valid JSON, no markdown fences.
-
-Scope enums:
-- impact_scope: "local" | "module" | "subsystem" | "codebase"
-- fix_scope: "single_edit" | "multi_file_refactor" | "architectural_change"
-
-Output schema:
-{
-  "batch": "Package Organization",
-  "batch_index": 7,
-  "assessments": {"<dimension>": <0-100 with one decimal place>},
-  "dimension_notes": {
-    "<dimension>": {
-      "evidence": ["specific code observations"],
-      "impact_scope": "local|module|subsystem|codebase",
-      "fix_scope": "single_edit|multi_file_refactor|architectural_change",
-      "confidence": "high|medium|low",
-      "issues_preventing_higher_score": "required when score >85.0",
-      "sub_axes": {"abstraction_leverage": 0-100 with one decimal place, "indirection_cost": 0-100 with one decimal place, "interface_honesty": 0-100 with one decimal place}  // required for abstraction_fitness when evidence supports it
-    }
-  },
-  "findings": [{
-    "dimension": "<dimension>",
-    "identifier": "short_id",
-    "summary": "one-line defect summary",
-    "related_files": ["relative/path.py"],
-    "evidence": ["specific code observation"],
-    "suggestion": "concrete fix recommendation",
-    "confidence": "high|medium|low",
-    "impact_scope": "local|module|subsystem|codebase",
-    "fix_scope": "single_edit|multi_file_refactor|architectural_change",
-    "root_cause_cluster": "optional_cluster_name_when_supported_by_history"
-  }],
-  "retrospective": {
-    "root_causes": ["optional: concise root-cause hypotheses"],
-    "likely_symptoms": ["optional: identifiers that look symptom-level"],
-    "possible_false_positives": ["optional: prior concept keys likely mis-scoped"]
-  }
-}

package/.desloppify/subagents/runs/20260315_185613/prompts/batch-8.md

@@ -1,84 +0,0 @@
-You are a focused subagent reviewer for a single holistic investigation batch.
-
-Repository root: /Users/suyash.x.srijan/Documents/Personal_Projects/llm-mock-server
-Blind packet: /Users/suyash.x.srijan/Documents/Personal_Projects/llm-mock-server/.desloppify/review_packet_blind.json
-Batch index: 8
-Batch name: Governance & Contracts
-Batch dimensions: cross_module_architecture, high_level_elegance, package_organization
-Batch rationale: architecture contracts, compatibility policy, docs-vs-runtime scope, and quality-gate coverage
-
-Files assigned:
-- README.md
-- src/types.ts
-- src/formats/types.ts
-- src/formats/request-helpers.ts
-- src/logger.ts
-- src/rule-engine.ts
-
-Task requirements:
-1. Read the blind packet and follow `system_prompt` constraints exactly.
-1a. If previously flagged issues are listed above, use them as context for your review.
-    Verify whether each still applies to the current code. Do not re-report fixed or
-    wontfix issues. Use them as starting points to look deeper — inspect adjacent code
-    and related modules for defects the prior review may have missed.
-1c. Think structurally: when you spot multiple individual issues that share a common
-    root cause (missing abstraction, duplicated pattern, inconsistent convention),
-    explain the deeper structural issue in the finding, not just the surface symptom.
-    If the pattern is significant enough, report the structural issue as its own finding
-    with appropriate fix_scope ('multi_file_refactor' or 'architectural_change') and
-    use `root_cause_cluster` to connect related symptom findings together.
-2. Evaluate ONLY listed files and ONLY listed dimensions for this batch.
-3. Return 0-10 high-quality findings for this batch (empty array allowed).
-3a. Do not suppress real defects to keep scores high; report every material issue you can support with evidence.
-3b. Do not default to 100. Reserve 100 for genuinely exemplary evidence in this batch.
-4. Score/finding consistency is required: broader or more severe findings MUST lower dimension scores.
-4a. Any dimension scored below 85.0 MUST include explicit feedback: add at least one finding with the same `dimension` and a non-empty actionable `suggestion`.
-5. Every finding must include `related_files` with at least 2 files when possible.
-6. Every finding must include `dimension`, `identifier`, `summary`, `evidence`, `suggestion`, and `confidence`.
-7. Every finding must include `impact_scope` and `fix_scope`.
-8. Every scored dimension MUST include dimension_notes with concrete evidence.
-9. If a dimension score is >85.0, include `issues_preventing_higher_score` in dimension_notes.
-10. Use exactly one decimal place for every assessment and abstraction sub-axis score.
-9a. For package_organization, ground scoring in objective structure signals from `holistic_context.structure` (root_files fan_in/fan_out roles, directory_profiles, coupling_matrix). Prefer thresholded evidence (for example: fan_in < 5 for root stragglers, import-affinity > 60%, directories > 10 files with mixed concerns).
-9b. Suggestions must include a staged reorg plan (target folders, move order, and import-update/validation commands).
-11. Ignore prior chat context and any target-threshold assumptions.
-12. Do not edit repository files.
-13. Return ONLY valid JSON, no markdown fences.
-
-Scope enums:
-- impact_scope: "local" | "module" | "subsystem" | "codebase"
-- fix_scope: "single_edit" | "multi_file_refactor" | "architectural_change"
-
-Output schema:
-{
-  "batch": "Governance & Contracts",
-  "batch_index": 8,
-  "assessments": {"<dimension>": <0-100 with one decimal place>},
-  "dimension_notes": {
-    "<dimension>": {
-      "evidence": ["specific code observations"],
-      "impact_scope": "local|module|subsystem|codebase",
-      "fix_scope": "single_edit|multi_file_refactor|architectural_change",
-      "confidence": "high|medium|low",
-      "issues_preventing_higher_score": "required when score >85.0",
-      "sub_axes": {"abstraction_leverage": 0-100 with one decimal place, "indirection_cost": 0-100 with one decimal place, "interface_honesty": 0-100 with one decimal place}  // required for abstraction_fitness when evidence supports it
-    }
-  },
-  "findings": [{
-    "dimension": "<dimension>",
-    "identifier": "short_id",
-    "summary": "one-line defect summary",
-    "related_files": ["relative/path.py"],
-    "evidence": ["specific code observation"],
-    "suggestion": "concrete fix recommendation",
-    "confidence": "high|medium|low",
-    "impact_scope": "local|module|subsystem|codebase",
-    "fix_scope": "single_edit|multi_file_refactor|architectural_change",
-    "root_cause_cluster": "optional_cluster_name_when_supported_by_history"
-  }],
-  "retrospective": {
-    "root_causes": ["optional: concise root-cause hypotheses"],
-    "likely_symptoms": ["optional: identifiers that look symptom-level"],
-    "possible_false_positives": ["optional: prior concept keys likely mis-scoped"]
-  }
-}

package/.desloppify/subagents/runs/20260315_185613/prompts/batch-9.md

@@ -1,112 +0,0 @@
-You are a focused subagent reviewer for a single holistic investigation batch.
-
-Repository root: /Users/suyash.x.srijan/Documents/Personal_Projects/llm-mock-server
-Blind packet: /Users/suyash.x.srijan/Documents/Personal_Projects/llm-mock-server/.desloppify/review_packet_blind.json
-Batch index: 9
-Batch name: Cross-cutting Sweep
-Batch dimensions: design_coherence
-Batch rationale: selected dimensions had no direct batch mapping; review representative cross-cutting files
-
-Files assigned:
-- src/types.ts
-- src/formats/types.ts
-- src/formats/request-helpers.ts
-- src/logger.ts
-- src/rule-engine.ts
-- src/history.ts
-- test/history.test.ts
-- src/cli.ts
-- src/formats/anthropic/schema.ts
-- src/formats/openai/schema.ts
-- src/formats/responses/schema.ts
-- src/types/request.ts
-- test/helpers/make-req.ts
-- test/cli-validators.test.ts
-- test/mock-server.test.ts
-- test/rule-engine.test.ts
-- src/cli-validators.ts
-- src/mock-server.ts
-- test/formats/anthropic.test.ts
-- src/formats/responses/serialize.ts
-- test/formats/responses.test.ts
-- src/loader.ts
-- test/formats/openai.test.ts
-- test/loader.test.ts
-- test/logger.test.ts
-- src/formats/openai/serialize.ts
-- src/types/rule.ts
-- vitest.config.ts
-- src/formats/anthropic/index.ts
-- src/formats/anthropic/parse.ts
-- src/formats/serialize-helpers.ts
-- src/formats/openai/index.ts
-- src/formats/openai/parse.ts
-- src/formats/responses/index.ts
-- src/formats/responses/parse.ts
-- README.md
-
-Task requirements:
-1. Read the blind packet and follow `system_prompt` constraints exactly.
-1a. If previously flagged issues are listed above, use them as context for your review.
-    Verify whether each still applies to the current code. Do not re-report fixed or
-    wontfix issues. Use them as starting points to look deeper — inspect adjacent code
-    and related modules for defects the prior review may have missed.
-1c. Think structurally: when you spot multiple individual issues that share a common
-    root cause (missing abstraction, duplicated pattern, inconsistent convention),
-    explain the deeper structural issue in the finding, not just the surface symptom.
-    If the pattern is significant enough, report the structural issue as its own finding
-    with appropriate fix_scope ('multi_file_refactor' or 'architectural_change') and
-    use `root_cause_cluster` to connect related symptom findings together.
-2. Evaluate ONLY listed files and ONLY listed dimensions for this batch.
-3. Return 0-10 high-quality findings for this batch (empty array allowed).
-3a. Do not suppress real defects to keep scores high; report every material issue you can support with evidence.
-3b. Do not default to 100. Reserve 100 for genuinely exemplary evidence in this batch.
-4. Score/finding consistency is required: broader or more severe findings MUST lower dimension scores.
-4a. Any dimension scored below 85.0 MUST include explicit feedback: add at least one finding with the same `dimension` and a non-empty actionable `suggestion`.
-5. Every finding must include `related_files` with at least 2 files when possible.
-6. Every finding must include `dimension`, `identifier`, `summary`, `evidence`, `suggestion`, and `confidence`.
-7. Every finding must include `impact_scope` and `fix_scope`.
-8. Every scored dimension MUST include dimension_notes with concrete evidence.
-9. If a dimension score is >85.0, include `issues_preventing_higher_score` in dimension_notes.
-10. Use exactly one decimal place for every assessment and abstraction sub-axis score.
-11. Ignore prior chat context and any target-threshold assumptions.
-12. Do not edit repository files.
-13. Return ONLY valid JSON, no markdown fences.
-
-Scope enums:
-- impact_scope: "local" | "module" | "subsystem" | "codebase"
-- fix_scope: "single_edit" | "multi_file_refactor" | "architectural_change"
-
-Output schema:
-{
-  "batch": "Cross-cutting Sweep",
-  "batch_index": 9,
-  "assessments": {"<dimension>": <0-100 with one decimal place>},
-  "dimension_notes": {
-    "<dimension>": {
-      "evidence": ["specific code observations"],
-      "impact_scope": "local|module|subsystem|codebase",
-      "fix_scope": "single_edit|multi_file_refactor|architectural_change",
-      "confidence": "high|medium|low",
-      "issues_preventing_higher_score": "required when score >85.0",
-      "sub_axes": {"abstraction_leverage": 0-100 with one decimal place, "indirection_cost": 0-100 with one decimal place, "interface_honesty": 0-100 with one decimal place}  // required for abstraction_fitness when evidence supports it
-    }
-  },
-  "findings": [{
-    "dimension": "<dimension>",
-    "identifier": "short_id",
-    "summary": "one-line defect summary",
-    "related_files": ["relative/path.py"],
-    "evidence": ["specific code observation"],
-    "suggestion": "concrete fix recommendation",
-    "confidence": "high|medium|low",
-    "impact_scope": "local|module|subsystem|codebase",
-    "fix_scope": "single_edit|multi_file_refactor|architectural_change",
-    "root_cause_cluster": "optional_cluster_name_when_supported_by_history"
-  }],
-  "retrospective": {
-    "root_causes": ["optional: concise root-cause hypotheses"],
-    "likely_symptoms": ["optional: identifiers that look symptom-level"],
-    "possible_false_positives": ["optional: prior concept keys likely mis-scoped"]
-  }
-}

package/.desloppify/subagents/runs/20260315_185613/results/batch-1.raw.txt

@@ -1,78 +0,0 @@
-{
-  "batch": "Architecture & Coupling",
-  "batch_index": 1,
-  "assessments": {
-    "cross_module_architecture": 82.0,
-    "high_level_elegance": 84.0
-  },
-  "dimension_notes": {
-    "cross_module_architecture": {
-      "evidence": [
-        "src/types.ts is a barrel that re-exports request/reply/rule types, and internal modules like src/rule-engine.ts and src/formats/request-helpers.ts import from \"./types.js\"/\"../types.js\" instead of their domain-specific type files.",
-        "The root types barrel becomes a dependency hub for unrelated modules, increasing blast radius for type changes across domains."
-      ],
-      "impact_scope": "subsystem",
-      "fix_scope": "multi_file_refactor",
-      "confidence": "high"
-    },
-    "high_level_elegance": {
-      "evidence": [
-        "src/formats/types.ts (format contracts) imports RequestMeta from src/formats/request-helpers.ts, coupling a contract type to a helper/logic module.",
-        "src/formats/request-helpers.ts mixes RequestMeta with buildMockRequest and parsing helpers, blurring ownership of the format boundary types."
-      ],
-      "impact_scope": "module",
-      "fix_scope": "multi_file_refactor",
-      "confidence": "high"
-    }
-  },
-  "findings": [
-    {
-      "dimension": "cross_module_architecture",
-      "identifier": "types_barrel_hub",
-      "summary": "Root types barrel creates a dependency hub and obscures domain boundaries.",
-      "related_files": [
-        "src/types.ts",
-        "src/rule-engine.ts",
-        "src/formats/request-helpers.ts"
-      ],
-      "evidence": [
-        "src/types.ts only re-exports from ./types/request.js, ./types/reply.js, ./types/rule.js.",
-        "src/rule-engine.ts and src/formats/request-helpers.ts import shared types from \"./types.js\"/\"../types.js\" rather than domain-specific type files."
-      ],
-      "suggestion": "Prefer direct imports from domain type files (e.g., src/types/request.ts) for internal modules, or split into domain-specific entry points and reserve src/types.ts for external/public API use.",
-      "confidence": "high",
-      "impact_scope": "subsystem",
-      "fix_scope": "multi_file_refactor",
-      "root_cause_cluster": "type_barrel_hub"
-    },
-    {
-      "dimension": "high_level_elegance",
-      "identifier": "request_meta_in_helper",
-      "summary": "Format contract depends on helper module, blurring ownership of request boundary types.",
-      "related_files": [
-        "src/formats/types.ts",
-        "src/formats/request-helpers.ts"
-      ],
-      "evidence": [
-        "src/formats/types.ts imports RequestMeta from ./request-helpers.js.",
-        "src/formats/request-helpers.ts combines RequestMeta with buildMockRequest and isStreaming logic."
-      ],
-      "suggestion": "Move RequestMeta into a dedicated types module (e.g., src/formats/request-types.ts) or into src/formats/types.ts, and have request-helpers import it instead of defining it.",
-      "confidence": "high",
-      "impact_scope": "module",
-      "fix_scope": "multi_file_refactor",
-      "root_cause_cluster": "types_helpers_boundary_blur"
-    }
-  ],
-  "retrospective": {
-    "root_causes": [
-      "Centralized barrel exports used for internal imports create hidden coupling between domains.",
-      "Type definitions colocated with helper logic blur boundary ownership."
-    ],
-    "likely_symptoms": [
-      "types_barrel_hub",
-      "request_meta_in_helper"
-    ],
-    "possible_false_positives": []
-  }
-}

package/.desloppify/subagents/runs/20260315_185613/results/batch-10.raw.txt

@@ -1,242 +0,0 @@
-{
-  "batch": "Full Codebase Sweep",
-  "batch_index": 10,
-  "assessments": {
-    "cross_module_architecture": 90.0,
-    "convention_outlier": 92.0,
-    "error_consistency": 82.0,
-    "abstraction_fitness": 88.0,
-    "api_surface_coherence": 89.0,
-    "authorization_consistency": 95.0,
-    "ai_generated_debt": 93.0,
-    "incomplete_migration": 97.0,
-    "package_organization": 82.0,
-    "high_level_elegance": 88.0,
-    "mid_level_elegance": 86.0,
-    "low_level_elegance": 84.0,
-    "design_coherence": 87.0
-  },
-  "dimension_notes": {
-    "cross_module_architecture": {
-      "evidence": [
-        "Core types are centralized via `src/types.ts` and imported widely; this creates a hub module with broad blast radius for changes.",
-        "Formats depend on shared helpers in `src/formats/request-helpers.ts` and `src/formats/serialize-helpers.ts`, keeping boundary direction mostly consistent."
-      ],
-      "impact_scope": "subsystem",
-      "fix_scope": "multi_file_refactor",
-      "confidence": "medium",
-      "issues_preventing_higher_score": "The type hub in `src/types.ts` concentrates change impact and could be split by concern if the surface grows further."
-    },
-    "convention_outlier": {
-      "evidence": [
-        "Format packages follow a consistent `index/parse/schema/serialize` pattern across `src/formats/*`.",
-        "Top-level `src/` mixes executable entry points, server runtime, and utilities in one directory, which is consistent but raises organization concerns rather than convention drift."
-      ],
-      "impact_scope": "module",
-      "fix_scope": "single_edit",
-      "confidence": "low",
-      "issues_preventing_higher_score": "The repository largely follows consistent naming and export patterns; remaining issues are about placement rather than conventions."
-    },
-    "error_consistency": {
-      "evidence": [
-        "Resolver exceptions in `src/route-handler.ts` are caught and converted into a normal fallback reply, returning HTTP 200 without an error payload.",
-        "In `src/formats/responses/parse.ts`, malformed tool entries are silently dropped via `safeParse`, while `src/formats/openai/parse.ts` and `src/formats/anthropic/parse.ts` hard-fail on schema validation."
-      ],
-      "impact_scope": "subsystem",
-      "fix_scope": "multi_file_refactor",
-      "confidence": "high"
-    },
-    "abstraction_fitness": {
-      "evidence": [
-        "The `Format` interface in `src/formats/types.ts` is implemented three times with small per-format differences, so the abstraction is useful but only minimally polymorphic.",
-        "`createRouteHandler` in `src/route-handler.ts` bundles parsing, matching, logging, and streaming in one function, suggesting boundary abstractions are only partially leveraged."
-      ],
-      "impact_scope": "module",
-      "fix_scope": "multi_file_refactor",
-      "confidence": "medium",
-      "issues_preventing_higher_score": "Some abstractions are thin wrappers with limited leverage outside the current three formats.",
-      "sub_axes": {
-        "abstraction_leverage": 86.0,
-        "indirection_cost": 88.0,
-        "interface_honesty": 90.0
-      }
-    },
-    "api_surface_coherence": {
-      "evidence": [
-        "`src/cli-validators.ts` exposes both sync and async parsers (`parseHost` is async, others are sync), which makes the module’s API shape uneven.",
-        "The server surface is small and consistent (single `MockServer` entry point plus `createMock`)."
-      ],
-      "impact_scope": "local",
-      "fix_scope": "single_edit",
-      "confidence": "medium",
-      "issues_preventing_higher_score": "Mixed async/sync validators in a single module create minor API irregularity for consumers."
-    },
-    "authorization_consistency": {
-      "evidence": [
-        "The only route handler is created in `src/mock-server.ts` and has no auth checks, indicating a fully public mock server."
-      ],
-      "impact_scope": "module",
-      "fix_scope": "single_edit",
-      "confidence": "low",
-      "issues_preventing_higher_score": "Auth posture is implicit rather than explicit; there is no in-code signal that the endpoints are intentionally unauthenticated."
-    },
-    "ai_generated_debt": {
-      "evidence": [
-        "Comment ratio is high in `src/types/request.ts` and `src/types/rule.ts` compared with the codebase average, suggesting some doc-comment bulk.",
-        "Comments mostly describe semantics and appear purposeful rather than restating code."
-      ],
-      "impact_scope": "local",
-      "fix_scope": "single_edit",
-      "confidence": "low",
-      "issues_preventing_higher_score": "Comment density in the types layer is higher than typical and could become noise if it grows further."
-    },
-    "incomplete_migration": {
-      "evidence": [
-        "No deprecated markers or migration TODOs appear in the reviewed production files.",
-        "No mixed JS/TS implementations exist for the same module in the reviewed set."
-      ],
-      "impact_scope": "local",
-      "fix_scope": "single_edit",
-      "confidence": "high",
-      "issues_preventing_higher_score": "No explicit migration scaffolding is visible; score held below 100 only due to limited evidence scope."
-    },
-    "package_organization": {
-      "evidence": [
-        "`src/` contains 11 mixed-concern files (cli, server runtime, loader, logger, rule engine), exceeding the >10 file flat-directory threshold.",
-        "`src/` avg fan-in is 3.8 and coupling shows bidirectional edges between `src/` and `src/formats/`, suggesting responsibilities are not strongly separated."
-      ],
-      "impact_scope": "codebase",
-      "fix_scope": "architectural_change",
-      "confidence": "high"
-    },
-    "high_level_elegance": {
-      "evidence": [
-        "Primary domain concepts (formats, server, rules) are clear, but are all housed in a flat `src/` root alongside CLI utilities.",
-        "The public API surface in `src/index.ts` is concise but coupled to internal layout."
-      ],
-      "impact_scope": "subsystem",
-      "fix_scope": "multi_file_refactor",
-      "confidence": "medium",
-      "issues_preventing_higher_score": "Top-level decomposition would read cleaner if CLI/runtime utilities were separated from core server and rule-engine concerns."
-    },
-    "mid_level_elegance": {
-      "evidence": [
-        "`createRouteHandler` orchestrates parsing, matching, error handling, logging, and streaming directly, making handoffs between layers less explicit.",
-        "Format-specific parsing and serialization are cleanly separated, reducing translation friction."
-      ],
-      "impact_scope": "module",
-      "fix_scope": "multi_file_refactor",
-      "confidence": "medium",
-      "issues_preventing_higher_score": "Integration seams are mostly predictable but could be clearer with narrower handler responsibilities."
-    },
-    "low_level_elegance": {
-      "evidence": [
-        "ID generation in `src/formats/serialize-helpers.ts` uses `Date.now()` without collision avoidance, which can produce duplicate IDs under same-millisecond calls."
-      ],
-      "impact_scope": "subsystem",
-      "fix_scope": "single_edit",
-      "confidence": "high"
-    },
-    "design_coherence": {
-      "evidence": [
-        "`createRouteHandler` bundles multiple responsibilities (parsing, matching, metrics/logging, response mode selection), which could be separated for clearer intent.",
-        "Helper modules under `src/formats/` are focused and coherent."
-      ],
-      "impact_scope": "module",
-      "fix_scope": "multi_file_refactor",
-      "confidence": "medium",
-      "issues_preventing_higher_score": "Some core control flow aggregates multiple responsibilities in one function, reducing separation of concerns."
-    }
-  },
-  "findings": [
-    {
-      "dimension": "error_consistency",
-      "identifier": "resolver_errors_swallowed",
-      "summary": "Resolver exceptions are swallowed and returned as normal fallback replies",
-      "related_files": [
-        "src/route-handler.ts",
-        "src/types/reply.ts",
-        "src/mock-server.ts"
-      ],
-      "evidence": [
-        "`resolveReply` catches resolver errors and returns `normalizeReply(fallback)` with no error signal.",
-        "Downstream in the handler, the fallback reply is serialized as a normal 200 response if it doesn’t set `error`."
-      ],
-      "suggestion": "Surface resolver failures explicitly: either rethrow and let Fastify return 500, or translate to `ReplyObject.error` with a 5xx status. Update `resolveReply` and `createRouteHandler` to propagate an error reply, and document the error contract in `src/types/reply.ts`.",
-      "confidence": "high",
-      "impact_scope": "subsystem",
-      "fix_scope": "multi_file_refactor",
-      "root_cause_cluster": "error_handling_policy"
-    },
-    {
-      "dimension": "error_consistency",
-      "identifier": "responses_tools_silent_drop",
-      "summary": "Responses tool parsing silently drops invalid tools unlike other formats",
-      "related_files": [
-        "src/formats/responses/parse.ts",
-        "src/formats/openai/parse.ts",
-        "src/formats/anthropic/parse.ts"
-      ],
-      "evidence": [
-        "`parseTools` in responses uses `FunctionToolSchema.safeParse` and filters out failed parses, so malformed tool entries are ignored.",
-        "OpenAI and Anthropic requests rely on schema parsing that fails the whole request on invalid structures."
-      ],
-      "suggestion": "Align tool-validation behavior across formats: either treat invalid tools as a request error for responses, or document and apply a consistent “best-effort” policy across all formats. Prefer failing the request for invalid tools to keep error handling predictable.",
-      "confidence": "medium",
-      "impact_scope": "module",
-      "fix_scope": "multi_file_refactor",
-      "root_cause_cluster": "error_handling_policy"
-    },
-    {
-      "dimension": "low_level_elegance",
-      "identifier": "non_unique_ids",
-      "summary": "ID generation relies on Date.now(), risking collisions under concurrency",
-      "related_files": [
-        "src/formats/serialize-helpers.ts",
-        "src/formats/openai/serialize.ts",
-        "src/formats/responses/serialize.ts"
-      ],
-      "evidence": [
-        "`genId` and `toolId` use `Date.now().toString(36)` which can repeat in the same millisecond.",
-        "Streaming serializers call these helpers multiple times per request, and concurrent requests can produce duplicate IDs."
-      ],
-      "suggestion": "Switch to a collision-resistant ID source (e.g., `crypto.randomUUID()` or a process-wide monotonic counter with a random prefix). Update `genId`/`toolId` and regenerate IDs in the serializers to avoid duplicate response IDs.",
-      "confidence": "high",
-      "impact_scope": "subsystem",
-      "fix_scope": "single_edit"
-    },
-    {
-      "dimension": "package_organization",
-      "identifier": "flat_src_mixed_concerns",
-      "summary": "Flat `src/` directory mixes CLI, server, and rule-engine concerns",
-      "related_files": [
-        "src/cli.ts",
-        "src/mock-server.ts",
-        "src/route-handler.ts",
-        "src/loader.ts"
-      ],
-      "evidence": [
-        "`src/` contains 11 files across CLI, HTTP server, rule engine, logging, and utilities (directory profile shows `file_count: 11`).",
-        "Coupling shows bidirectional edges between `src/` and `src/formats/`, indicating blurred boundaries at the top level."
-      ],
-      "suggestion": "Stage a reorg to clarify ownership: 1) create `src/server/` and move `mock-server.ts`, `route-handler.ts`, `sse-writer.ts`; 2) create `src/cli/` and move `cli.ts`, `cli-validators.ts`; 3) create `src/core/` (or `src/rules/`) and move `rule-engine.ts`, `loader.ts`, `history.ts`, `logger.ts`; 4) update imports and `src/index.ts` exports; 5) run `npm test` or `vitest` to validate and adjust any path-based tooling.",
-      "confidence": "high",
-      "impact_scope": "codebase",
-      "fix_scope": "architectural_change"
-    }
-  ],
-  "retrospective": {
-    "root_causes": [
-      "Error handling policy is inconsistent across request parsing, resolver execution, and tool validation paths.",
-      "Top-level `src/` is serving as a catch-all for multiple concerns, suggesting missing package boundaries."
-    ],
-    "likely_symptoms": [
-      "resolver_errors_swallowed",
-      "responses_tools_silent_drop",
-      "flat_src_mixed_concerns"
-    ],
-    "possible_false_positives": [
-      "non_unique_ids"
-    ]
-  }
-}