@untangle-code/config 0.0.0-stage → 0.1.0

package/NOTICE

@@ -0,0 +1,90 @@
+# NOTICE
+
+Copyright (C) 2026 Luke Bölling and contributors.
+
+This attribution covers original Untangle work. Contributors retain copyright in
+their contributions. Third-party packages, grammars and other materials retain
+their own copyright holders, licenses and notices; this line does not replace them.
+
+## License — binding decision
+
+Untangle is licensed under the **GNU Affero General Public License, Version 3
+(AGPL-3.0-only)**. See [`LICENSE`](./LICENSE).
+
+This decision is **final, not provisional**, and was explicitly instructed by
+the project owner. No contributor, agent or tool may change it without a new
+explicit instruction.
+
+The repository-wide license covers Untangle's first-party source code, scripts,
+tests, fixtures, configuration, documentation, website and brand artwork, including
+the logo and 3D yarn illustrations. Every workspace `package.json` declares
+`"license": "AGPL-3.0-only"`. There is no separately licensed enterprise component
+or separate permissive license for documentation or brand assets.
+
+Third-party code, embedded grammars, dependency assets and their notices retain
+their original licenses. Their inclusion does not relicense those works. The
+repository license does not grant trademark rights or change the license of a
+repository analyzed with Untangle. See the repository's `docs/LICENSING.md` for
+scope and verification details.
+
+This resolves the license question left open in `vision.md` §14 and completes
+`product.md` §16, item 2.
+
+## Rationale
+
+- **Network copyleft fits the intended product model.** AGPL §13 sets source
+  availability requirements for modified versions used through a computer network.
+  The current local CLI/stdio-MCP entry and future shared-server modes share the
+  same license.
+- **Local-first analysis has a clear boundary.** Running Untangle against a codebase
+  does not replace that codebase's own license with Untangle's license.
+- **First-party components share one license.** Implemented components and future
+  official plugins use this repository's licensing policy. Planned integrations do
+  not establish implemented or published products.
+
+## Deliberately accepted consequence
+
+The project deliberately chooses AGPL rather than a permissive embedding license.
+Redistribution, modifications and combined works must be assessed against the
+actual terms in `LICENSE`, including applicable Corresponding Source requirements.
+No permissive exception, commercial dual license or special contract-only package
+license is granted or promised by this notice.
+
+## Dependencies
+
+Third-party runtime dependencies are checked against the allowlist in
+`scripts/check-licenses.mjs`. Their licenses and copyright notices remain unchanged
+and traceable through package `THIRD_PARTY_LICENSES.md` files, grammar provenance,
+the lockfile and release SBOM. The allowlist includes MIT / Apache-2.0 / BSD / ISC
+and other explicitly listed licenses; it is not a license grant for dependencies.
+
+The allowlist in `scripts/check-licenses.mjs` applies to **dependencies**, not
+workspace packages. Untangle's own packages carry AGPL-3.0-only and are excluded
+from that check.
+
+## Clean room
+
+Untangle is an independent implementation with its own data models, APIs, tool
+names, tests and sources. Feature ideas may be derived from publicly observable
+behavior and generally known techniques. Third-party source code is not copied,
+including from AGPL projects even where the license would permit it.
+
+## Contribution terms
+
+Pull requests are welcome under the repository's existing AGPL-3.0-only license.
+No separate CLA, copyright assignment or DCO sign-off is required. Contributors
+must have the right to submit their work under those terms. See CONTRIBUTING.md.
+
+## Release decisions
+
+- [x] Copyright attribution: Luke Bölling, with contributors retaining their rights.
+- [x] Contributions use AGPL-3.0-only without an additional CLA or DCO gate.
+
+## Open legal items before public beta
+
+- [ ] Trademark search for the product name `Untangle`.
+- [ ] Registration and legal review of the npm scope `@untangle-code`.
+- [ ] Verify source availability and notices for each released network daemon/server
+  mode (WP-59). The current stdio MCP `untangle_about` already reports the license,
+  source repository and build commit when supplied; metadata alone does not prove
+  that a concrete deployed version's source is available.

package/README.md

@@ -1,3 +1,263 @@
-# Temporary Holding Version
+# @untangle-code/config
 
