llm-mock-server 1.0.6 → 1.0.7

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

@@ -1,102 +0,0 @@
-{
-  "batch": "Conventions & Errors",
-  "batch_index": 2,
-  "assessments": {
-    "convention_outlier": 86.0,
-    "error_consistency": 84.0,
-    "mid_level_elegance": 90.0
-  },
-  "dimension_notes": {
-    "convention_outlier": {
-      "evidence": [
-        "Log level naming diverges: `LEVEL_PRIORITY` exposes `warning` while the logger API uses `warn`, and CLI validation only accepts `warning` (src/logger.ts, src/cli-validators.ts, src/cli.ts).",
-        "Validator API mixes sync and async parsing in the same module: `parseHost` is async while other `parse*` helpers are sync, making call sites and tests use different interaction patterns (src/cli-validators.ts, test/cli-validators.test.ts)."
-      ],
-      "impact_scope": "module",
-      "fix_scope": "multi_file_refactor",
-      "confidence": "medium",
-      "issues_preventing_higher_score": "Conventions around log-level naming and validator async/sync shape are inconsistent within the CLI surface."
-    },
-    "error_consistency": {
-      "evidence": [
-        "Rules reload path resets server state before load and then only logs on failure, leaving the server running with cleared rules if reload fails (src/cli.ts, src/logger.ts)."
-      ],
-      "impact_scope": "module",
-      "fix_scope": "multi_file_refactor",
-      "confidence": "medium"
-    },
-    "mid_level_elegance": {
-      "evidence": [
-        "CLI start-up output bypasses the Logger and writes directly to `console.log`, while runtime events use Logger formatting and filtering (src/cli.ts, src/logger.ts)."
-      ],
-      "impact_scope": "module",
-      "fix_scope": "single_edit",
-      "confidence": "low",
-      "issues_preventing_higher_score": "Startup logging is routed through a different seam than the rest of runtime logging, making log formatting and filtering inconsistent."
-    }
-  },
-  "findings": [
-    {
-      "dimension": "convention_outlier",
-      "identifier": "log_level_naming_mismatch",
-      "summary": "Log level naming is inconsistent (`warning` vs `warn`) across CLI and Logger APIs.",
-      "related_files": [
-        "src/logger.ts",
-        "src/cli-validators.ts",
-        "src/cli.ts"
-      ],
-      "evidence": [
-        "`LEVEL_PRIORITY` defines `warning`, CLI validation only accepts `warning`, but Logger exposes `warn` and labels logs as `WARN` (src/logger.ts, src/cli-validators.ts).",
-        "CLI flag `--log-level` is the public surface; a user seeing `WARN` may reasonably try `warn`, which is rejected (src/cli.ts, src/cli-validators.ts)."
-      ],
-      "suggestion": "Align on one string (`warn` or `warning`) and accept both in the validator to preserve compatibility; update logger constants and CLI help text accordingly.",
-      "confidence": "medium",
-      "impact_scope": "module",
-      "fix_scope": "multi_file_refactor"
-    },
-    {
-      "dimension": "convention_outlier",
-      "identifier": "mixed_sync_async_parsers",
-      "summary": "CLI validators mix async and sync parsing styles, creating an API shape outlier.",
-      "related_files": [
-        "src/cli-validators.ts",
-        "test/cli-validators.test.ts"
-      ],
-      "evidence": [
-        "`parseHost` is async (DNS lookup) while `parsePort`, `parseLogLevel`, `parseChunkSize`, and `parseLatency` are sync, so consumers must treat the module inconsistently (src/cli-validators.ts).",
-        "Tests reflect the split by mixing `await expect(parseHost(...))` with sync expectations for other parsers (test/cli-validators.test.ts)."
-      ],
-      "suggestion": "Normalize the validator interface: either make all parsers async (returning Promises) or provide a sync `parseHostSync` and move the async lookup to the CLI entrypoint.",
-      "confidence": "low",
-      "impact_scope": "module",
-      "fix_scope": "multi_file_refactor"
-    },
-    {
-      "dimension": "error_consistency",
-      "identifier": "reload_rules_clears_on_error",
-      "summary": "Rules reload clears existing rules before load, and on failure only logs, leaving a running server with no rules.",
-      "related_files": [
-        "src/cli.ts",
-        "src/logger.ts"
-      ],
-      "evidence": [
-        "Watch reload path does `server.reset(); await server.load(rulesPath);` inside a try/catch and only logs on error (src/cli.ts).",
-        "If `server.load` throws, prior rules are already cleared and the server continues running with an empty rule set, with no rollback (src/cli.ts)."
-      ],
-      "suggestion": "Load into a temporary ruleset or only call `reset()` after a successful load; on failure, preserve the previous rules and log the error with context.",
-      "confidence": "medium",
-      "impact_scope": "module",
-      "fix_scope": "multi_file_refactor"
-    }
-  ],
-  "retrospective": {
-    "root_causes": [
-      "Public CLI surface does not have a single authoritative source for naming and error-handling conventions."
-    ],
-    "likely_symptoms": [
-      "log_level_naming_mismatch",
-      "mixed_sync_async_parsers"
-    ],
-    "possible_false_positives": []
-  }
-}

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

