@dailephd/my-dev-kit-lab 0.6.3 → 0.7.1

package/CHANGELOG.md

@@ -4,6 +4,23 @@ All notable changes to my-dev-kit-lab are documented here.
 
 ## [Unreleased]
 
+## [0.7.1] - 2026-10-02
+
+### Synthetic large-repository generator
+
+- Added deterministic synthetic TypeScript and Python repository generation under `src/evaluation/syntheticRepository/`: a strict `SyntheticRepositoryConfigV1`, seed- and identity-based pure planning, a versioned generator-owned PRNG, exact source/test/symbol/import/depth/repeated-pattern dimensions, and localized, cross-module, and broad-change task answer keys.
+- Added contained, idempotent materialization with a per-repository generation manifest (deterministic file hashes and metrics) and a read-only manifest verifier, plus an in-memory `EvaluationCase` adapter that reuses the existing raw baseline and scoring.
+- Added `--synthetic-config <path>` to `experiment run --experiment context-window-scaling` so the experiment can run over generated repositories placed beneath the run output; it is a command input selector (mutually exclusive with `--case`), not a plugin config field. Without it, the bundled v0.7.0 fixed corpus is used unchanged.
+- Extended help, `experiment list`/`describe` text, and installed-package acceptance to cover the synthetic input for both languages. The `context-window-scaling` treatments, budget semantics, correctness/success semantics, execution artifact, reports, and plots are unchanged.
+
+## [0.7.0] - 2026-10-01
+
+### Context-window scaling
+
+- Added the self-only `context-window-scaling` experiment plugin with standard and custom estimated-token budgets, raw-full-file and my-dev-kit-guided context evidence, fit/utilization/correctness/success measurements, and bounded omitted-relevant-file reporting.
+- Added the versioned `context-window-scaling-execution.json` artifact, JSON/text/HTML report section, and three context-window plot families through the existing `plots generate` command.
+- Extended exact packed-package acceptance to cover installed discovery, execution, reports, plots, custom budgets, and immutability of the bundled context-window case contract and fixed project.
+
 ## [0.6.3] - 2026-09-30
 
 ### Four-treatment partial-refresh experiments

package/README.md