-This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
+Untangle configuration (WP-02): types, discovery, six-layer resolution, handwritten JSON Schema,
+secret redaction, canonical effective configuration with hashes and `embedding_profile_id`, and
+migration infrastructure for future `schemaVersion` changes. A public package
+(`@untangle-code/config`, product.md §6.2).
+
+Normative sources: [`spec.md`](../../spec.md) §4.1–§4.8, §5.7 (takes precedence),
+[`product.md`](../../product.md) §11, [`architecture.md`](../../architecture.md) §6.3, §23.2,
+[`portfolio.md`](../../portfolio.md) §13, §14.4.
+
+`src/index.ts` is the only public interface. Its sole runtime dependency is
+`@untangle-code/domain` (`workspace:*`); no other Untangle or external runtime dependencies.
+
+<a id="modulübersicht"></a>
+
+## Modules
+
+| Module | Contents | Normative source |
+|---|---|---|
+| `types.ts` | `UntangleConfigV1`, `QdrantConfig`, `EmbeddingConfig`, `IndexConfig`, `SearchConfig`, `GraphConfig`, `ComplexityConfig`, `ChangeConfig`, `QualityGateConfig`, `TelemetryConfig`, `PortfolioConfig`/`PortfolioEnrichmentConfig`, `EffectiveUntangleConfigV1`, `RawConfigLayer`/`DeepPartial`; re-exports domain's `RepositoryConfig`/`ContextArtifactConfig` | spec §4.2–§4.7; portfolio §13, §14.4 |
+| `defaults.ts` | Defaults per section, `PRODUCT_DEFAULT_CONFIG` (layer 6), `CURRENT_SCHEMA_VERSION` | spec §4.5; product §11 |
+| `schema.ts` | Parsed `CONFIG_SCHEMA` and `CONFIG_SCHEMA_PATH` | arch §6.3, §7.3 |
+| `discovery.ts` | `discoverConfigFile`, `discoverConfigFiles`: upward discovery to repository/filesystem root | spec §4.1 |
+| `user-config.ts` | `resolveUserConfigDir`/`resolveUserConfigPath`: OS configuration directory | spec §4.1 layer 5 |
+| `env.ts` | `ENV_MAPPING`, `buildEnvConfigLayer`: `UNTANGLE_*` to config paths | spec §4.1 layer 2 |
+| `merge.ts` | `deepMergeConfig`, `mergeConfigLayers`: replace arrays, never concatenate | spec §4.1 |
+| `paths.ts` | Canonical `resolveConfigPath`, `resolveRepositoryPaths`, relative to configuration file | spec §4.3 |
+| `secrets.ts` | `redactSecrets`, `toRedactedJson`, `resolveApiKey` | spec §4.4/§4.5, §24; arch §23.2 |
+| `hash.ts` | `computeConfigHash`, `deriveEmbeddingProfile`/`deriveEmbeddingProfileId` | arch §6.3; spec §5.1, §5.7 |
+| `validate.ts` | `validateEffectiveConfig`, `assertConfigValid`, `assertEmbeddingDimensionsMatch` | spec §4.8 |
+| `migrations.ts` | `registerMigration`, `migrateConfig`, `clearMigrations` | arch §6.3 |
+| `load.ts` | `loadConfig`: orchestrates these modules | spec §4.1–§4.8 |
+
+## Layering (spec.md §4.1)
+
+Highest priority first; `loadConfig` merges in the following order, lowest first and last wins:
+
+```text
+1. Explicit API/CLI arguments        (loadConfig({ explicit }))
+2. Environment variables             (UNTANGLE_*, see env.ts ENV_MAPPING)
+3. .untangle.local.json              (upward discovery from cwd)
+4. .untangle.json                    (upward discovery from cwd)
+5. User configuration (OS directory) (user-config.ts)
+6. Product defaults                  (defaults.ts PRODUCT_DEFAULT_CONFIG)
+```
+
+Merge semantics: objects merge recursively; **arrays replace completely**, never concatenate.
+Replacing a full list such as `exclude` is the only way a higher layer can shrink it; silently
+combining array sources would be unpredictable.
+
+`.untangle.local.json` and `.untangle.json` are discovered **independently**, each searching upward
+from `cwd` to the repository root (a directory containing `.git`) or filesystem root, whichever
+comes first.
+
+<a id="untangle_-umgebungsvariablen-auszug-additiv-erweiterbar"></a>
+
+## `UNTANGLE_*` environment variables (excerpt, additively extensible)
+
+| Variable | Configuration path |
+|---|---|
+| `UNTANGLE_WORKSPACE_ID` | `workspaceId` |
+| `UNTANGLE_PROJECT_ID` | `projectId` |
+| `UNTANGLE_STORAGE_BACKEND` | `storage.backend` (`lancedb` or `qdrant`) |
+| `UNTANGLE_LANCEDB_PATH` | `storage.path` (local directory) |
+| `UNTANGLE_QDRANT_MODE` / `_URL` / `_API_KEY_ENV` / `_COLLECTION_PREFIX` / `_REQUEST_TIMEOUT_MS` / `_MAX_RETRIES` | `qdrant.*` |
+| `UNTANGLE_EMBEDDINGS_MODE` / `_URL` / `_API_KEY_ENV` / `_MODEL` / `_DIMENSIONS` / `_REQUEST_TIMEOUT_MS` | `embeddings.*` |
+| `UNTANGLE_INDEX_WATCH` / `_MAX_FILE_SIZE_MB` / `_EXTRA_EXTENSIONS` (CSV) | `index.*` |
+| `UNTANGLE_QUALITY_GATE_MODE` / `_MINIMUM_PARSE_QUALITY` | `qualityGate.*` |
+| `UNTANGLE_TELEMETRY_ENABLED` / `_LOG_LEVEL` | `telemetry.*` |
+| `UNTANGLE_PORTFOLIO_ENABLED` | `portfolio.enabled` |
+
+The complete machine-readable table is `ENV_MAPPING` in `src/env.ts`. `*_API_KEY_ENV` sets another
+environment variable's **name**, never its secret value (see Secrets).
+
+## Search storage
+
+New projects use embedded LanceDB at `.untangle/index/lancedb`. A relative `storage.path`
+resolves against the repository root, including when configuration lives in
+`.untangle/config.json`. Absolute local directories are accepted; URI schemes and network
+paths are rejected.
+
+Existing projects that explicitly configure a `qdrant` section or a mapped
+`UNTANGLE_QDRANT_*` variable retain Qdrant. An explicit `storage.backend` overrides that
+compatibility default, with the ordinary layer precedence. Setting only `storage.path`
+does not move an existing Qdrant project. Qdrant connection options remain under `qdrant`:
+
+```toml
+[storage]
+backend = "qdrant"
+
+[qdrant]
+mode = "external"
+url = "http://127.0.0.1:16333"
+```
+
+`parseConfigText(text, "json" | "toml")` parses and migrates an existing document without
+filesystem access, product defaults or environment overrides. Callers such as `init` can
+preserve declared storage choices while inspecting the original configuration.
+
+## Secrets (spec.md §4.4/§4.5, §24; architecture.md §23.2)
+
+`QdrantConfig.apiKeyEnv` / `EmbeddingConfig.apiKeyEnv` store only environment variable **names**, so
+effective configuration structurally never contains secret values. `resolveApiKey(envVarName, env)`
+resolves values at runtime on demand; results must never be written back to configuration objects.
+`redactSecrets`/`toRedactedJson` provide additional protection: every field resembling a resolved
+secret (`apiKey`, `token`, `secret`, `password`, `credential`, but NOT `...Env`) is replaced with
+`[REDACTED]` before serialization, even if accidentally attached to configuration. Verified in
+`secrets.test.ts`.
+
+<a id="validierung-specmd-48"></a>
+
+## Validation (spec.md §4.8)
+
+`loadConfig` **never** throws for warnings or errors; it returns
+`{ effectiveConfig, warnings, errors }`. Unknown top-level fields warn with the field name as path.
+Invalid enums, unresolved core values (such as missing `qdrant.url` with `mode: "external"`),
+duplicate repository/artifact IDs and `portfolio.blueprint.weights` sums outside `1.0 ± 0.001`
+produce `CONFIG_INVALID`. Aborting is deliberately the caller's choice:
+`assertConfigValid(result.errors)` throws a domain `UntangleError`.
+`assertEmbeddingDimensionsMatch(configured, existing)` checks conflicts before the first upsert
+(`EMBEDDING_DIMENSION_MISMATCH`).
+
+<a id="korpusgebundene-relevanz-policies-wp-231"></a>
+
+### Corpus-bound relevance policies (WP-231)
+
+`search.relevancePolicies` deliberately has **no product default**. Raw cosine values and their
+separation depend jointly on embedding profile and indexed corpus. Each entry is therefore keyed
+by complete `embeddingProfileId` and bound to exactly one `workspaceId` and physical `collection`:
+
+```toml
+workspaceId = "workspace-stable-id"
+
+[search.relevancePolicies."complete-embedding-profile-id"]
+workspaceId = "workspace-stable-id"
+collection = "untangle_project_code_profile_v1"
+
+[search.relevancePolicies."complete-embedding-profile-id".policy]
+calibrationId = "model/corpus/revision"
+minimumDenseScore = 0.45
+minimumDenseSpread = 0.061
+denseReferenceRank = 50
+minimumCandidateIdfCoverage = 0.291
+```
+
+If any profile/workspace/collection scope fails to match, search discards no results and reports
+`RELEVANCE_POLICY_NOT_EVALUATED`. The same applies when retrieval did not actually reach the
+calibrated dense reference rank or the sparse branch is missing. IDF evidence uses fixed
+dense/sparse prefixes through the reference rank, so raising `candidateLimit` cannot move the
+calibrated yes/no decision. Significant corpus changes require remeasurement. An already-indexed
+workspace should declare a top-level `workspaceId`, otherwise adding the policy changes the
+configuration hash and thus the derived workspace ID itself.
+
+<a id="kanonische-effective-config-hash-und-embedding_profile_id"></a>
+
+## Canonical effective configuration, hash and `embedding_profile_id`
+
+`computeConfigHash(effectiveConfig)` equals `SHA256(canonical_json(effectiveConfig))`, using
+domain's `canonicalJson`/`sha256Hex`, for LanceDB. For Qdrant, the additive `storage` section is
+excluded so existing configuration hashes and derived workspace identities remain unchanged;
+the endpoint and other connection options remain represented by `qdrant`. Without explicit `workspaceId`, `loadConfig` uses that hash as
+`configHash` input to `buildWorkspaceId` (spec §5.1). `deriveEmbeddingProfile`/
+`deriveEmbeddingProfileId` construct domain's `EmbeddingProfile` from `EmbeddingConfig` plus fixed
+`DEFAULT_EMBEDDING_NORMALIZATION` (`"none"`) and `PREPARED_TEXT_VERSION`
+(`"untangle-prepared-text-v1"`), then call `buildEmbeddingProfileId` (spec §5.7).
+
+## Migration (architecture.md §6.3)
+
+`registerMigration({ fromVersion, toVersion, migrate })` registers one step;
+`migrateConfig(raw, targetVersion)` chains registered steps from `raw.schemaVersion` (default `1`)
+to `targetVersion` (default `CURRENT_SCHEMA_VERSION`). Configuration already at the target version
+undergoes **identity migration** and returns unchanged without requiring registered steps (tested).
+`loadConfig` migrates each raw file configuration separately before merging it.
+
+<a id="entscheidungen"></a>
+
+## Decisions
+
+1. **`RepositoryConfig`/`ContextArtifactConfig` re-export domain types instead of duplicating
+   them.** Domain README decision 5 explicitly requires this for `RepositoryConfig`; the same
+   applies to `ContextArtifactConfig` (BUILD_PLAN §3.3 lists it among domain core contracts).
+
+2. **`SearchConfig`, `GraphConfig`, `ComplexityConfig`, `ChangeConfig` are designed here.**
+   Spec.md §4.2 names them without shapes, unlike §4.4–§4.7's four concrete infrastructure/index/
+   quality schemas. `TelemetryConfig` is likewise unspecified beyond mandatory default-off
+   behavior (spec §24). Each shape references its closest normative source in `types.ts`:
+   `SearchConfig` uses `SearchRequestV1`/§13.3 boosts, `GraphConfig` architecture.md §17.4 traversal
+   limits, `ComplexityConfig` product.md §11's example, and `ChangeConfig` spec §17.6 risk defaults.
+   Downstream work may extend them additively, not redefine them locally.
+
+3. **`PortfolioConfig` follows portfolio.md §14.4 verbatim**, including every default; its required
+   ±0.001 sum validation for `blueprint.weights` is implemented in `validate.ts`.
+
+4. **JSON Schema lives in `packages/config/schemas/config-v1.json`, not root `schemas/`.**
+   BUILD_PLAN §4 also assigns `schemas/**` to WP-02, but this package's task explicitly limited
+   writes to `packages/config/**`. As noted in `openIssues`, an authorized owner must mirror it
+   to `schemas/config-v1.json`. `schema.ts` resolves `../schemas/config-v1.json` from
+   `import.meta.url`, working from both `src/` tests and `dist/` builds because both are siblings
+   of `schemas/`.
+
+5. **`additionalProperties: false` in JSON Schema despite spec §4.8's warn-not-fail rule.** The
+   handwritten schema is tooling for editor completion/external validators; this package does not
+   run it through a runtime schema validator such as ajv. `validate.ts` implements exact warning/
+   abort semantics from spec §4.8 directly in TypeScript without another runtime dependency. The schema documents
+   this decision in `description`.
+
+6. **`normalization` and `preparedTextVersion` are not `EmbeddingConfig` fields but are required
+   for `embedding_profile_id`.** Spec §4.5 lists exactly ten fields excluding them, while §5.7
+   requires them for profile identity. Fixed defaults in `defaults.ts` supply
+   `DEFAULT_EMBEDDING_NORMALIZATION = "none"` and
+   `PREPARED_TEXT_VERSION = "untangle-prepared-text-v1"`; `deriveEmbeddingProfile`'s second
+   argument can override them for future configuration extensions.
+
+7. **Deep-partial raw layers (`RawConfigLayer`/`DeepPartial<T>`).** An individual file/environment/
+   argument layer rarely supplies complete `QdrantConfig`/`EmbeddingConfig`; a shallow
+   `Partial<UntangleConfigV1>` would still require every field within any supplied child object.
+   `DeepPartial` makes every field recursively optional; after merging product defaults,
+   `validate.ts` enforces actual requirements. Its condition deliberately uses `T extends object`
+   rather than `T extends Record<string, unknown>`: the latter is structurally false for
+   interfaces lacking index signatures in TypeScript conditional types, a verified compiler trap.
+
+8. **`loadConfig` never throws itself.** File read errors, invalid JSON and validation failures all
+   enter `errors`/`warnings`; only explicitly invoked `assertConfigValid` throws
+   `UntangleError("CONFIG_INVALID", …)`. This follows the requested result-object rather than
+   exception behavior for warnings, consistently extended to errors so a CLI can collect and
+   present every issue before aborting.
+
+9. **Discovery stops at a `.git` directory entry OR filesystem root.** Spec §4.1 names repository/
+   filesystem roots without defining repository detection. A directory containing `.git` as a file
+   or directory, supporting Git worktrees, is a repository root: it is searched, its parent is not.
+   No `GitPort` is needed; filesystem existence checks suffice, and discovery already needs filesystem access.
+
+10. **JSON Schema uses `schemaVersion` `const: 1`, while `RawConfigLayer` uses `number`.** Raw
+    unmigrated files may carry any historical version, read by `migrateConfig` before merge.
+    JSON Schema describes the *current* v1 tooling contract.
+
+<a id="verifikation"></a>
+
+## Verification
+
+```bash
+pnpm --filter @untangle-code/config run typecheck   # tsc, 0 errors
+pnpm --filter @untangle-code/config run test        # vitest, 73 tests passed, 1 skipped (Windows path test on POSIX)
+pnpm --filter @untangle-code/config run build       # emit to dist/
+```
+
+<a id="lizenz"></a>
+
+## License
+
+
+**AGPL-3.0-only.** This package includes the complete license in [`LICENSE`](./LICENSE), the
+license-choice rationale in [`NOTICE`](./NOTICE), and licenses for all third-party production
+dependencies in [`THIRD_PARTY_LICENSES.md`](./THIRD_PARTY_LICENSES.md). All three ship in the npm
+tarball: AGPL-3.0-only §4 and §5 require recipients to receive the license; a README alone is not
+a copy of the license.
+
+Local use alone does not trigger an obligation. Copyleft obligations apply to redistribution and
+providing a network service (AGPL §13).
+
+Corresponding TypeScript source ships under `src/` in the same tarball; the complete repository
+is available at <https://github.com/lboel/untangle>.