@@ -1,94 +0,0 @@
-{
-  "batch": "Abstractions & Dependencies",
-  "batch_index": 3,
-  "assessments": {
-    "abstraction_fitness": 82.0,
-    "mid_level_elegance": 84.0,
-    "low_level_elegance": 88.0
-  },
-  "dimension_notes": {
-    "abstraction_fitness": {
-      "evidence": [
-        "src/mock-server.ts builds sequence rules inline in when().replySequence(), including mapping entries and calling createSequenceResolver, then sets rule.remaining.",
-        "src/loader.ts repeats near-identical sequence rule wiring in addSequenceRule(), including entry mapping, createSequenceResolver, and rule.remaining."
-      ],
-      "impact_scope": "module",
-      "fix_scope": "multi_file_refactor",
-      "confidence": "high",
-      "issues_preventing_higher_score": "Sequence-rule construction is duplicated in two modules, making future option/behavior changes easy to miss in one path.",
-      "sub_axes": {
-        "abstraction_leverage": 79.0,
-        "indirection_cost": 84.0,
-        "interface_honesty": 83.0
-      }
-    },
-    "mid_level_elegance": {
-      "evidence": [
-        "src/mock-server.ts registers routes from the formats array (openaiFormat/anthropicFormat/responsesFormat) and relies on each format’s route.",
-        "src/cli.ts prints a hard-coded endpoints string instead of deriving from the same formats registry."
-      ],
-      "impact_scope": "module",
-      "fix_scope": "multi_file_refactor",
-      "confidence": "medium",
-      "issues_preventing_higher_score": "Endpoint listing is a manual seam between CLI output and runtime route registration, which can drift when adding/removing formats."
-    },
-    "low_level_elegance": {
-      "evidence": [
-        "src/formats/responses/serialize.ts serialize() mixes header creation, block construction, chunk flattening, and response finalization in one dense function.",
-        "src/formats/openai/serialize.ts serialize() builds text/tool chunks, finish/usage chunks, and envelopes inline without local extraction."
-      ],
-      "impact_scope": "local",
-      "fix_scope": "single_edit",
-      "confidence": "medium",
-      "issues_preventing_higher_score": "Serialization functions are readable but locally dense; small extractions would make the control flow more intention-revealing."
-    }
-  },
-  "findings": [
-    {
-      "dimension": "abstraction_fitness",
-      "identifier": "sequence_rule_duplication",
-      "summary": "Sequence rule construction is duplicated across MockServer and loader, risking drift.",
-      "related_files": [
-        "src/mock-server.ts",
-        "src/loader.ts",
-        "src/rule-engine.ts"
-      ],
-      "evidence": [
-        "src/mock-server.ts when().replySequence() maps entries, calls createSequenceResolver, mutates rule.resolve and rule.remaining.",
-        "src/loader.ts addSequenceRule() performs the same mapping/resolve/remaining steps with a slightly different entry shape."
-      ],
-      "suggestion": "Extract a shared helper (e.g., in src/rule-engine.ts) that accepts normalized sequence steps and applies createSequenceResolver + remaining, then reuse it from both MockServer and loader.",
-      "confidence": "high",
-      "impact_scope": "module",
-      "fix_scope": "multi_file_refactor",
-      "root_cause_cluster": "sequence_rule_duplication"
-    },
-    {
-      "dimension": "mid_level_elegance",
-      "identifier": "format_registry_split",
-      "summary": "CLI hard-codes endpoints while MockServer derives routes from format modules.",
-      "related_files": [
-        "src/mock-server.ts",
-        "src/cli.ts"
-      ],
-      "evidence": [
-        "src/mock-server.ts registers routes by iterating formats[] with per-format route values.",
-        "src/cli.ts prints a static endpoints list string that must be updated manually."
-      ],
-      "suggestion": "Expose a single formats registry (or route list) and have the CLI render endpoints from it, avoiding cross-module drift.",
-      "confidence": "medium",
-      "impact_scope": "module",
-      "fix_scope": "multi_file_refactor"
-    }
-  ],
-  "retrospective": {
-    "root_causes": [
-      "Shared logic exists without a single owning abstraction, leading to duplication across modules."
-    ],
-    "likely_symptoms": [
-      "sequence_rule_duplication",
-      "format_registry_split"
-    ],
-    "possible_false_positives": []
-  }
-}

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