@@ -6,7 +6,7 @@ my-dev-kit provides local repository indexing and graph-guided retrieval. my-dev
 
 Whole-ecosystem workflows are centralized in [my-dev-kit/docs/ECOSYSTEM_DEVELOPMENT_WORKFLOWS.md](https://github.com/dailephd/my-dev-kit/blob/main/docs/ECOSYSTEM_DEVELOPMENT_WORKFLOWS.md). Its [command-surface compatibility map](https://github.com/dailephd/my-dev-kit/blob/main/docs/ECOSYSTEM_DEVELOPMENT_WORKFLOWS.md#915-command-surface-compatibility-map) documents which Lab outputs can safely seed my-dev-kit investigation, Observer reference work, or Orchestrator evidence, and which look-alike artifacts are not direct inputs.
 
-The latest release is v0.6.3 (four-treatment partial-refresh experiments), and the published package and installed CLI are version 0.6.3. The previous release is v0.6.2 (incremental-change and staleness experiments). The v0.4.5 context-integrity evaluation remains intentionally frozen against the published `@dailephd/my-dev-kit@1.10.4` and `@dailephd/my-dev-kit-orchestrator@1.2.3` contracts; those versions are historical validation baselines, not a statement that they are the ecosystem's current releases. See [docs/CURRENT_STATE.md](docs/CURRENT_STATE.md) for current state.
+The latest release is v0.7.1 (synthetic large-repository generator), and the published package and installed CLI are version 0.7.1. The previous release is v0.7.0 (context-window scaling), and v0.7.2 (real/local external repository experiments) is planned after the current release. The v0.4.5 context-integrity evaluation remains intentionally frozen against the published `@dailephd/my-dev-kit@1.10.4` and `@dailephd/my-dev-kit-orchestrator@1.2.3` contracts; those versions are historical validation baselines, not a statement that they are the ecosystem's current releases. See [docs/CURRENT_STATE.md](docs/CURRENT_STATE.md) for current state.
 
 v0.4.6 adds a supported `my-dev-kit-lab` installed CLI router (`--help`, `--version`, `security validate`, `audit`, the `experiment` family, `report render`, `plots generate`, `gallery build`, `demo final`, and the historical direct final-demo invocation form), a writable lab workspace model kept separate from the installed package and the inspected target, and a permanent packed-tarball installation/execution acceptance gate (`npm run verify:packed-package`). See [docs/ROADMAP.md](docs/ROADMAP.md) and [docs/CURRENT_STATE.md](docs/CURRENT_STATE.md) for status detail and [docs/ARCHITECTURE.md](docs/ARCHITECTURE.md) for the runtime path model. The "Installed CLI" section below documents the shipped command surface; the source-checkout `npm run` workflow in Quickstart remains available for contributors.
 
@@ -16,7 +16,9 @@ v0.4.6 adds a supported `my-dev-kit-lab` installed CLI router (`--help`, `--vers
 - **Measure warm-index reuse (v0.5.0–v0.5.1, released):** the `warm-index-reuse` experiment plugin builds one my-dev-kit index per benchmark project, reuses it across that project's tasks, and compares every task with a matched `raw-full-file` baseline. Reports separate one-time index-build cost from per-task retrieval cost, show amortized index cost and cumulative measurements, and include deterministic fake-agent correctness and token evidence; `plots generate` renders four warm-index SVG charts. The v0.5.1 release adds a dedicated 12-task benchmark corpus (`benchmarks/contracts/warm-index-benchmark-cases.json`: six medium and six large/mixed tasks tagged `localized`, `cross-module`, or `broad-change`) for comparing warm-index behavior as task count grows. Estimated context tokens (a character-based context-size estimate) and fake-agent total tokens (simulated harness telemetry) are reported separately, and neither is provider billing telemetry.
 - **Run selectable real-agent warm-index campaigns (v0.5.2, released):** `--campaign codex-full`, `claude-full`, or `codex-timeout-isolation` (with `--include-real-agents`) runs exactly one provider — Codex or Claude — against the exact raw and warm contexts the experiment already measured, over the frozen production corpus each preset owns. Provider outcomes (`completed`, `failed`, `timeout`, `invalid-output`, `agent-unavailable`, `agent-limit-reached`, `skipped`) are classified and reported separately from warm-index infrastructure status, so a campaign can complete its indexing/retrieval work even when provider evidence is partial or unavailable. A campaign run automatically produces the report, the same four warm-index SVG charts, and a three-item gallery (report, plots, bounded execution evidence). Its report screenshot is best-effort presentation evidence: unavailable browser runtime or failed capture is reported explicitly, no PNG is fabricated, and neither outcome fails an otherwise successful campaign. Legacy runs without `--campaign` keep the existing deterministic fake-agent, report-only behavior unchanged. See [docs/WORKFLOWS.md](docs/WORKFLOWS.md#warm-index-reuse-experiment) and [docs/METRICS.md](docs/METRICS.md#warm-index-reuse-metrics).
 - **Record index freshness evidence (v0.6.0):** a warm-index run captures an index snapshot after its one index build — the exact indexed file set from the my-dev-kit index contract, each with SHA-256 content identity, size, and modified-time metadata, plus the my-dev-kit version and index-command evidence — and assesses freshness immediately before each task's warm retrieval as `fresh`, `stale`, `partially-stale`, or `unknown`. The evidence appears in `warm-index-execution.json` and in the existing `report.json`/`report.txt`/`report.html` warm-index reports. It is observational only: it covers only files the snapshot lists (not the whole repository), never changes retrieval, execution or provider status, and adds no CLI flag, metric, plot, gallery item, or reindex recommendation in v0.6.0. See [docs/METRICS.md](docs/METRICS.md#index-freshness-evidence-v060) and [docs/WORKFLOWS.md](docs/WORKFLOWS.md#warm-index-reuse-experiment).
-- **Compare no-refresh, partial-refresh, and full-refresh retrieval after a controlled change (v0.6.3, current release):** the `incremental-change-staleness` experiment plugin runs six frozen controlled-change scenario families (unrelated-file, local-implementation, exported-symbol, public-API, import-graph, and test-only changes) against four disposable target copies — `stale-index` (no refresh), `changed-files-refresh` and `affected-neighborhood-refresh` (real partial refreshes performed by my-dev-kit 1.12.5 through `index --incremental --refresh-scope`, selected internally with no Lab-level flag), and `full-refresh` (a complete new post-change index, used as a comparison reference rather than a preferred treatment). Each partial treatment truthfully records whether upstream applied the requested partial scope or fell back to a full rebuild (`APPLIED_PARTIAL` or `FALLBACK_FULL`); a fallback is not counted as partial-refresh evidence. Three comparisons against `full-refresh` are persisted with retrieval, deterministic fake-agent correctness, and required-file evidence in `incremental-change-staleness-execution.json` (schema `my-dev-kit-lab-incremental-change-staleness-execution-v2`) and the existing `report.json`/`report.txt`/`report.html`; historical v0.6.2 (V1) artifacts stay readable. There is no winner, ranking, or safety claim, and the plugin is self-only (`--target` is not accepted). `--kit-command` also accepts `incremental-change-staleness` and now defaults to my-dev-kit 1.12.5. See [docs/WORKFLOWS.md](docs/WORKFLOWS.md) and [docs/METRICS.md](docs/METRICS.md).
+- **Compare no-refresh, partial-refresh, and full-refresh retrieval after a controlled change (v0.6.3, previous release):** the `incremental-change-staleness` experiment plugin runs six frozen controlled-change scenario families (unrelated-file, local-implementation, exported-symbol, public-API, import-graph, and test-only changes) against four disposable target copies — `stale-index` (no refresh), `changed-files-refresh` and `affected-neighborhood-refresh` (real partial refreshes performed by my-dev-kit 1.12.5 through `index --incremental --refresh-scope`, selected internally with no Lab-level flag), and `full-refresh` (a complete new post-change index, used as a comparison reference rather than a preferred treatment). Each partial treatment truthfully records whether upstream applied the requested partial scope or fell back to a full rebuild (`APPLIED_PARTIAL` or `FALLBACK_FULL`); a fallback is not counted as partial-refresh evidence. Three comparisons against `full-refresh` are persisted with retrieval, deterministic fake-agent correctness, and required-file evidence in `incremental-change-staleness-execution.json` (schema `my-dev-kit-lab-incremental-change-staleness-execution-v2`) and the existing `report.json`/`report.txt`/`report.html`; historical v0.6.2 (V1) artifacts stay readable. There is no winner, ranking, or safety claim, and the plugin is self-only (`--target` is not accepted). `--kit-command` also accepts `incremental-change-staleness` and now defaults to my-dev-kit 1.12.5. See [docs/WORKFLOWS.md](docs/WORKFLOWS.md) and [docs/METRICS.md](docs/METRICS.md).
+- **Measure context-window scaling (v0.7.0, released):** the self-only `context-window-scaling` plugin compares `raw-full-file` and `my-dev-kit-guided` over 8k, 16k, 32k, 64k, or custom positive-integer estimated-token budgets. It records fit, utilization, deterministic fake-agent correctness/success, and omitted expected relevant files, with JSON/text/HTML reports and three SVG plots. `plots generate` reads `context-window-scaling-execution.json`. Token counts are a character-based estimate, not provider-tokenizer or billing data; fake-agent correctness is context-independent in the current harness. See [docs/WORKFLOWS.md](docs/WORKFLOWS.md), [docs/METRICS.md](docs/METRICS.md), and [docs/COMMANDS.md](docs/COMMANDS.md).
+- **Run context-window scaling over synthetic repositories (v0.7.1, current release):** `context-window-scaling` uses the bundled fixed corpus by default, or `--synthetic-config <path>` (a `SyntheticRepositoryConfigV1` JSON file) to generate disposable deterministic TypeScript/Python repositories beneath the run output. The option is a command input selector, not plugin scientific config; it is mutually exclusive with `--case`, and the scientific semantics, execution artifact, reports, and plots are unchanged. See [docs/COMMANDS.md](docs/COMMANDS.md) and [docs/WORKFLOWS.md](docs/WORKFLOWS.md).
 - **Assess affected-neighborhood evidence (v0.6.1, released; retained in the current package):** using the baseline my-dev-kit graph of the same prepared warm index (loaded once per session), each task's confirmed modified or missing indexed files, and the baseline symbols those files contain, are mapped to graph nodes. The affected neighborhood is those seed nodes plus their direct one-hop neighbors (edges of any kind, either direction). The task's `expectedFiles` and file-scoped `expectedSymbols` are mapped to graph nodes and compared with that neighborhood, which yields six numeric warm-side metrics (`changedFileCount`, `changedSymbolCount`, `affectedNodeCount`, `affectedEdgeCount`, `taskOverlapCount`, `taskOverlapPercent`) plus categorical evidence: a `related`, `unrelated`, or `unknown` relationship and a `recommended`, `not-indicated`, or `unknown` `reindexRecommendation`. Incomplete evidence is reported as `unknown`, never as unrelated. The assessment is recorded additively in `warm-index-execution.json` and shown in the existing `report.json`/`report.txt`/`report.html` warm-index reports. It is observational only: retrieval, execution status, and provider status are unchanged, nothing is reindexed automatically, and no CLI flag, experiment plugin, plot, or gallery item was added. See [docs/METRICS.md](docs/METRICS.md#affected-neighborhood-metrics-v061) and [docs/WORKFLOWS.md](docs/WORKFLOWS.md#warm-index-reuse-experiment).
 - **Audit repository health:** run conservative code-rot detectors for TypeScript/JavaScript, Python, Java, and Kotlin, or adapt security findings into the common audit report.
 - **Validate CLI/package security:** inspect dependencies, package contents, path and subprocess boundaries, malformed inputs, optional static scanners, and bounded fuzz targets.
@@ -236,11 +238,12 @@ See [docs/METRICS.md](docs/METRICS.md) for full metric definitions.
 - Claude and Codex token totals are used only when the CLI/run exposes them; missing provider token evidence stays explicitly unavailable (never zero, and never substituted with an estimated context-token count)
 - Codex and Claude campaign runs can produce timeouts, invalid-output, agent-unavailable, or agent-limit-reached outcomes; these are structured provider states, not warm-index infrastructure failures
 - Small projects may make raw-full-file cheaper than my-dev-kit-guided; larger localized tasks are where my-dev-kit is expected to become more useful
-- The generic experiment-plugin framework has three registered plugins: `context-strategy-comparison`, the v0.5.0-introduced `warm-index-reuse`, and the `incremental-change-staleness` plugin (introduced in v0.6.2; extended to four treatments in current release v0.6.3). Later plugins such as context-window scaling remain future roadmap work
+- The generic experiment-plugin framework has four registered plugins: `context-strategy-comparison`, `warm-index-reuse`, `incremental-change-staleness`, and `context-window-scaling`. The v0.7.0 context-window-scaling plugin is released; v0.7.1 lets it also run over caller-supplied synthetic repositories; external/local repository experiments (v0.7.2), retrieval precision/recall, and agent-success plugins remain planned.
 - `warm-index-reuse` without `--campaign` still uses the deterministic fake agent only. With `--campaign`, exactly one real provider (Codex or Claude) runs per campaign preset — there is no multi-agent matrix, retry, provider switching, or scheduler. The v0.5.1 expanded corpus is deterministic fake-agent benchmark evidence when run without `--campaign`. No warm-index mode calculates a token-savings percentage, break-even task, winner, or ranking, and component-duration sums are not wall-clock latency
 - The current release does not guarantee token savings; it produces auditable evidence for specific cases, targets, agents, and strategies
+- Context-window scaling uses estimated tokens (`ceil(characters / 4)`) and experiment budgets, not actual provider tokenizer or model-window limits. Its deterministic fake-agent correctness check does not measure semantic sensitivity to the supplied context.
 - Released v0.6.1 affected-neighborhood evidence is bounded to the baseline graph of the prepared index and to the snapshot-represented files: a changed symbol means the symbol was present in a confirmed changed indexed file, not that its own text was proven to change; `not-indicated` means only that this bounded analysis found no supporting evidence for reindexing, not that skipping a reindex is safe; unresolved or ambiguous expected symbols keep a task at `unknown` rather than unrelated
-- v0.6.3 (current release) partial-refresh evidence is scoped to the executed deterministic scenarios and the configured my-dev-kit 1.12.5-or-later tool. A partial treatment can fall back to a full rebuild and is then reported as not comparable as partial refresh, so an applied partial refresh in one run does not guarantee the next; `no-observed-regression-relative-to-full` is not a safety claim, and full refresh is a reference rather than a winner. Correctness remains deterministic fake-agent evidence, and `incremental-change-staleness` accepts no external `--target`.
+- v0.6.3 (previous release) partial-refresh evidence is scoped to the executed deterministic scenarios and the configured my-dev-kit 1.12.5-or-later tool. A partial treatment can fall back to a full rebuild and is then reported as not comparable as partial refresh, so an applied partial refresh in one run does not guarantee the next; `no-observed-regression-relative-to-full` is not a safety claim, and full refresh is a reference rather than a winner. Correctness remains deterministic fake-agent evidence, and `incremental-change-staleness` accepts no external `--target`.
 - Provider telemetry dashboards, semantic LLM judging, and cloud API billing integration are not yet implemented
 - The six new stage-context strategies have no CLI flags yet, are configured programmatically, and do not yet include plots, screenshots, or gallery integration
 - The published upstream artifacts the stage-context strategies read do not expose considered-but-unselected reads or unnecessary-read evidence; those metrics report `unavailable` rather than zero

package/benchmarks/contracts/context-window-scaling-cases.json

@@ -0,0 +1,220 @@
+[
+  {
+    "id": "ctx-scale-a-8k-16k",
+    "title": "Context scaling A: Shipping quote by weight band",
+    "benchmarkProject": "context-window-scaling-fixed-ts",
+    "taskLocality": "localized",
+    "targetRoot": "benchmarks/projects/context-window-scaling-fixed-ts",
+    "sourceRoots": [
+      "src",
+      "tests"
+    ],
+    "query": "shipping quote weight band zone surcharge parcel",
+    "expectedFiles": [
+      "src/tasks/shippingQuote.ts",
+      "tests/tasks/shippingQuote.test.ts"
+    ],
+    "expectedSymbols": [
+      "selectWeightBand",
+      "calculateShippingQuote"
+    ],
+    "answerKey": {
+      "expectedFiles": [
+        "src/tasks/shippingQuote.ts",
+        "tests/tasks/shippingQuote.test.ts"
+      ],
+      "expectedSymbols": [
+        "selectWeightBand",
+        "calculateShippingQuote"
+      ],
+      "expectedFacts": [
+        {
+          "id": "ctx-scale-a-band-selection",
+          "text": "selectWeightBand returns the smallest weight band whose maxGrams holds the parcel weight and rejects non-positive or oversize weights.",
+          "weight": 1,
+          "required": true
+        },
+        {
+          "id": "ctx-scale-a-zone-surcharge",
+          "text": "calculateShippingQuote adds a zone surcharge (domestic 0, regional 250, international 1200 cents) to the selected band base price.",
+          "weight": 1,
+          "required": true
+        }
+      ],
+      "minimumCorrectFacts": 2,
+      "notes": "Small task-relevant surface inside a fixed static repository whose filler tiers scale raw context."
+    },
+    "rawIncludeGlobs": [
+      "src/tasks/**/*",
+      "tests/**/*",
+      "src/filler/tier-1/**/*"
+    ],
+    "notes": "Raw context scale band A (filler tiers 1..1); band bounds are enforced by the corpus test."
+  },
+  {
+    "id": "ctx-scale-b-16k-32k",
+    "title": "Context scaling B: Invoice total with bulk discount and tax",
+    "benchmarkProject": "context-window-scaling-fixed-ts",
+    "taskLocality": "localized",
+    "targetRoot": "benchmarks/projects/context-window-scaling-fixed-ts",
+    "sourceRoots": [
+      "src",
+      "tests"
+    ],
+    "query": "invoice total bulk discount quantity tax rounding cents",
+    "expectedFiles": [
+      "src/tasks/invoiceTotals.ts",
+      "tests/tasks/invoiceTotals.test.ts"
+    ],
+    "expectedSymbols": [
+      "calculateInvoiceTotal",
+      "applyBulkDiscount",
+      "roundToCents"
+    ],
+    "answerKey": {
+      "expectedFiles": [
+        "src/tasks/invoiceTotals.ts",
+        "tests/tasks/invoiceTotals.test.ts"
+      ],
+      "expectedSymbols": [
+        "calculateInvoiceTotal",
+        "applyBulkDiscount",
+        "roundToCents"
+      ],
+      "expectedFacts": [
+        {
+          "id": "ctx-scale-b-bulk-discount",
+          "text": "applyBulkDiscount gives 5 percent off at quantity 20 and 10 percent off at quantity 100 or more.",
+          "weight": 1,
+          "required": true
+        },
+        {
+          "id": "ctx-scale-b-tax-after-discount",
+          "text": "calculateInvoiceTotal adds rounded tax computed on the discounted subtotal.",
+          "weight": 1,
+          "required": true
+        }
+      ],
+      "minimumCorrectFacts": 2,
+      "notes": "Small task-relevant surface inside a fixed static repository whose filler tiers scale raw context."
+    },
+    "rawIncludeGlobs": [
+      "src/tasks/**/*",
+      "tests/**/*",
+      "src/filler/tier-1/**/*",
+      "src/filler/tier-2/**/*"
+    ],
+    "notes": "Raw context scale band B (filler tiers 1..2); band bounds are enforced by the corpus test."
+  },
+  {
+    "id": "ctx-scale-c-32k-64k",
+    "title": "Context scaling C: Inventory stock reservation",
+    "benchmarkProject": "context-window-scaling-fixed-ts",
+    "taskLocality": "localized",
+    "targetRoot": "benchmarks/projects/context-window-scaling-fixed-ts",
+    "sourceRoots": [
+      "src",
+      "tests"
+    ],
+    "query": "reserve stock release reservation available quantity insufficient",
+    "expectedFiles": [
+      "src/tasks/inventoryReservation.ts",
+      "tests/tasks/inventoryReservation.test.ts"
+    ],
+    "expectedSymbols": [
+      "reserveStock",
+      "releaseReservation",
+      "availableStock"
+    ],
+    "answerKey": {
+      "expectedFiles": [
+        "src/tasks/inventoryReservation.ts",
+        "tests/tasks/inventoryReservation.test.ts"
+      ],
+      "expectedSymbols": [
+        "reserveStock",
+        "releaseReservation",
+        "availableStock"
+      ],
+      "expectedFacts": [
+        {
+          "id": "ctx-scale-c-reserve-limits",
+          "text": "reserveStock rejects non-positive quantities and quantities above available stock, returning a new level without mutating the input.",
+          "weight": 1,
+          "required": true
+        },
+        {
+          "id": "ctx-scale-c-release-limits",
+          "text": "releaseReservation rejects quantities that are non-positive or larger than the reserved amount.",
+          "weight": 1,
+          "required": true
+        }
+      ],
+      "minimumCorrectFacts": 2,
+      "notes": "Small task-relevant surface inside a fixed static repository whose filler tiers scale raw context."
+    },
+    "rawIncludeGlobs": [
+      "src/tasks/**/*",
+      "tests/**/*",
+      "src/filler/tier-1/**/*",
+      "src/filler/tier-2/**/*",
+      "src/filler/tier-3/**/*"
+    ],
+    "notes": "Raw context scale band C (filler tiers 1..3); band bounds are enforced by the corpus test."
+  },
+  {
+    "id": "ctx-scale-d-64k-plus",
+    "title": "Context scaling D: Audit entry redaction",
+    "benchmarkProject": "context-window-scaling-fixed-ts",
+    "taskLocality": "localized",
+    "targetRoot": "benchmarks/projects/context-window-scaling-fixed-ts",
+    "sourceRoots": [
+      "src",
+      "tests"
+    ],
+    "query": "audit entry redact mask email token",
+    "expectedFiles": [
+      "src/tasks/auditRedaction.ts",
+      "tests/tasks/auditRedaction.test.ts"
+    ],
+    "expectedSymbols": [
+      "redactAuditEntry",
+      "maskEmail"
+    ],
+    "answerKey": {
+      "expectedFiles": [
+        "src/tasks/auditRedaction.ts",
+        "tests/tasks/auditRedaction.test.ts"
+      ],
+      "expectedSymbols": [
+        "redactAuditEntry",
+        "maskEmail"
+      ],
+      "expectedFacts": [
+        {
+          "id": "ctx-scale-d-email-mask",
+          "text": "maskEmail keeps the first local-part character, masks the rest, and returns [invalid-email] for malformed addresses.",
+          "weight": 1,
+          "required": true
+        },
+        {
+          "id": "ctx-scale-d-token-redaction",
+          "text": "redactAuditEntry replaces any token with [redacted] and drops fields other than actor, action, email, and token.",
+          "weight": 1,
+          "required": true
+        }
+      ],
+      "minimumCorrectFacts": 2,
+      "notes": "Small task-relevant surface inside a fixed static repository whose filler tiers scale raw context."
+    },
+    "rawIncludeGlobs": [
+      "src/tasks/**/*",
+      "tests/**/*",
+      "src/filler/tier-1/**/*",
+      "src/filler/tier-2/**/*",
+      "src/filler/tier-3/**/*",
+      "src/filler/tier-4/**/*"
+    ],
+    "notes": "Raw context scale band D (filler tiers 1..4); band bounds are enforced by the corpus test."
+  }
+]

package/benchmarks/projects/README.md

@@ -2,7 +2,7 @@
 
 This directory contains deterministic benchmark projects used by my-dev-kit-lab.
 
-The current suite mixes baseline Todo fixtures with more complex workflow and analytics projects:
+The shared-profile suite mixes baseline Todo fixtures with more complex workflow and analytics projects:
 
 - `todo-ts`
 - `todo-js`
@@ -11,6 +11,8 @@ The current suite mixes baseline Todo fixtures with more complex workflow and an
 - `task-workflow-medium-ts`
 - `task-analytics-large-mixed`
 
+The v0.7.0 release also includes `context-window-scaling-fixed-ts` as an experiment-specific, static scaling corpus. It is intentionally not part of the shared `benchmark-project-profiles.json` contract: the `context-window-scaling` plugin derives its project profile in memory. The fixed corpus is frozen v0.7.0 evidence and is not a generator.
+
 The Todo fixtures stay intentionally small so validation and smoke experiments remain cheap. The newer medium and large projects are intentionally more connected so raw full-file context and guided retrieval diverge more meaningfully.
 
 Benchmark project profiles live in `benchmarks/contracts/benchmark-project-profiles.json`.

package/benchmarks/projects/context-window-scaling-fixed-ts/README.md

@@ -0,0 +1,14 @@
+# context-window-scaling-fixed-ts
+
+Static, committed benchmark project for the v0.7.0 context-window-scaling plugin. It is an ordinary
+TypeScript tree, not a generator.
+
+- `src/tasks/` and `tests/tasks/` hold the four small task-relevant implementation surfaces
+  (shipping quote, invoice totals, inventory reservation, audit redaction).
+- `src/filler/tier-1` ... `tier-4` hold scale-only catalog modules that are semantically unrelated to
+  every task. Cases include filler tiers cumulatively through `rawIncludeGlobs`, so raw full-file
+  context grows from scale A (tier-1) to scale D (tier-1..4).
+
+Cases live in `benchmarks/contracts/context-window-scaling-cases.json`. Measured raw estimated-token
+bands are enforced by `tests/benchmarks/contextWindowScalingCorpus.test.ts` using the production
+raw-full-file baseline and `countEstimatedTokens`.

package/benchmarks/projects/context-window-scaling-fixed-ts/src/filler/tier-1/carrier-depot-catalog-01.ts

@@ -0,0 +1,302 @@
+// Scale-only filler (tier-1). Ordinary catalog data for a carrier depot listing.
+// It is unrelated to every task under src/tasks and exists only to add repository context.
+
+export interface CarrierDepotRecord01 {
+  id: string;
+  label: string;
+  capacity: number;
+  priority: number;
+  active: boolean;
+  notes: string;
+}
+
+export const carrierDepotRecords01: readonly CarrierDepotRecord01[] = [
+  {
+    id: "car-01-001",
+    label: "central annex 1",
+    capacity: 84,
+    priority: 3,
+    active: false,
+    notes: "granite carrier depot entry reviewed in cycle 5"
+  },
+  {
+    id: "car-01-002",
+    label: "granite annex 2",
+    capacity: 62,
+    priority: 3,
+    active: false,
+    notes: "central carrier depot entry reviewed in cycle 1"
+  },
+  {
+    id: "car-01-003",
+    label: "northern annex 3",
+    capacity: 64,
+    priority: 2,
+    active: false,
+    notes: "eastern carrier depot entry reviewed in cycle 5"
+  },
+  {
+    id: "car-01-004",
+    label: "northern hall 4",
+    capacity: 12,
+    priority: 5,
+    active: false,
+    notes: "northern carrier depot entry reviewed in cycle 9"
+  },
+  {
+    id: "car-01-005",
+    label: "granite hall 5",
+    capacity: 64,
+    priority: 1,
+    active: false,
+    notes: "northern carrier depot entry reviewed in cycle 9"
+  },
+  {
+    id: "car-01-006",
+    label: "central hall 6",
+    capacity: 16,
+    priority: 2,
+    active: false,
+    notes: "northern carrier depot entry reviewed in cycle 9"
+  },
+  {
+    id: "car-01-007",
+    label: "central annex 7",
+    capacity: 58,
+    priority: 5,
+    active: false,
+    notes: "granite carrier depot entry reviewed in cycle 5"
+  },
+  {
+    id: "car-01-008",
+    label: "northern row 8",
+    capacity: 50,
+    priority: 4,
+    active: false,
+    notes: "granite carrier depot entry reviewed in cycle 1"
+  },
+  {
+    id: "car-01-009",
+    label: "northern hall 9",
+    capacity: 14,
+    priority: 3,
+    active: false,
+    notes: "granite carrier depot entry reviewed in cycle 5"
+  },
+  {
+    id: "car-01-010",
+    label: "northern hall 10",
+    capacity: 48,
+    priority: 3,
+    active: false,
+    notes: "central carrier depot entry reviewed in cycle 1"
+  },
+  {
+    id: "car-01-011",
+    label: "central hall 11",
+    capacity: 26,
+    priority: 3,
+    active: false,
+    notes: "northern carrier depot entry reviewed in cycle 1"
+  },
+  {
+    id: "car-01-012",
+    label: "granite row 12",
+    capacity: 66,
+    priority: 4,
+    active: false,
+    notes: "northern carrier depot entry reviewed in cycle 5"
+  },
+  {
+    id: "car-01-013",
+    label: "riverside row 13",
+    capacity: 24,
+    priority: 5,
+    active: false,
+    notes: "central carrier depot entry reviewed in cycle 9"
+  },
+  {
+    id: "car-01-014",
+    label: "granite hall 14",
+    capacity: 88,
+    priority: 2,
+    active: false,
+    notes: "northern carrier depot entry reviewed in cycle 5"
+  },
+  {
+    id: "car-01-015",
+    label: "northern hall 15",
+    capacity: 28,
+    priority: 3,
+    active: false,
+    notes: "northern carrier depot entry reviewed in cycle 1"
+  },
+  {
+    id: "car-01-016",
+    label: "granite row 16",
+    capacity: 96,
+    priority: 1,
+    active: false,
+    notes: "northern carrier depot entry reviewed in cycle 1"
+  },
+  {
+    id: "car-01-017",
+    label: "northern row 17",
+    capacity: 68,
+    priority: 1,
+    active: false,
+    notes: "central carrier depot entry reviewed in cycle 1"
+  },
+  {
+    id: "car-01-018",
+    label: "northern annex 18",
+    capacity: 98,
+    priority: 3,
+    active: false,
+    notes: "northern carrier depot entry reviewed in cycle 5"
+  },
+  {
+    id: "car-01-019",
+    label: "granite hall 19",
+    capacity: 52,
+    priority: 1,
+    active: false,
+    notes: "granite carrier depot entry reviewed in cycle 1"
+  },
+  {
+    id: "car-01-020",
+    label: "northern hall 20",
+    capacity: 70,
+    priority: 5,
+    active: false,
+    notes: "central carrier depot entry reviewed in cycle 5"
+  },
+  {
+    id: "car-01-021",
+    label: "northern row 21",
+    capacity: 30,
+    priority: 5,
+    active: false,
+    notes: "central carrier depot entry reviewed in cycle 5"
+  },
+  {
+    id: "car-01-022",
+    label: "central hall 22",
+    capacity: 34,
+    priority: 1,
+    active: false,
+    notes: "northern carrier depot entry reviewed in cycle 9"
+  },
+  {
+    id: "car-01-023",
+    label: "central annex 23",
+    capacity: 68,
+    priority: 1,
+    active: false,
+    notes: "central carrier depot entry reviewed in cycle 5"
+  },
+  {
+    id: "car-01-024",
+    label: "northern hall 24",
+    capacity: 46,
+    priority: 4,
+    active: false,
+    notes: "central carrier depot entry reviewed in cycle 9"
+  },
+  {
+    id: "car-01-025",
+    label: "northern row 25",
+    capacity: 90,
+    priority: 1,
+    active: false,
+    notes: "northern carrier depot entry reviewed in cycle 9"
+  },
+  {
+    id: "car-01-026",
+    label: "northern row 26",
+    capacity: 66,
+    priority: 5,
+    active: false,
+    notes: "northern carrier depot entry reviewed in cycle 5"
+  },
+  {
+    id: "car-01-027",
+    label: "central annex 27",
+    capacity: 98,
+    priority: 4,
+    active: false,
+    notes: "granite carrier depot entry reviewed in cycle 1"
+  },
+  {
+    id: "car-01-028",
+    label: "granite hall 28",
+    capacity: 14,
+    priority: 5,
+    active: false,
+    notes: "northern carrier depot entry reviewed in cycle 5"
+  },
+  {
+    id: "car-01-029",
+    label: "central row 29",
+    capacity: 92,
+    priority: 4,
+    active: false,
+    notes: "central carrier depot entry reviewed in cycle 9"
+  },
+  {
+    id: "car-01-030",
+    label: "northern row 30",
+    capacity: 30,
+    priority: 1,
+    active: false,
+    notes: "northern carrier depot entry reviewed in cycle 9"
+  },
+  {
+    id: "car-01-031",
+    label: "central row 31",
+    capacity: 18,
+    priority: 4,
+    active: false,
+    notes: "central carrier depot entry reviewed in cycle 5"
+  },
+  {
+    id: "car-01-032",
+    label: "granite hall 32",
+    capacity: 80,
+    priority: 5,
+    active: false,
+    notes: "granite carrier depot entry reviewed in cycle 9"
+  },
+  {
+    id: "car-01-033",
+    label: "northern annex 33",
+    capacity: 36,
+    priority: 2,
+    active: false,
+    notes: "granite carrier depot entry reviewed in cycle 1"
+  },
+  {
+    id: "car-01-034",
+    label: "granite row 34",
+    capacity: 68,
+    priority: 3,
+    active: false,
+    notes: "northern carrier depot entry reviewed in cycle 1"
+  }
+];
+
+export function findCarrierDepotRecord01(id: string): CarrierDepotRecord01 | undefined {
+  return carrierDepotRecords01.find((record) => record.id === id);
+}
+
+export function listCarrierDepotActiveRecords01(): CarrierDepotRecord01[] {
+  return carrierDepotRecords01.filter((record) => record.active);
+}
+
+export function totalCarrierDepotCapacity01(): number {
+  return carrierDepotRecords01.reduce((sum, record) => sum + record.capacity, 0);
+}
+
+export function countCarrierDepotByPriority01(priority: number): number {
+  return carrierDepotRecords01.filter((record) => record.priority === priority).length;
+}