package/THIRD_PARTY_LICENSES.md

@@ -0,0 +1,29 @@
+# Third-party licenses — @untangle-code/config
+
+Generated by `pnpm third-party-licenses` from this package's installed
+production dependency tree: transitive `dependencies`, across
+workspace edges, with no `devDependencies` included. The generator reads
+each resolved package's `package.json` in `node_modules`; nothing is maintained by hand
+or estimated.
+
+Do not edit manually: `pnpm third-party-licenses --check` fails on drift,
+and `pnpm check-publishable` rejects packages without a current file.
+
+This file exists because `docs/BUILD_PLAN.md`, risk R6, makes
+per-package `THIRD_PARTY_LICENSES.md` a release gate for npm publication.
+
+Untangle itself is **AGPL-3.0-only** (see `LICENSE` and `NOTICE` in
+this package). The packages below are third-party works; their own
+licenses and copyright notices continue to apply unchanged. Workspace
+packages (`@untangle-code/*`) are not listed here; they belong to the same
+work and use the same AGPL-3.0-only license.
+
+## Production dependencies (transitive, 1)
+
+| Package | Version | License | Project |
+| --- | --- | --- | --- |
+| `smol-toml` | 1.8.0 | BSD-3-Clause | `github:squirrelchat/smol-toml` |
+
+The allowlist (MIT / Apache-2.0 / BSD / ISC / …) is checked by
+`scripts/check-licenses.mjs` against this exact tree on every run;
+the GPL family is excluded (architecture.md §2.4, BUILD_PLAN R6).