@@ -1,86 +0,0 @@
-{
-  "batch": "Testing & API",
-  "batch_index": 4,
-  "assessments": {
-    "api_surface_coherence": 76.0,
-    "mid_level_elegance": 86.0
-  },
-  "dimension_notes": {
-    "api_surface_coherence": {
-      "evidence": [
-        "parsePort/parseChunkSize/parseLatency use parseInt without strict digit validation, so values like \"10abc\" or \"1.5\" are accepted as 10 or 1.",
-        "parseLogLevel uses `value in LEVEL_PRIORITY`, which is true for prototype keys like \"toString\" and can accept non-log-level strings.",
-        "parseHost is async (DNS lookup) while other validators are sync, creating mixed sync/async API shape in the same validator module."
-      ],
-      "impact_scope": "module",
-      "fix_scope": "single_edit",
-      "confidence": "high"
-    },
-    "mid_level_elegance": {
-      "evidence": [
-        "parseHost introduces network I/O during validation, while peer validators are pure, forcing callers into an async control flow for otherwise synchronous validation."
-      ],
-      "impact_scope": "module",
-      "fix_scope": "single_edit",
-      "confidence": "medium",
-      "issues_preventing_higher_score": "Validation seams are not uniform: one validator performs async DNS lookup while others are synchronous, complicating orchestration of CLI validation flow."
-    }
-  },
-  "findings": [
-    {
-      "dimension": "api_surface_coherence",
-      "identifier": "lax_numeric_parsing",
-      "summary": "Numeric validators accept non-numeric suffixes due to parseInt behavior",
-      "related_files": [
-        "src/cli-validators.ts"
-      ],
-      "evidence": [
-        "parsePort/parseChunkSize/parseLatency use parseInt and only check isNaN and range, so inputs like \"10abc\" or \"1.5\" pass as 10 or 1."
-      ],
-      "suggestion": "Validate with a strict digit regex (e.g., `/^\\d+$/`) and use `Number(value)` + `Number.isInteger` before range checks.",
-      "confidence": "high",
-      "impact_scope": "module",
-      "fix_scope": "single_edit"
-    },
-    {
-      "dimension": "api_surface_coherence",
-      "identifier": "log_level_guard_proto_keys",
-      "summary": "Log-level guard accepts prototype keys because it uses `in`",
-      "related_files": [
-        "src/cli-validators.ts"
-      ],
-      "evidence": [
-        "`isLogLevel` uses `value in LEVEL_PRIORITY`, which returns true for inherited keys like \"toString\"."
-      ],
-      "suggestion": "Use `Object.hasOwn(LEVEL_PRIORITY, value)` or `VALID_LOG_LEVELS.includes(value as LogLevel)` to restrict to real log levels.",
-      "confidence": "high",
-      "impact_scope": "local",
-      "fix_scope": "single_edit"
-    },
-    {
-      "dimension": "api_surface_coherence",
-      "identifier": "mixed_sync_async_validators",
-      "summary": "Validator API mixes sync and async functions within the same surface",
-      "related_files": [
-        "src/cli-validators.ts"
-      ],
-      "evidence": [
-        "parseHost is async (DNS lookup) while parsePort/parseLogLevel/parseChunkSize/parseLatency are synchronous."
-      ],
-      "suggestion": "Either make all validators async (returning Promise) or split DNS resolution into a separate async phase so the core validator API is uniform.",
-      "confidence": "medium",
-      "impact_scope": "module",
-      "fix_scope": "multi_file_refactor"
-    }
-  ],
-  "retrospective": {
-    "root_causes": [
-      "Validators prioritize permissive parsing and ad-hoc checks over strict, uniform validation rules."
-    ],
-    "likely_symptoms": [
-      "lax_numeric_parsing",
-      "mixed_sync_async_validators"
-    ],
-    "possible_false_positives": []
-  }
-}

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