package/dist/chunker-budget.d.ts

@@ -0,0 +1,58 @@
+/**
+ * Chunk-token budget wiring: `IndexConfig` (spec.md §4.6) →
+ * `@untangle-code/chunker`'s `ChunkerConfigInput.maxTokensPerChunk`.
+ *
+ * spec.md §4.6 defines TWO index-level chunk-size knobs —
+ * `targetChunkTokens` (a soft aim) and `maxChunkTokens` (a hard ceiling) —
+ * with their product defaults (900 / 1500) fixed exactly once, in this
+ * package's `defaults.ts` (`DEFAULT_INDEX_CONFIG`). That is the single
+ * source of truth this file wires onward.
+ *
+ * `@untangle-code/chunker` currently exposes exactly ONE budget knob,
+ * `ChunkerConfigInput.maxTokensPerChunk`, and treats it everywhere as a hard
+ * "must not exceed" ceiling (every comparison in chunker's `split.ts` and
+ * `line-fallback-strategy.ts` is `<=`). The correct mapping is therefore
+ * `maxChunkTokens → maxTokensPerChunk`. `targetChunkTokens` has no
+ * chunker-side counterpart today — the chunker does not currently support
+ * aiming below its hard ceiling — and is deliberately NOT passed here;
+ * smuggling it in as `maxTokensPerChunk` instead would silently turn a soft
+ * aim into the hard ceiling the chunker actually enforces, which is a
+ * different (smaller) budget than spec.md §4.6 configures.
+ *
+ * `@untangle-code/config` deliberately does NOT take a runtime dependency on
+ * `@untangle-code/chunker` for this: config sits below chunker in the
+ * dependency graph (chunker already depends on domain; depending on chunker
+ * from here would invert that layering for the sake of one field mapping),
+ * and chunker is maintained independently of this package. `deriveChunkerBudget`
+ * therefore returns a plain object structurally compatible with
+ * `ChunkerConfigInput` (verified in `chunker-budget.test.ts` against the
+ * fields spec.md and the chunker README actually document) rather than
+ * importing its type.
+ *
+ * Whatever code builds the indexer (constructing `ChunkerConfigInput` to
+ * pass to `@untangle-code/chunker`'s `resolveChunkerConfig`/`chunkFile`) MUST
+ * spread this function's result into that input — e.g.
+ * `resolveChunkerConfig({ ...deriveChunkerBudget(effectiveConfig.index), preparedText })`
+ * — rather than reading `index.maxChunkTokens` directly or (worse) relying
+ * on the chunker's own independent default. That is the one piece of wiring
+ * this fix cannot complete by itself: no indexer package exists in this
+ * repository yet to receive it (see this package's `package.json`
+ * `dependencies`, and `packages/`'s directory listing) — but every future
+ * caller now has exactly one function to call instead of a field name to
+ * remember, which is what keeps a changed config value from silently
+ * failing to reach the chunker.
+ */
+import type { IndexConfig } from "./types.js";
+/** Structurally assignable to `@untangle-code/chunker`'s `ChunkerConfigInput` — see file doc comment. */
+export interface ChunkerBudgetInput {
+    maxTokensPerChunk: number;
+}
+/**
+ * Derives the chunker's token-budget input from the effective `IndexConfig`
+ * (spec.md §4.6). This is the ONLY function in the codebase permitted to
+ * decide which `IndexConfig` field feeds
+ * `ChunkerConfigInput.maxTokensPerChunk` — see file doc comment for why it
+ * is `maxChunkTokens`, not `targetChunkTokens`.
+ */
+export declare function deriveChunkerBudget(index: Pick<IndexConfig, "maxChunkTokens">): ChunkerBudgetInput;
+//# sourceMappingURL=chunker-budget.d.ts.map

package/dist/chunker-budget.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"chunker-budget.d.ts","sourceRoot":"","sources":["../src/chunker-budget.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA2CG;AACH,OAAO,KAAK,EAAE,WAAW,EAAE,MAAM,YAAY,CAAC;AAE9C,yGAAyG;AACzG,MAAM,WAAW,kBAAkB;IACjC,iBAAiB,EAAE,MAAM,CAAC;CAC3B;AAED;;;;;;GAMG;AACH,wBAAgB,mBAAmB,CACjC,KAAK,EAAE,IAAI,CAAC,WAAW,EAAE,gBAAgB,CAAC,GACzC,kBAAkB,CAEpB"}

package/dist/chunker-budget.js

@@ -0,0 +1,11 @@
+/**
+ * Derives the chunker's token-budget input from the effective `IndexConfig`
+ * (spec.md §4.6). This is the ONLY function in the codebase permitted to
+ * decide which `IndexConfig` field feeds
+ * `ChunkerConfigInput.maxTokensPerChunk` — see file doc comment for why it
+ * is `maxChunkTokens`, not `targetChunkTokens`.
+ */
+export function deriveChunkerBudget(index) {
+    return { maxTokensPerChunk: index.maxChunkTokens };
+}
+//# sourceMappingURL=chunker-budget.js.map