@@ -1 +0,0 @@
-{"batch":"Authorization","batch_index":5,"assessments":{"authorization_consistency":92.0,"mid_level_elegance":90.0},"dimension_notes":{"authorization_consistency":{"evidence":["MockServer wires all format routes via `this.app.post(format.route, createRouteHandler(format, deps))` with no auth/token checks in this file.","`host` option allows `\"0.0.0.0\"` exposure but there is no access-control or warning path in MockServer."],"impact_scope":"module","fix_scope":"single_edit","confidence":"medium","issues_preventing_higher_score":"No optional auth hook or explicit guard/warning when binding to public interfaces; the server is always unauthenticated regardless of host exposure."},"mid_level_elegance":{"evidence":["Route wiring and dependency injection happen inside the constructor, so adding middleware/auth per format requires editing `MockServer` internals rather than a seam or hook.","The dependency bag passed to `createRouteHandler` is assembled inline with implicit shape and no local contract comments, making the handoff less explicit."],"impact_scope":"module","fix_scope":"single_edit","confidence":"low","issues_preventing_higher_score":"Handoff between MockServer and route-handler is implicit and not externally configurable, limiting seam clarity for auth/middleware composition."}},"findings":[],"retrospective":{"root_causes":[],"likely_symptoms":[],"possible_false_positives":[]}}

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