package/dist/chunker-budget.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"chunker-budget.js","sourceRoot":"","sources":["../src/chunker-budget.ts"],"names":[],"mappings":"AAmDA;;;;;;GAMG;AACH,MAAM,UAAU,mBAAmB,CACjC,KAA0C;IAE1C,OAAO,EAAE,iBAAiB,EAAE,KAAK,CAAC,cAAc,EAAE,CAAC;AACrD,CAAC"}

package/dist/defaults.d.ts

@@ -0,0 +1,50 @@
+import type { ChangeConfig, ComplexityConfig, EmbeddingConfig, GraphConfig, IndexConfig, PortfolioConfig, QdrantConfig, QualityGateConfig, RawConfigLayer, SearchConfig, StorageConfig, TelemetryConfig } from "./types.js";
+/**
+ * Embedding profile fields that are NOT part of `EmbeddingConfig` (spec.md
+ * §4.5 lists exactly ten fields, none of them `normalization` or
+ * `preparedTextVersion`) but ARE required inputs to
+ * `buildEmbeddingProfileId` (spec.md §5.7). Untangle decision: default
+ * normalization to "none" (no vector post-processing) and mint an explicit
+ * prepared-text format version so a future change to how document text is
+ * assembled can roll `embedding_profile_id` forward deliberately.
+ */
+export declare const DEFAULT_EMBEDDING_NORMALIZATION: "none";
+export declare const PREPARED_TEXT_VERSION: "untangle-prepared-text-v1";
+/** spec.md §4.5 "Defaultprofil für MVP" — Ollama, nomic-embed-text, 768 dims. */
+export declare const DEFAULT_EMBEDDING_CONFIG: EmbeddingConfig;
+/**
+ * Qdrant defaults. spec.md §4.4 defines the shape but not default values;
+ * `managed` mode with no explicit `url` matches product.md §4.1's
+ * zero-config narrative (the CLI starts a managed container and fills `url`
+ * in from that at runtime — this package only supplies the mode default).
+ */
+export declare const DEFAULT_QDRANT_CONFIG: QdrantConfig;
+/** Embedded search for new projects; explicit legacy Qdrant layers retain their backend. */
+export declare const DEFAULT_STORAGE_CONFIG: StorageConfig;
+/** spec.md §4.6; numeric defaults are an Untangle decision, chosen conservatively. */
+export declare const DEFAULT_INDEX_CONFIG: IndexConfig;
+/** Untangle decision (see `types.ts` `SearchConfig` doc comment). */
+export declare const DEFAULT_SEARCH_CONFIG: SearchConfig;
+/** Untangle decision, values taken from architecture.md §17.4's per-query limits. */
+export declare const DEFAULT_GRAPH_CONFIG: GraphConfig;
+/** Untangle decision (see `types.ts` `ComplexityConfig` doc comment). */
+export declare const DEFAULT_COMPLEXITY_CONFIG: ComplexityConfig;
+/** spec.md §17.6 default risk score weights. */
+export declare const DEFAULT_CHANGE_CONFIG: ChangeConfig;
+/** spec.md §4.7 shape; MVP defaults chosen deliberately permissive (warn, not fail). */
+export declare const DEFAULT_QUALITY_GATE_CONFIG: QualityGateConfig;
+/** spec.md §24: "Telemetrie MUSS standardmäßig aus sein." */
+export declare const DEFAULT_TELEMETRY_CONFIG: TelemetryConfig;
+/** portfolio.md §14.4 defaults, spelled out explicitly. */
+export declare const DEFAULT_PORTFOLIO_CONFIG: PortfolioConfig;
+/** Current config schema version this package produces and validates against. */
+export declare const CURRENT_SCHEMA_VERSION: 1;
+/**
+ * The complete product-default layer (spec.md §4.1 layer 6, lowest
+ * priority). Every optional sub-config `EffectiveUntangleConfigV1`
+ * guarantees present is defaulted here; `repositories` and
+ * `contextArtifacts` are deliberately absent (spec.md §4.3: no universal
+ * default repository set exists).
+ */
+export declare const PRODUCT_DEFAULT_CONFIG: RawConfigLayer;
+//# sourceMappingURL=defaults.d.ts.map