@@ -1,87 +0,0 @@
-{
-  "batch": "AI Debt & Migrations",
-  "batch_index": 6,
-  "assessments": {
-    "ai_generated_debt": 90.0,
-    "incomplete_migration": 95.0,
-    "low_level_elegance": 88.0
-  },
-  "dimension_notes": {
-    "ai_generated_debt": {
-      "evidence": [
-        "src/types/request.ts uses multiple explanatory comments on self-describing fields (e.g., lastMessage/systemMessage/toolNames) that mostly restate the property name.",
-        "src/types/rule.ts has a long comment block on Match that largely repeats the union’s behavior (string/RegExp/object/function)."
-      ],
-      "impact_scope": "local",
-      "fix_scope": "single_edit",
-      "confidence": "medium",
-      "issues_preventing_higher_score": "Several comments restate obvious field semantics and could be reduced to higher-signal notes only."
-    },
-    "incomplete_migration": {
-      "evidence": [
-        "No @deprecated markers, migration TODOs, or legacy/new dual-path APIs appear in src/types/request.ts.",
-        "No @deprecated markers, migration TODOs, or legacy/new dual-path APIs appear in src/types/rule.ts."
-      ],
-      "impact_scope": "local",
-      "fix_scope": "single_edit",
-      "confidence": "low",
-      "issues_preventing_higher_score": "Small surface area limits certainty; no migration residue observed in the reviewed files."
-    },
-    "low_level_elegance": {
-      "evidence": [
-        "src/types/request.ts uses optional properties with explicit `| undefined` (e.g., tools?: readonly ToolDef[] | undefined; toolCallId?: string | undefined).",
-        "src/types/rule.ts uses optional properties without explicit `| undefined` (e.g., message?: string | RegExp; toolCallId?: string), creating inconsistent type style."
-      ],
-      "impact_scope": "local",
-      "fix_scope": "single_edit",
-      "confidence": "high",
-      "issues_preventing_higher_score": "Inconsistent and redundant optional typing adds noise and small but repeated cognitive overhead."
-    }
-  },
-  "findings": [
-    {
-      "dimension": "ai_generated_debt",
-      "identifier": "restating_comments_on_types",
-      "summary": "Comments restate obvious type semantics, adding low-signal noise",
-      "related_files": [
-        "src/types/request.ts",
-        "src/types/rule.ts"
-      ],
-      "evidence": [
-        "src/types/request.ts comments explain fields like lastMessage/systemMessage/toolNames in a way that mirrors the field name.",
-        "src/types/rule.ts Match comment block describes each union variant in a way that repeats the type definition."
-      ],
-      "suggestion": "Trim comments to only convey non-obvious constraints or behavioral nuances; remove restatements of field names or type unions.",
-      "confidence": "medium",
-      "impact_scope": "local",
-      "fix_scope": "single_edit"
-    },
-    {
-      "dimension": "low_level_elegance",
-      "identifier": "redundant_optional_undefined",
-      "summary": "Optional fields redundantly include `| undefined`, creating inconsistency and noise",
-      "related_files": [
-        "src/types/request.ts",
-        "src/types/rule.ts"
-      ],
-      "evidence": [
-        "src/types/request.ts declares `tools?: readonly ToolDef[] | undefined` and `toolCallId?: string | undefined`, which are already implied by `?`.",
-        "src/types/rule.ts uses `?:` without explicit `| undefined`, so the style is inconsistent across related type modules."
-      ],
-      "suggestion": "Remove explicit `| undefined` from optional properties in src/types/request.ts to align with TypeScript conventions and the style used in src/types/rule.ts.",
-      "confidence": "high",
-      "impact_scope": "local",
-      "fix_scope": "single_edit"
-    }
-  ],
-  "retrospective": {
-    "root_causes": [
-      "Documentation and type style appear auto-generated or copied without consolidation, leading to minor noise."
-    ],
-    "likely_symptoms": [
-      "restating_comments_on_types",
-      "redundant_optional_undefined"
-    ],
-    "possible_false_positives": []
-  }
-}

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

@@ -1 +0,0 @@
-{"batch":"Package Organization","batch_index":7,"assessments":{"package_organization":80.0,"high_level_elegance":83.0},"dimension_notes":{"package_organization":{"evidence":["holistic_context.structure.directory_profiles shows `src/` has `file_count: 11` with mixed concerns (cli, server/runtime, history, loader, logger, rule-engine).","holistic_context.structure.coupling_matrix shows bidirectional edges `src/ → src/formats/` (3) and `src/formats/ → src/` (3), indicating a blurred boundary between core runtime and format-specific code."],"impact_scope":"subsystem","fix_scope":"multi_file_refactor","confidence":"high"},"high_level_elegance":{"evidence":["Top-level `src/` bundles CLI entry (`cli.ts`), CLI validators (`cli-validators.ts`), and runtime/state (`history.ts`) in a single flat folder, making ownership boundaries non-obvious for newcomers.","Format-specific areas are cleanly grouped under `src/formats/*`, but core runtime files remain flat, which weakens the overall domain-aligned decomposition."],"impact_scope":"subsystem","fix_scope":"multi_file_refactor","confidence":"medium"}},"findings":[{"dimension":"package_organization","identifier":"flat_src_root_mixed_concerns","summary":"`src/` is a flat folder with mixed CLI/runtime/history concerns, obscuring ownership boundaries.","related_files":["src/cli.ts","src/history.ts","src/cli-validators.ts"],"evidence":["`holistic_context.structure.directory_profiles` lists 11 files in `src/` spanning CLI (`cli.ts`), history/state (`history.ts`), and core runtime (`mock-server.ts`, `rule-engine.ts`).","`holistic_context.structure.coupling_matrix` shows `src/ ↔ src/formats/` bidirectional imports, which is a typical signal of missing subpackage boundaries."],"suggestion":"Staged reorg plan: 1) Create `src/cli/` and `src/server/` folders. 2) Move CLI files first: `src/cli.ts` → `src/cli/index.ts`, `src/cli-validators.ts` → `src/cli/validators.ts`. 3) Move runtime/state next: `src/history.ts` → `src/server/history.ts` (and later other runtime files like `mock-server.ts`, `rule-engine.ts` if desired). 4) Update import paths using `rg \"./cli-validators|./history\" src test` and edit imports to new locations. 5) Validate with `npm test` (vitest) and, if available, `npm run build` to ensure path resolution is correct.","confidence":"high","impact_scope":"subsystem","fix_scope":"multi_file_refactor","root_cause_cluster":"flat_src_root"},{"dimension":"package_organization","identifier":"cli_validators_not_colocated","summary":"CLI-only validators live at `src/` root despite being used only by the CLI entrypoint.","related_files":["src/cli.ts","src/cli-validators.ts","test/cli-validators.test.ts"],"evidence":["`src/cli-validators.ts` is imported only by `src/cli.ts` and its dedicated test (`test/cli-validators.test.ts`).","No other modules consume `cli-validators.ts`, indicating it belongs inside a CLI-focused subpackage rather than the root."],"suggestion":"Staged reorg plan: 1) Create `src/cli/`. 2) Move `src/cli-validators.ts` → `src/cli/validators.ts`. 3) Update `src/cli.ts` to import from `./cli/validators.js` (or `./cli/validators.js` after moving `cli.ts` as part of a broader CLI folder move). 4) Update `test/cli-validators.test.ts` to import from `../src/cli/validators.js`. 5) Validate with `npm test` to ensure CLI parsing tests still pass.","confidence":"high","impact_scope":"module","fix_scope":"multi_file_refactor","root_cause_cluster":"flat_src_root"},{"dimension":"high_level_elegance","identifier":"ownership_boundaries_blurred_by_root_layout","summary":"Top-level decomposition mixes CLI and runtime concerns, weakening domain-aligned ownership.","related_files":["src/cli.ts","src/history.ts"],"evidence":["CLI entry (`src/cli.ts`) and runtime/state (`src/history.ts`) sit side-by-side at the root, making the top-level package map less expressive than the format-specific subfolders under `src/formats/*`.","The flat root layout requires readers to scan files to infer domains instead of discovering boundaries through folder structure."],"suggestion":"Staged reorg plan: 1) Introduce explicit domain folders such as `src/cli/` and `src/runtime/` (or `src/server/`). 2) Move `src/cli.ts` (and `src/cli-validators.ts`) into `src/cli/` first, then move `src/history.ts` into `src/runtime/` alongside related runtime modules. 3) Update imports via `rg \"\\./cli|\\./history\" src test` and edit to new paths. 4) Validate with `npm test` and, if applicable, `npm run build` to confirm the public entrypoints still resolve correctly.","confidence":"medium","impact_scope":"subsystem","fix_scope":"multi_file_refactor","root_cause_cluster":"flat_src_root"}],"retrospective":{"root_causes":["Flat `src/` root mixes multiple domains without subpackages, reducing navigability and ownership clarity."],"likely_symptoms":["cli_validators_not_colocated"],"possible_false_positives":[]}}

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