package/dist/defaults.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"defaults.d.ts","sourceRoot":"","sources":["../src/defaults.ts"],"names":[],"mappings":"AASA,OAAO,KAAK,EACV,YAAY,EACZ,gBAAgB,EAChB,eAAe,EACf,WAAW,EACX,WAAW,EACX,eAAe,EACf,YAAY,EACZ,iBAAiB,EACjB,cAAc,EACd,YAAY,EACZ,aAAa,EACb,eAAe,EAChB,MAAM,YAAY,CAAC;AAEpB;;;;;;;;GAQG;AACH,eAAO,MAAM,+BAA+B,EAAG,MAAe,CAAC;AAC/D,eAAO,MAAM,qBAAqB,EAAG,2BAAoC,CAAC;AAE1E,iFAAiF;AACjF,eAAO,MAAM,wBAAwB,EAAE,eAYtC,CAAC;AAEF;;;;;GAKG;AACH,eAAO,MAAM,qBAAqB,EAAE,YAOnC,CAAC;AAEF,4FAA4F;AAC5F,eAAO,MAAM,sBAAsB,EAAE,aAGpC,CAAC;AAEF,sFAAsF;AACtF,eAAO,MAAM,oBAAoB,EAAE,WAelC,CAAC;AAEF,qEAAqE;AACrE,eAAO,MAAM,qBAAqB,EAAE,YAanC,CAAC;AAEF,qFAAqF;AACrF,eAAO,MAAM,oBAAoB,EAAE,WAOlC,CAAC;AAEF,yEAAyE;AACzE,eAAO,MAAM,yBAAyB,EAAE,gBAKvC,CAAC;AAEF,gDAAgD;AAChD,eAAO,MAAM,qBAAqB,EAAE,YAenC,CAAC;AAEF,wFAAwF;AACxF,eAAO,MAAM,2BAA2B,EAAE,iBAKzC,CAAC;AAEF,6DAA6D;AAC7D,eAAO,MAAM,wBAAwB,EAAE,eAItC,CAAC;AAEF,2DAA2D;AAC3D,eAAO,MAAM,wBAAwB,EAAE,eAuBtC,CAAC;AAEF,iFAAiF;AACjF,eAAO,MAAM,sBAAsB,EAAG,CAAU,CAAC;AAEjD;;;;;;GAMG;AACH,eAAO,MAAM,sBAAsB,EAAE,cAapC,CAAC"}