@@ -1,107 +0,0 @@
-{
-  "batch": "Governance & Contracts",
-  "batch_index": 8,
-  "assessments": {
-    "cross_module_architecture": 88.0,
-    "high_level_elegance": 87.0,
-    "package_organization": 82.0
-  },
-  "dimension_notes": {
-    "cross_module_architecture": {
-      "evidence": [
-        "src/types.ts is a root barrel that re-exports three distinct type domains (request/reply/rule) and is a top imported module in the codebase (fan_in 19 per holistic_context.god_modules).",
-        "src/formats/types.ts and src/formats/request-helpers.ts both import from ../types.js, pulling format-specific code through the root barrel."
-      ],
-      "impact_scope": "subsystem",
-      "fix_scope": "multi_file_refactor",
-      "confidence": "medium",
-      "issues_preventing_higher_score": "The root-level types barrel concentrates multiple domain contracts and becomes a coupling hub; narrowing entry points would reduce cross-module blast radius."
-    },
-    "high_level_elegance": {
-      "evidence": [
-        "src/formats/request-helpers.ts constructs the core MockRequest (including headers/path defaults and message-derived fields), tying core request shape to the format layer rather than a core request module.",
-        "src/formats/types.ts defines the Format interface yet relies on root-level types via ../types.js, reinforcing format-layer ownership of core request lifecycle."
-      ],
-      "impact_scope": "subsystem",
-      "fix_scope": "multi_file_refactor",
-      "confidence": "medium",
-      "issues_preventing_higher_score": "Request lifecycle ownership is blurred between core and format layers, making high-level responsibilities less crisp."
-    },
-    "package_organization": {
-      "evidence": [
-        "holistic_context.structure shows src/ has 11 production files (avg_fan_in 3.8) spanning CLI, server, logging, rules, and types, indicating a flat, mixed-concern directory.",
-        "Within src/, core building blocks like src/logger.ts, src/rule-engine.ts, and src/types.ts sit alongside unrelated entrypoints (cli.ts, mock-server.ts), which obscures ownership boundaries."
-      ],
-      "impact_scope": "codebase",
-      "fix_scope": "multi_file_refactor",
-      "confidence": "high"
-    }
-  },
-  "findings": [
-    {
-      "dimension": "cross_module_architecture",
-      "identifier": "types_barrel_coupling_hub",
-      "summary": "Root types barrel concentrates multiple domains and amplifies cross-module coupling.",
-      "related_files": [
-        "src/types.ts",
-        "src/formats/types.ts",
-        "src/formats/request-helpers.ts"
-      ],
-      "evidence": [
-        "src/types.ts re-exports request/reply/rule types into one root barrel, and format modules import from ../types.js rather than their specific domain files.",
-        "This pattern makes any change to request/reply/rule type boundaries ripple through a single high-fan-in module."
-      ],
-      "suggestion": "Split the barrel into domain entry points (for example: `src/types/request.ts`, `src/types/reply.ts`, `src/types/rule.ts`) and update format imports to target the specific domain paths; keep `src/types.ts` only for external package exports if needed, and avoid internal imports from it.",
-      "confidence": "medium",
-      "impact_scope": "subsystem",
-      "fix_scope": "multi_file_refactor"
-    },
-    {
-      "dimension": "high_level_elegance",
-      "identifier": "format_layer_owns_request_construction",
-      "summary": "Format layer builds the core MockRequest, blurring ownership of request lifecycle.",
-      "related_files": [
-        "src/formats/request-helpers.ts",
-        "src/formats/types.ts",
-        "src/types.ts"
-      ],
-      "evidence": [
-        "buildMockRequest in src/formats/request-helpers.ts derives lastMessage/systemMessage/toolNames and sets headers/path defaults, which are core request concerns.",
-        "Format interface in src/formats/types.ts consumes this helper indirectly, keeping request shape tied to the formats package."
-      ],
-      "suggestion": "Move MockRequest construction into a core module (for example `src/request/build-mock-request.ts` or `src/core/mock-request.ts`) and have format parsers return a minimal parsed shape; use the core builder to add shared defaults and derived fields.",
-      "confidence": "medium",
-      "impact_scope": "subsystem",
-      "fix_scope": "multi_file_refactor"
-    },
-    {
-      "dimension": "package_organization",
-      "identifier": "flat_src_mixed_concerns",
-      "summary": "The root src/ directory is a mixed-concern flat folder that hides ownership boundaries.",
-      "related_files": [
-        "src/logger.ts",
-        "src/rule-engine.ts",
-        "src/types.ts"
-      ],
-      "evidence": [
-        "holistic_context.structure shows src/ contains 11 production files spanning CLI/server/logging/rules/types, indicating mixed responsibilities in a single directory.",
-        "Core building blocks (logger, rule engine, types) live beside entrypoints, making navigation and change ownership less predictable."
-      ],
-      "suggestion": "Staged reorg plan: 1) Create target folders `src/core/`, `src/logging/`, and `src/entrypoints/`. 2) Move core building blocks: `git mv src/rule-engine.ts src/core/rule-engine.ts`, `git mv src/types.ts src/core/types.ts`. 3) Move logging: `git mv src/logger.ts src/logging/logger.ts`. 4) Update imports by searching: `rg -n \"from \\\"\\.\\/rule-engine\\\"|from \\\"\\.\\/types\\\"|from \\\"\\.\\/logger\\\"\" src test` and adjust to new paths. 5) Validate with `npm test` and `npm run build`.",
-      "confidence": "high",
-      "impact_scope": "codebase",
-      "fix_scope": "multi_file_refactor"
-    }
-  ],
-  "retrospective": {
-    "root_causes": [
-      "Core domain types and request lifecycle are centralized at the root level, encouraging broad coupling and diffusing ownership boundaries.",
-      "The src/ directory has grown organically without sub-package delineation, leading to mixed concerns."
-    ],
-    "likely_symptoms": [
-      "types_barrel_coupling_hub",
-      "format_layer_owns_request_construction"
-    ],
-    "possible_false_positives": []
-  }
-}

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

@@ -1,67 +0,0 @@
-{
-  "batch": "Cross-cutting Sweep",
-  "batch_index": 9,
-  "assessments": {
-    "design_coherence": 82.0
-  },
-  "dimension_notes": {
-    "design_coherence": {
-      "evidence": [
-        "Sequence rule construction is implemented in two places with similar step-mapping and resolver wiring (`MockServer.when().replySequence()` in src/mock-server.ts and `addSequenceRule()` in src/loader.ts).",
-        "The `MockServer` class mixes HTTP server lifecycle (Fastify setup/start/stop), rule authoring APIs, fallback management, and request history/logging state in one surface (src/mock-server.ts)."
-      ],
-      "impact_scope": "subsystem",
-      "fix_scope": "multi_file_refactor",
-      "confidence": "medium"
-    }
-  },
-  "findings": [
-    {
-      "dimension": "design_coherence",
-      "identifier": "sequence_rule_duplication",
-      "summary": "Sequence rule normalization is duplicated in server API and loader paths",
-      "related_files": [
-        "src/mock-server.ts",
-        "src/loader.ts",
-        "src/rule-engine.ts"
-      ],
-      "evidence": [
-        "`MockServer.when().replySequence()` maps `SequenceEntry` values into steps, creates a sequence resolver, assigns `rule.resolve`, and sets `rule.remaining`.",
-        "`addSequenceRule()` in `src/loader.ts` performs the same step normalization, `createSequenceResolver()` call, and `rule.remaining` setup for JSON5 rules."
-      ],
-      "suggestion": "Extract a shared helper in `src/rule-engine.ts` (or a new `sequence` utility) that accepts normalized entries and returns a configured rule; use it from both `replySequence()` and `addSequenceRule()` to centralize sequence behavior.",
-      "confidence": "medium",
-      "impact_scope": "module",
-      "fix_scope": "multi_file_refactor"
-    },
-    {
-      "dimension": "design_coherence",
-      "identifier": "mockserver_multi_role",
-      "summary": "`MockServer` combines server lifecycle, rule authoring, and state tracking responsibilities",
-      "related_files": [
-        "src/mock-server.ts",
-        "src/rule-engine.ts",
-        "src/history.ts"
-      ],
-      "evidence": [
-        "`MockServer` constructs the Fastify server and registers format routes in the constructor, exposes rule authoring methods (`when`, `whenTool`, `nextError`), manages fallback state, and owns `RequestHistory` and logging.",
-        "This blends HTTP runtime concerns with rule registry and history concerns that already exist as separate modules (`RuleEngine`, `RequestHistory`)."
-      ],
-      "suggestion": "Split `MockServer` into a runtime/server wrapper and a rule/history registry (e.g., extract a `RuleRegistry` or `MockServerCore` that exposes `when*`, `history`, `rules`, and fallback), and keep Fastify lifecycle and route wiring in a thinner server class.",
-      "confidence": "medium",
-      "impact_scope": "subsystem",
-      "fix_scope": "architectural_change"
-    }
-  ],
-  "retrospective": {
-    "root_causes": [
-      "Sequence rule behavior is implemented in parallel call paths without a shared abstraction.",
-      "Top-level API class aggregates multiple subsystems to present a convenient surface, but lacks internal separation."
-    ],
-    "likely_symptoms": [
-      "sequence_rule_duplication",
-      "mockserver_multi_role"
-    ],
-    "possible_false_positives": []
-  }
-}