@ashx-j/lunr 0.2.11 → 0.2.13

package/dist/core/behavior-preset.d.ts

@@ -1,60 +0,0 @@
-import type { SettingsManager } from "./settings-manager.ts";
-/**
- * Built-in behavior.md presets.
- *
- * Selecting default / humanizer / concise replaces ~/.lunr/agent/behavior.md.
- * Custom leaves the file alone. lunr-behavior re-reads the file every turn, so
- * hand edits apply without a watcher. Fingerprint the body (header comments
- * stripped) to detect drift off a built-in template.
- */
-export declare const BEHAVIOR_PRESET_BRIDGE_SYMBOL: unique symbol;
-export type BehaviorPreset = "default" | "humanizer" | "concise" | "custom";
-export declare const BEHAVIOR_PRESETS: readonly BehaviorPreset[];
-export declare const BEHAVIOR_HEADER = "<!-- lunR behavior rules \u2014 one rule per line. Edit freely or use the behavior tools. -->\n";
-/** Empty on purpose. Default content is a later fill-in. */
-export declare const DEFAULT_BEHAVIOR_PRESET = "";
-export declare const HUMANIZER_BEHAVIOR_PRESET = "# Humanizer (every reply)\n\nWrite like a person. Keep real claims. Never invent facts, names, numbers, dates, quotes, citations, rankings, or sources. Missing detail: ask or simplify. Fiction exempt when inventing is the task.\n\nMatch user voice when known. Personality (opinions, mixed feelings, humor, I, asides, uneven rhythm) only for essays/opinions/personal prose. Technical, legal, reference, factual stay neutral. Never invent facts for voice. Apply on the reply itself (no rewrite pass).\n\n1. Inflated legacy. Avoid: stands/serves as; is a testament/reminder; vital/significant/crucial/pivotal/key role/moment; underscores/highlights its importance/significance; reflects broader; symbolizing its ongoing/enduring/lasting; contributing to the; setting the stage for; marking/shaping the; represents/marks a shift; key turning point; evolving landscape; focal point; indelible mark; deeply rooted.\n2. Status name-drops. Avoid: independent coverage; local/regional/national media outlets; written by a leading expert; active social media presence. Cite only with what was said and where.\n3. Shallow -ing tack-ons. Avoid: highlighting/underscoring/emphasizing; ensuring; reflecting/symbolizing; contributing to; cultivating/fostering; encompassing; showcasing.\n4. Sales tone. Avoid: boasts a; vibrant; rich (figurative); profound; enhancing its; showcasing; exemplifies; commitment to; natural beauty; nestled; in the heart of; groundbreaking (figurative); renowned; breathtaking; must-visit; stunning.\n5. Vague authorities. Avoid: Industry reports; Observers have cited; Experts argue; Some critics argue; several sources/publications (unnamed). Real source or drop claim. Never invent one.\n6. Stock challenges/outlook. Avoid: Despite its... faces several challenges; Despite these challenges; Challenges and Legacy; Future Outlook.\n7. Stock AI words (esp. clustered): Actually; additionally; align with; crucial; delve; emphasizing; enduring; enhance; fostering; garner; gate/gated/gating (figurative only; keep technical gate); highlight (verb); interplay; intricate/intricacies; key (adj); landscape (abstract); pivotal; quietly; showcase; tapestry (abstract); testament; underscore (verb); valuable; vibrant. Also: at the end of the day; when it comes to; in a world where; moving forward; circle back; deep dive; game-changer; double down; take a step back; on the same page; make no mistake; it turns out; let me be clear; navigate (for challenges); lean into; unpack (before analysis); straightforward (filler praise).\n8. Prefer is/are/has. Avoid: serves as/stands as/marks/represents [a]; boasts/features/offers [a].\n9. No not-X-but-Y or clipped negatives (Not only...but; It's not just X, it's Y; \"no guessing\"). Full clause.\n10. No forced groups of three for a complete-sounding list.\n11. No synonym cycling of one subject. No machine-repeated openings. One clear name. Deliberate rhythm OK.\n12. No false from-X-to-Y when ends are not a real scale.\n13. Prefer active voice with a clear subject.\n14. No em/en dash characters, spaced dash pairs, or double-hyphen used as a dash, unless the user uses them. Use period, comma, colon, or parentheses.\n15. No decorative bold on ordinary phrases.\n16. No bold-label lists (`- **Label:** text`). Normal bullets or prose.\n17. Headings in sentence case, not Title Case.\n18. No decorative emojis on headings or bullets.\n19. Straight quotes only, not curly quotes.\n20. No chatbot leftovers: I hope this helps; Of course!; Certainly!; You're absolutely right!; Would you like...; Want me to...?; Should I continue?; let me know; here is a...\n21. No cutoff padding or guessed biography: as of [date]; Up to my last training update; While specific details are limited/scarce; based on available information; not publicly available; maintains a low profile; keeps personal details private; prefers to stay out of the spotlight; likely [grew up/studied/began]; it is believed that. State unknown or omit. Never present a guess as fact.\n22. No sycophantic openers (Great question!; excellent point; absolutely right).\n23. Cut filler: In order to \u2192 To; Due to the fact that \u2192 Because; At this point in time \u2192 Now; In the event that \u2192 If; has the ability to \u2192 can; It is important to note that \u2192 (delete).\n24. One needed qualifier max. Avoid stacks: to be fair; it's also possible; could potentially; might arguably; in some cases it may; this is an inference.\n25. No generic positive endings (future looks bright; exciting times; journey toward excellence; step in the right direction). End on last concrete fact.\n26. Hyphen pairs: keep before a noun when needed (`high-quality report`); drop after (`report is high quality`). Watch: third-party; cross-functional; client-facing; data-driven; decision-making; well-known; high-quality; real-time; long-term; end-to-end.\n27. No deeper-truth framing: The real question is; at its core; in reality; what really matters; fundamentally; the deeper issue; the heart of the matter.\n28. Do not announce the next point: Let's dive in/explore/break this down; here's what you need to know; now let's look at; without further ado; heads up; quick note; before I forget.\n29. Do not restate a heading in the first sentence under it.\n30. Describe current behavior. Prior versions only in changelogs/release notes/migration guides.\n31. No forced punchlines or stacks of dramatic fragments. One short emphatic line OK.\n32. No formulaic sayings: X is the Y of Z; X becomes a trap; X is not a tool but a mirror; the language/currency/architecture of.\n33. No fake-candid hooks: Honestly?; Look; Here's the thing; The thing is; Let's be honest; Real talk.\n34. Do not answer unraised objections: This isn't (mainly) about; I'm not saying/arguing; To be clear; Don't get me wrong; This is not to say; You could argue... but; Some might say... but. Direct claims OK.\n35. Do not reject fake alternatives: A tempting option/approach would be; One might be tempted to; An obvious approach would be; You might think... but; It would be easy to just; Some would suggest. Keep real options a reader might choose.\n\nDo not over-flag alone: polish; mixed register; dry prose without stock tells; formal words outside #7; salutations/sign-offs; one however/additionally; curly quotes alone; one dash alone; one short emphatic sentence; deliberate repeated openings; honestly/look mid-sentence; useful scope/legal/safety limits; real alternatives; unsourced web claims; clean formatting; watched phrases inside quotes, titles, names, or examples under discussion. Several patterns together beat one.\n\nKeep: specific odd details; mixed feelings; era slang; deliberate first person; short/long mix; genuine asides or self-corrections.";
-export declare const CONCISE_BEHAVIOR_PRESET = "# Concise (every reply)\n\nBe extremely concise. Sacrifice grammar for concision.\n\nPlans are not novels. Terminals read bottom-up. Scanning beats reading. Fewer tokens = faster and cheaper.\n\n## Brevity swaps\n| Instead of | Write |\n|---|---|\n| The user will be able to... | User can... |\n| This component is responsible for... | Handles... |\n| In order to achieve this, we need to... | Requires: |\n| It should be noted that... | (delete) |\n\nPrefer: fragments over full sentences; tables over paragraphs; bullets over prose; diagrams over descriptions.\n\n## Output order (always)\n1. Brief overview (2-3 sentences max)\n2. Main content (tables, bullets, diagrams)\n3. Unresolved questions (if any)\n4. Numbered action steps (ALWAYS LAST)\n\nUnresolved questions go before action steps as short bullets. Catch ambiguity before it becomes a bug.\n\n## Action steps (last visible block)\nEnd every non-trivial reply with concrete numbered next steps. Most important = most visible at the bottom.\n\n```\n## Next steps\n1. ...\n2. ...\n```\n\nTrivial yes/no or single-fact answers may skip the scaffold. Any plan, fix, design, or multi-step answer must end on numbered steps.\n\n## Anti-patterns\n| Don't | Do |\n|---|---|\n| Long prose explanations | Bullet points |\n| Nested sub-bullets (3+ levels) | Flat structure, tables |\n| \"Let me explain...\" | Just explain |\n| Repeating context | Reference by ID/name |\n| Hedging language | Direct statements |\n\n## Shape\nBad: The authentication system will need to handle user login. In order to accomplish this, we will need to implement a JWT-based mechanism that allows users to securely log in.\n\nGood:\nAuth: JWT login\n\n| Piece | Detail |\n|---|---|\n| Endpoint | POST /auth/login |\n| Token | JWT, 24h |\n| Guard | verify on protected routes |\n\n## Unresolved questions\n- OAuth provider? (Google, GitHub, both)\n- Session duration?\n\n## Next steps\n1. Add auth module at src/auth/\n2. Add JWT dependency\n3. Implement login endpoint\n4. Add tests";
-export declare function isBehaviorPreset(value: unknown): value is BehaviorPreset;
-export declare function isBuiltinBehaviorPreset(preset: BehaviorPreset): boolean;
-export declare function behaviorFilePath(agentDir?: string): string;
-export declare function normalizeBehaviorBody(text: string): string;
-export declare function builtinBehaviorBody(preset: Exclude<BehaviorPreset, "custom">): string;
-export declare function wrapBehaviorFile(body: string): string;
-export declare function detectBehaviorPreset(fileText: string): BehaviorPreset;
-export declare function readBehaviorFile(agentDir?: string): string;
-export declare function writeBehaviorFile(body: string, agentDir?: string): void;
-export declare function writeBehaviorPreset(preset: Exclude<BehaviorPreset, "custom">, agentDir?: string): void;
-export type ApplyBehaviorPresetResult = {
-    ok: true;
-    preset: BehaviorPreset;
-} | {
-    ok: false;
-    reason: "needs-overwrite";
-};
-/**
- * Persist a preset and, for built-ins, replace behavior.md.
- * Custom never writes. Switching onto a built-in while the file is custom
- * requires `{ overwrite: true }` so the settings UI can confirm first.
- */
-export declare function applyBehaviorPreset(settingsManager: SettingsManager, preset: BehaviorPreset, agentDir?: string, options?: {
-    overwrite?: boolean;
-}): ApplyBehaviorPresetResult;
-/**
- * Align the stored preset with the file.
- * Custom stored always wins (file is the source of truth).
- * A custom file while a built-in is stored flips the setting to custom.
- * A missing/empty file while a non-default built-in is stored restores that template.
- * A different built-in already on disk is adopted (file wins).
- */
-export declare function reconcileBehaviorPreset(settingsManager: SettingsManager, agentDir?: string): BehaviorPreset;
-export interface BehaviorPresetBridge {
-    getPreset(): BehaviorPreset;
-    setPreset(preset: BehaviorPreset): void;
-    isCapExempt(): boolean;
-    /** Fingerprint the current file text; persist custom when a built-in selection drifted. */
-    syncFromFile(fileText: string): BehaviorPreset;
-}
-export declare function registerBehaviorPresetBridge(settingsManager: SettingsManager): void;
-export declare function getBehaviorPresetBridge(): BehaviorPresetBridge | undefined;
-//# sourceMappingURL=behavior-preset.d.ts.map

package/dist/core/behavior-preset.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"behavior-preset.d.ts","sourceRoot":"","sources":["../../src/core/behavior-preset.ts"],"names":[],"mappings":"AAGA,OAAO,KAAK,EAAE,eAAe,EAAE,MAAM,uBAAuB,CAAC;AAE7D;;;;;;;GAOG;AAEH,eAAO,MAAM,6BAA6B,eAAsC,CAAC;AAEjF,MAAM,MAAM,cAAc,GAAG,SAAS,GAAG,WAAW,GAAG,SAAS,GAAG,QAAQ,CAAC;AAE5E,eAAO,MAAM,gBAAgB,EAAE,SAAS,cAAc,EAAkD,CAAC;AAEzG,eAAO,MAAM,eAAe,oGACiE,CAAC;AAE9F,4DAA4D;AAC5D,eAAO,MAAM,uBAAuB,KAAK,CAAC;AAE1C,eAAO,MAAM,yBAAyB,qnNA4C8F,CAAC;AAErI,eAAO,MAAM,uBAAuB,q+DAgEvB,CAAC;AAEd,wBAAgB,gBAAgB,CAAC,KAAK,EAAE,OAAO,GAAG,KAAK,IAAI,cAAc,CAExE;AAED,wBAAgB,uBAAuB,CAAC,MAAM,EAAE,cAAc,GAAG,OAAO,CAEvE;AAED,wBAAgB,gBAAgB,CAAC,QAAQ,GAAE,MAAsB,GAAG,MAAM,CAEzE;AAED,wBAAgB,qBAAqB,CAAC,IAAI,EAAE,MAAM,GAAG,MAAM,CAO1D;AAED,wBAAgB,mBAAmB,CAAC,MAAM,EAAE,OAAO,CAAC,cAAc,EAAE,QAAQ,CAAC,GAAG,MAAM,CAIrF;AAED,wBAAgB,gBAAgB,CAAC,IAAI,EAAE,MAAM,GAAG,MAAM,CAIrD;AAED,wBAAgB,oBAAoB,CAAC,QAAQ,EAAE,MAAM,GAAG,cAAc,CAMrE;AAED,wBAAgB,gBAAgB,CAAC,QAAQ,CAAC,EAAE,MAAM,GAAG,MAAM,CAI1D;AAED,wBAAgB,iBAAiB,CAAC,IAAI,EAAE,MAAM,EAAE,QAAQ,CAAC,EAAE,MAAM,GAAG,IAAI,CAKvE;AAED,wBAAgB,mBAAmB,CAAC,MAAM,EAAE,OAAO,CAAC,cAAc,EAAE,QAAQ,CAAC,EAAE,QAAQ,CAAC,EAAE,MAAM,GAAG,IAAI,CAEtG;AAED,MAAM,MAAM,yBAAyB,GAAG;IAAE,EAAE,EAAE,IAAI,CAAC;IAAC,MAAM,EAAE,cAAc,CAAA;CAAE,GAAG;IAAE,EAAE,EAAE,KAAK,CAAC;IAAC,MAAM,EAAE,iBAAiB,CAAA;CAAE,CAAC;AAExH;;;;GAIG;AACH,wBAAgB,mBAAmB,CAClC,eAAe,EAAE,eAAe,EAChC,MAAM,EAAE,cAAc,EACtB,QAAQ,CAAC,EAAE,MAAM,EACjB,OAAO,GAAE;IAAE,SAAS,CAAC,EAAE,OAAO,CAAA;CAAO,GACnC,yBAAyB,CAY3B;AAED;;;;;;GAMG;AACH,wBAAgB,uBAAuB,CAAC,eAAe,EAAE,eAAe,EAAE,QAAQ,CAAC,EAAE,MAAM,GAAG,cAAc,CAe3G;AAED,MAAM,WAAW,oBAAoB;IACpC,SAAS,IAAI,cAAc,CAAC;IAC5B,SAAS,CAAC,MAAM,EAAE,cAAc,GAAG,IAAI,CAAC;IACxC,WAAW,IAAI,OAAO,CAAC;IACvB,2FAA2F;IAC3F,YAAY,CAAC,QAAQ,EAAE,MAAM,GAAG,cAAc,CAAC;CAC/C;AA4BD,wBAAgB,4BAA4B,CAAC,eAAe,EAAE,eAAe,GAAG,IAAI,CAGnF;AAED,wBAAgB,uBAAuB,IAAI,oBAAoB,GAAG,SAAS,CAE1E","sourcesContent":["import { existsSync, mkdirSync, readFileSync, writeFileSync } from \"node:fs\";\nimport { join } from \"node:path\";\nimport { getAgentDir } from \"../config.ts\";\nimport type { SettingsManager } from \"./settings-manager.ts\";\n\n/**\n * Built-in behavior.md presets.\n *\n * Selecting default / humanizer / concise replaces ~/.lunr/agent/behavior.md.\n * Custom leaves the file alone. lunr-behavior re-reads the file every turn, so\n * hand edits apply without a watcher. Fingerprint the body (header comments\n * stripped) to detect drift off a built-in template.\n */\n\nexport const BEHAVIOR_PRESET_BRIDGE_SYMBOL = Symbol.for(\"@lunr/behavior-preset\");\n\nexport type BehaviorPreset = \"default\" | \"humanizer\" | \"concise\" | \"custom\";\n\nexport const BEHAVIOR_PRESETS: readonly BehaviorPreset[] = [\"default\", \"humanizer\", \"concise\", \"custom\"];\n\nexport const BEHAVIOR_HEADER =\n\t\"<!-- lunR behavior rules — one rule per line. Edit freely or use the behavior tools. -->\\n\";\n\n/** Empty on purpose. Default content is a later fill-in. */\nexport const DEFAULT_BEHAVIOR_PRESET = \"\";\n\nexport const HUMANIZER_BEHAVIOR_PRESET = `# Humanizer (every reply)\n\nWrite like a person. Keep real claims. Never invent facts, names, numbers, dates, quotes, citations, rankings, or sources. Missing detail: ask or simplify. Fiction exempt when inventing is the task.\n\nMatch user voice when known. Personality (opinions, mixed feelings, humor, I, asides, uneven rhythm) only for essays/opinions/personal prose. Technical, legal, reference, factual stay neutral. Never invent facts for voice. Apply on the reply itself (no rewrite pass).\n\n1. Inflated legacy. Avoid: stands/serves as; is a testament/reminder; vital/significant/crucial/pivotal/key role/moment; underscores/highlights its importance/significance; reflects broader; symbolizing its ongoing/enduring/lasting; contributing to the; setting the stage for; marking/shaping the; represents/marks a shift; key turning point; evolving landscape; focal point; indelible mark; deeply rooted.\n2. Status name-drops. Avoid: independent coverage; local/regional/national media outlets; written by a leading expert; active social media presence. Cite only with what was said and where.\n3. Shallow -ing tack-ons. Avoid: highlighting/underscoring/emphasizing; ensuring; reflecting/symbolizing; contributing to; cultivating/fostering; encompassing; showcasing.\n4. Sales tone. Avoid: boasts a; vibrant; rich (figurative); profound; enhancing its; showcasing; exemplifies; commitment to; natural beauty; nestled; in the heart of; groundbreaking (figurative); renowned; breathtaking; must-visit; stunning.\n5. Vague authorities. Avoid: Industry reports; Observers have cited; Experts argue; Some critics argue; several sources/publications (unnamed). Real source or drop claim. Never invent one.\n6. Stock challenges/outlook. Avoid: Despite its... faces several challenges; Despite these challenges; Challenges and Legacy; Future Outlook.\n7. Stock AI words (esp. clustered): Actually; additionally; align with; crucial; delve; emphasizing; enduring; enhance; fostering; garner; gate/gated/gating (figurative only; keep technical gate); highlight (verb); interplay; intricate/intricacies; key (adj); landscape (abstract); pivotal; quietly; showcase; tapestry (abstract); testament; underscore (verb); valuable; vibrant. Also: at the end of the day; when it comes to; in a world where; moving forward; circle back; deep dive; game-changer; double down; take a step back; on the same page; make no mistake; it turns out; let me be clear; navigate (for challenges); lean into; unpack (before analysis); straightforward (filler praise).\n8. Prefer is/are/has. Avoid: serves as/stands as/marks/represents [a]; boasts/features/offers [a].\n9. No not-X-but-Y or clipped negatives (Not only...but; It's not just X, it's Y; \"no guessing\"). Full clause.\n10. No forced groups of three for a complete-sounding list.\n11. No synonym cycling of one subject. No machine-repeated openings. One clear name. Deliberate rhythm OK.\n12. No false from-X-to-Y when ends are not a real scale.\n13. Prefer active voice with a clear subject.\n14. No em/en dash characters, spaced dash pairs, or double-hyphen used as a dash, unless the user uses them. Use period, comma, colon, or parentheses.\n15. No decorative bold on ordinary phrases.\n16. No bold-label lists (\\`- **Label:** text\\`). Normal bullets or prose.\n17. Headings in sentence case, not Title Case.\n18. No decorative emojis on headings or bullets.\n19. Straight quotes only, not curly quotes.\n20. No chatbot leftovers: I hope this helps; Of course!; Certainly!; You're absolutely right!; Would you like...; Want me to...?; Should I continue?; let me know; here is a...\n21. No cutoff padding or guessed biography: as of [date]; Up to my last training update; While specific details are limited/scarce; based on available information; not publicly available; maintains a low profile; keeps personal details private; prefers to stay out of the spotlight; likely [grew up/studied/began]; it is believed that. State unknown or omit. Never present a guess as fact.\n22. No sycophantic openers (Great question!; excellent point; absolutely right).\n23. Cut filler: In order to → To; Due to the fact that → Because; At this point in time → Now; In the event that → If; has the ability to → can; It is important to note that → (delete).\n24. One needed qualifier max. Avoid stacks: to be fair; it's also possible; could potentially; might arguably; in some cases it may; this is an inference.\n25. No generic positive endings (future looks bright; exciting times; journey toward excellence; step in the right direction). End on last concrete fact.\n26. Hyphen pairs: keep before a noun when needed (\\`high-quality report\\`); drop after (\\`report is high quality\\`). Watch: third-party; cross-functional; client-facing; data-driven; decision-making; well-known; high-quality; real-time; long-term; end-to-end.\n27. No deeper-truth framing: The real question is; at its core; in reality; what really matters; fundamentally; the deeper issue; the heart of the matter.\n28. Do not announce the next point: Let's dive in/explore/break this down; here's what you need to know; now let's look at; without further ado; heads up; quick note; before I forget.\n29. Do not restate a heading in the first sentence under it.\n30. Describe current behavior. Prior versions only in changelogs/release notes/migration guides.\n31. No forced punchlines or stacks of dramatic fragments. One short emphatic line OK.\n32. No formulaic sayings: X is the Y of Z; X becomes a trap; X is not a tool but a mirror; the language/currency/architecture of.\n33. No fake-candid hooks: Honestly?; Look; Here's the thing; The thing is; Let's be honest; Real talk.\n34. Do not answer unraised objections: This isn't (mainly) about; I'm not saying/arguing; To be clear; Don't get me wrong; This is not to say; You could argue... but; Some might say... but. Direct claims OK.\n35. Do not reject fake alternatives: A tempting option/approach would be; One might be tempted to; An obvious approach would be; You might think... but; It would be easy to just; Some would suggest. Keep real options a reader might choose.\n\nDo not over-flag alone: polish; mixed register; dry prose without stock tells; formal words outside #7; salutations/sign-offs; one however/additionally; curly quotes alone; one dash alone; one short emphatic sentence; deliberate repeated openings; honestly/look mid-sentence; useful scope/legal/safety limits; real alternatives; unsourced web claims; clean formatting; watched phrases inside quotes, titles, names, or examples under discussion. Several patterns together beat one.\n\nKeep: specific odd details; mixed feelings; era slang; deliberate first person; short/long mix; genuine asides or self-corrections.`;\n\nexport const CONCISE_BEHAVIOR_PRESET = `# Concise (every reply)\n\nBe extremely concise. Sacrifice grammar for concision.\n\nPlans are not novels. Terminals read bottom-up. Scanning beats reading. Fewer tokens = faster and cheaper.\n\n## Brevity swaps\n| Instead of | Write |\n|---|---|\n| The user will be able to... | User can... |\n| This component is responsible for... | Handles... |\n| In order to achieve this, we need to... | Requires: |\n| It should be noted that... | (delete) |\n\nPrefer: fragments over full sentences; tables over paragraphs; bullets over prose; diagrams over descriptions.\n\n## Output order (always)\n1. Brief overview (2-3 sentences max)\n2. Main content (tables, bullets, diagrams)\n3. Unresolved questions (if any)\n4. Numbered action steps (ALWAYS LAST)\n\nUnresolved questions go before action steps as short bullets. Catch ambiguity before it becomes a bug.\n\n## Action steps (last visible block)\nEnd every non-trivial reply with concrete numbered next steps. Most important = most visible at the bottom.\n\n\\`\\`\\`\n## Next steps\n1. ...\n2. ...\n\\`\\`\\`\n\nTrivial yes/no or single-fact answers may skip the scaffold. Any plan, fix, design, or multi-step answer must end on numbered steps.\n\n## Anti-patterns\n| Don't | Do |\n|---|---|\n| Long prose explanations | Bullet points |\n| Nested sub-bullets (3+ levels) | Flat structure, tables |\n| \"Let me explain...\" | Just explain |\n| Repeating context | Reference by ID/name |\n| Hedging language | Direct statements |\n\n## Shape\nBad: The authentication system will need to handle user login. In order to accomplish this, we will need to implement a JWT-based mechanism that allows users to securely log in.\n\nGood:\nAuth: JWT login\n\n| Piece | Detail |\n|---|---|\n| Endpoint | POST /auth/login |\n| Token | JWT, 24h |\n| Guard | verify on protected routes |\n\n## Unresolved questions\n- OAuth provider? (Google, GitHub, both)\n- Session duration?\n\n## Next steps\n1. Add auth module at src/auth/\n2. Add JWT dependency\n3. Implement login endpoint\n4. Add tests`;\n\nexport function isBehaviorPreset(value: unknown): value is BehaviorPreset {\n\treturn value === \"default\" || value === \"humanizer\" || value === \"concise\" || value === \"custom\";\n}\n\nexport function isBuiltinBehaviorPreset(preset: BehaviorPreset): boolean {\n\treturn preset === \"default\" || preset === \"humanizer\" || preset === \"concise\";\n}\n\nexport function behaviorFilePath(agentDir: string = getAgentDir()): string {\n\treturn join(agentDir, \"behavior.md\");\n}\n\nexport function normalizeBehaviorBody(text: string): string {\n\treturn text\n\t\t.replace(/\\r\\n/g, \"\\n\")\n\t\t.split(\"\\n\")\n\t\t.filter((line) => !line.startsWith(\"<!--\"))\n\t\t.join(\"\\n\")\n\t\t.trim();\n}\n\nexport function builtinBehaviorBody(preset: Exclude<BehaviorPreset, \"custom\">): string {\n\tif (preset === \"humanizer\") return HUMANIZER_BEHAVIOR_PRESET;\n\tif (preset === \"concise\") return CONCISE_BEHAVIOR_PRESET;\n\treturn DEFAULT_BEHAVIOR_PRESET;\n}\n\nexport function wrapBehaviorFile(body: string): string {\n\tconst trimmed = body.replace(/\\r\\n/g, \"\\n\").trim();\n\tif (!trimmed) return BEHAVIOR_HEADER;\n\treturn `${BEHAVIOR_HEADER}${trimmed}\\n`;\n}\n\nexport function detectBehaviorPreset(fileText: string): BehaviorPreset {\n\tconst body = normalizeBehaviorBody(fileText);\n\tif (body === normalizeBehaviorBody(HUMANIZER_BEHAVIOR_PRESET)) return \"humanizer\";\n\tif (body === normalizeBehaviorBody(CONCISE_BEHAVIOR_PRESET)) return \"concise\";\n\tif (body === normalizeBehaviorBody(DEFAULT_BEHAVIOR_PRESET)) return \"default\";\n\treturn \"custom\";\n}\n\nexport function readBehaviorFile(agentDir?: string): string {\n\tconst file = behaviorFilePath(agentDir);\n\tif (!existsSync(file)) return \"\";\n\treturn readFileSync(file, \"utf-8\");\n}\n\nexport function writeBehaviorFile(body: string, agentDir?: string): void {\n\tconst file = behaviorFilePath(agentDir);\n\tconst dir = agentDir ?? getAgentDir();\n\tif (!existsSync(dir)) mkdirSync(dir, { recursive: true });\n\twriteFileSync(file, wrapBehaviorFile(body), \"utf-8\");\n}\n\nexport function writeBehaviorPreset(preset: Exclude<BehaviorPreset, \"custom\">, agentDir?: string): void {\n\twriteBehaviorFile(builtinBehaviorBody(preset), agentDir);\n}\n\nexport type ApplyBehaviorPresetResult = { ok: true; preset: BehaviorPreset } | { ok: false; reason: \"needs-overwrite\" };\n\n/**\n * Persist a preset and, for built-ins, replace behavior.md.\n * Custom never writes. Switching onto a built-in while the file is custom\n * requires `{ overwrite: true }` so the settings UI can confirm first.\n */\nexport function applyBehaviorPreset(\n\tsettingsManager: SettingsManager,\n\tpreset: BehaviorPreset,\n\tagentDir?: string,\n\toptions: { overwrite?: boolean } = {},\n): ApplyBehaviorPresetResult {\n\tif (preset === \"custom\") {\n\t\tsettingsManager.setBehaviorPreset(\"custom\");\n\t\treturn { ok: true, preset: \"custom\" };\n\t}\n\tconst fingerprint = detectBehaviorPreset(readBehaviorFile(agentDir));\n\tif (fingerprint === \"custom\" && !options.overwrite) {\n\t\treturn { ok: false, reason: \"needs-overwrite\" };\n\t}\n\twriteBehaviorPreset(preset, agentDir);\n\tsettingsManager.setBehaviorPreset(preset);\n\treturn { ok: true, preset };\n}\n\n/**\n * Align the stored preset with the file.\n * Custom stored always wins (file is the source of truth).\n * A custom file while a built-in is stored flips the setting to custom.\n * A missing/empty file while a non-default built-in is stored restores that template.\n * A different built-in already on disk is adopted (file wins).\n */\nexport function reconcileBehaviorPreset(settingsManager: SettingsManager, agentDir?: string): BehaviorPreset {\n\tconst stored = settingsManager.getBehaviorPreset();\n\tconst fingerprint = detectBehaviorPreset(readBehaviorFile(agentDir));\n\tif (stored === \"custom\") return \"custom\";\n\tif (fingerprint === stored) return stored;\n\tif (fingerprint === \"custom\") {\n\t\tsettingsManager.setBehaviorPreset(\"custom\");\n\t\treturn \"custom\";\n\t}\n\tif (fingerprint === \"default\" && stored !== \"default\") {\n\t\twriteBehaviorPreset(stored, agentDir);\n\t\treturn stored;\n\t}\n\tsettingsManager.setBehaviorPreset(fingerprint);\n\treturn fingerprint;\n}\n\nexport interface BehaviorPresetBridge {\n\tgetPreset(): BehaviorPreset;\n\tsetPreset(preset: BehaviorPreset): void;\n\tisCapExempt(): boolean;\n\t/** Fingerprint the current file text; persist custom when a built-in selection drifted. */\n\tsyncFromFile(fileText: string): BehaviorPreset;\n}\n\nlet activeSettingsManager: SettingsManager | undefined;\n\nconst bridge: BehaviorPresetBridge = {\n\tgetPreset(): BehaviorPreset {\n\t\treturn activeSettingsManager?.getBehaviorPreset() ?? \"default\";\n\t},\n\tsetPreset(preset: BehaviorPreset): void {\n\t\tactiveSettingsManager?.setBehaviorPreset(preset);\n\t},\n\tisCapExempt(): boolean {\n\t\tconst preset = activeSettingsManager?.getBehaviorPreset() ?? \"default\";\n\t\treturn isBuiltinBehaviorPreset(preset);\n\t},\n\tsyncFromFile(fileText: string): BehaviorPreset {\n\t\tconst fingerprint = detectBehaviorPreset(fileText);\n\t\tconst stored = activeSettingsManager?.getBehaviorPreset() ?? \"default\";\n\t\t// Per-turn: only flip a built-in to custom when the file drifted. Restoring a\n\t\t// missing template or adopting another built-in is reconcileBehaviorPreset.\n\t\tif (stored !== \"custom\" && fingerprint === \"custom\") {\n\t\t\tactiveSettingsManager?.setBehaviorPreset(\"custom\");\n\t\t\treturn \"custom\";\n\t\t}\n\t\treturn stored;\n\t},\n};\n\nexport function registerBehaviorPresetBridge(settingsManager: SettingsManager): void {\n\tactiveSettingsManager = settingsManager;\n\t(globalThis as Record<symbol, unknown>)[BEHAVIOR_PRESET_BRIDGE_SYMBOL] = bridge;\n}\n\nexport function getBehaviorPresetBridge(): BehaviorPresetBridge | undefined {\n\treturn (globalThis as Record<symbol, unknown>)[BEHAVIOR_PRESET_BRIDGE_SYMBOL] as BehaviorPresetBridge | undefined;\n}\n"]}

package/dist/core/behavior-preset.js

@@ -1,257 +0,0 @@
-import { existsSync, mkdirSync, readFileSync, writeFileSync } from "node:fs";
-import { join } from "node:path";
-import { getAgentDir } from "../config.js";
-/**
- * Built-in behavior.md presets.
- *
- * Selecting default / humanizer / concise replaces ~/.lunr/agent/behavior.md.
- * Custom leaves the file alone. lunr-behavior re-reads the file every turn, so
- * hand edits apply without a watcher. Fingerprint the body (header comments
- * stripped) to detect drift off a built-in template.
- */
-export const BEHAVIOR_PRESET_BRIDGE_SYMBOL = Symbol.for("@lunr/behavior-preset");
-export const BEHAVIOR_PRESETS = ["default", "humanizer", "concise", "custom"];
-export const BEHAVIOR_HEADER = "<!-- lunR behavior rules — one rule per line. Edit freely or use the behavior tools. -->\n";
-/** Empty on purpose. Default content is a later fill-in. */
-export const DEFAULT_BEHAVIOR_PRESET = "";
-export const HUMANIZER_BEHAVIOR_PRESET = `# Humanizer (every reply)
-
-Write like a person. Keep real claims. Never invent facts, names, numbers, dates, quotes, citations, rankings, or sources. Missing detail: ask or simplify. Fiction exempt when inventing is the task.
-
-Match user voice when known. Personality (opinions, mixed feelings, humor, I, asides, uneven rhythm) only for essays/opinions/personal prose. Technical, legal, reference, factual stay neutral. Never invent facts for voice. Apply on the reply itself (no rewrite pass).
-
-1. Inflated legacy. Avoid: stands/serves as; is a testament/reminder; vital/significant/crucial/pivotal/key role/moment; underscores/highlights its importance/significance; reflects broader; symbolizing its ongoing/enduring/lasting; contributing to the; setting the stage for; marking/shaping the; represents/marks a shift; key turning point; evolving landscape; focal point; indelible mark; deeply rooted.
-2. Status name-drops. Avoid: independent coverage; local/regional/national media outlets; written by a leading expert; active social media presence. Cite only with what was said and where.
-3. Shallow -ing tack-ons. Avoid: highlighting/underscoring/emphasizing; ensuring; reflecting/symbolizing; contributing to; cultivating/fostering; encompassing; showcasing.
-4. Sales tone. Avoid: boasts a; vibrant; rich (figurative); profound; enhancing its; showcasing; exemplifies; commitment to; natural beauty; nestled; in the heart of; groundbreaking (figurative); renowned; breathtaking; must-visit; stunning.
-5. Vague authorities. Avoid: Industry reports; Observers have cited; Experts argue; Some critics argue; several sources/publications (unnamed). Real source or drop claim. Never invent one.
-6. Stock challenges/outlook. Avoid: Despite its... faces several challenges; Despite these challenges; Challenges and Legacy; Future Outlook.
-7. Stock AI words (esp. clustered): Actually; additionally; align with; crucial; delve; emphasizing; enduring; enhance; fostering; garner; gate/gated/gating (figurative only; keep technical gate); highlight (verb); interplay; intricate/intricacies; key (adj); landscape (abstract); pivotal; quietly; showcase; tapestry (abstract); testament; underscore (verb); valuable; vibrant. Also: at the end of the day; when it comes to; in a world where; moving forward; circle back; deep dive; game-changer; double down; take a step back; on the same page; make no mistake; it turns out; let me be clear; navigate (for challenges); lean into; unpack (before analysis); straightforward (filler praise).
-8. Prefer is/are/has. Avoid: serves as/stands as/marks/represents [a]; boasts/features/offers [a].
-9. No not-X-but-Y or clipped negatives (Not only...but; It's not just X, it's Y; "no guessing"). Full clause.
-10. No forced groups of three for a complete-sounding list.
-11. No synonym cycling of one subject. No machine-repeated openings. One clear name. Deliberate rhythm OK.
-12. No false from-X-to-Y when ends are not a real scale.
-13. Prefer active voice with a clear subject.
-14. No em/en dash characters, spaced dash pairs, or double-hyphen used as a dash, unless the user uses them. Use period, comma, colon, or parentheses.
-15. No decorative bold on ordinary phrases.
-16. No bold-label lists (\`- **Label:** text\`). Normal bullets or prose.
-17. Headings in sentence case, not Title Case.
-18. No decorative emojis on headings or bullets.
-19. Straight quotes only, not curly quotes.
-20. No chatbot leftovers: I hope this helps; Of course!; Certainly!; You're absolutely right!; Would you like...; Want me to...?; Should I continue?; let me know; here is a...
-21. No cutoff padding or guessed biography: as of [date]; Up to my last training update; While specific details are limited/scarce; based on available information; not publicly available; maintains a low profile; keeps personal details private; prefers to stay out of the spotlight; likely [grew up/studied/began]; it is believed that. State unknown or omit. Never present a guess as fact.
-22. No sycophantic openers (Great question!; excellent point; absolutely right).
-23. Cut filler: In order to → To; Due to the fact that → Because; At this point in time → Now; In the event that → If; has the ability to → can; It is important to note that → (delete).
-24. One needed qualifier max. Avoid stacks: to be fair; it's also possible; could potentially; might arguably; in some cases it may; this is an inference.
-25. No generic positive endings (future looks bright; exciting times; journey toward excellence; step in the right direction). End on last concrete fact.
-26. Hyphen pairs: keep before a noun when needed (\`high-quality report\`); drop after (\`report is high quality\`). Watch: third-party; cross-functional; client-facing; data-driven; decision-making; well-known; high-quality; real-time; long-term; end-to-end.
-27. No deeper-truth framing: The real question is; at its core; in reality; what really matters; fundamentally; the deeper issue; the heart of the matter.
-28. Do not announce the next point: Let's dive in/explore/break this down; here's what you need to know; now let's look at; without further ado; heads up; quick note; before I forget.
-29. Do not restate a heading in the first sentence under it.
-30. Describe current behavior. Prior versions only in changelogs/release notes/migration guides.
-31. No forced punchlines or stacks of dramatic fragments. One short emphatic line OK.
-32. No formulaic sayings: X is the Y of Z; X becomes a trap; X is not a tool but a mirror; the language/currency/architecture of.
-33. No fake-candid hooks: Honestly?; Look; Here's the thing; The thing is; Let's be honest; Real talk.
-34. Do not answer unraised objections: This isn't (mainly) about; I'm not saying/arguing; To be clear; Don't get me wrong; This is not to say; You could argue... but; Some might say... but. Direct claims OK.
-35. Do not reject fake alternatives: A tempting option/approach would be; One might be tempted to; An obvious approach would be; You might think... but; It would be easy to just; Some would suggest. Keep real options a reader might choose.
-
-Do not over-flag alone: polish; mixed register; dry prose without stock tells; formal words outside #7; salutations/sign-offs; one however/additionally; curly quotes alone; one dash alone; one short emphatic sentence; deliberate repeated openings; honestly/look mid-sentence; useful scope/legal/safety limits; real alternatives; unsourced web claims; clean formatting; watched phrases inside quotes, titles, names, or examples under discussion. Several patterns together beat one.
-
-Keep: specific odd details; mixed feelings; era slang; deliberate first person; short/long mix; genuine asides or self-corrections.`;
-export const CONCISE_BEHAVIOR_PRESET = `# Concise (every reply)
-
-Be extremely concise. Sacrifice grammar for concision.
-
-Plans are not novels. Terminals read bottom-up. Scanning beats reading. Fewer tokens = faster and cheaper.
-
-## Brevity swaps
-| Instead of | Write |
-|---|---|
-| The user will be able to... | User can... |
-| This component is responsible for... | Handles... |
-| In order to achieve this, we need to... | Requires: |
-| It should be noted that... | (delete) |
-
-Prefer: fragments over full sentences; tables over paragraphs; bullets over prose; diagrams over descriptions.
-
-## Output order (always)
-1. Brief overview (2-3 sentences max)
-2. Main content (tables, bullets, diagrams)
-3. Unresolved questions (if any)
-4. Numbered action steps (ALWAYS LAST)
-
-Unresolved questions go before action steps as short bullets. Catch ambiguity before it becomes a bug.
-
-## Action steps (last visible block)
-End every non-trivial reply with concrete numbered next steps. Most important = most visible at the bottom.
-
-\`\`\`
-## Next steps
-1. ...
-2. ...
-\`\`\`
-
-Trivial yes/no or single-fact answers may skip the scaffold. Any plan, fix, design, or multi-step answer must end on numbered steps.
-
-## Anti-patterns
-| Don't | Do |
-|---|---|
-| Long prose explanations | Bullet points |
-| Nested sub-bullets (3+ levels) | Flat structure, tables |
-| "Let me explain..." | Just explain |
-| Repeating context | Reference by ID/name |
-| Hedging language | Direct statements |
-
-## Shape
-Bad: The authentication system will need to handle user login. In order to accomplish this, we will need to implement a JWT-based mechanism that allows users to securely log in.
-
-Good:
-Auth: JWT login
-
-| Piece | Detail |
-|---|---|
-| Endpoint | POST /auth/login |
-| Token | JWT, 24h |
-| Guard | verify on protected routes |
-
-## Unresolved questions
-- OAuth provider? (Google, GitHub, both)
-- Session duration?
-
-## Next steps
-1. Add auth module at src/auth/
-2. Add JWT dependency
-3. Implement login endpoint
-4. Add tests`;
-export function isBehaviorPreset(value) {
-    return value === "default" || value === "humanizer" || value === "concise" || value === "custom";
-}
-export function isBuiltinBehaviorPreset(preset) {
-    return preset === "default" || preset === "humanizer" || preset === "concise";
-}
-export function behaviorFilePath(agentDir = getAgentDir()) {
-    return join(agentDir, "behavior.md");
-}
-export function normalizeBehaviorBody(text) {
-    return text
-        .replace(/\r\n/g, "\n")
-        .split("\n")
-        .filter((line) => !line.startsWith("<!--"))
-        .join("\n")
-        .trim();
-}
-export function builtinBehaviorBody(preset) {
-    if (preset === "humanizer")
-        return HUMANIZER_BEHAVIOR_PRESET;
-    if (preset === "concise")
-        return CONCISE_BEHAVIOR_PRESET;
-    return DEFAULT_BEHAVIOR_PRESET;
-}
-export function wrapBehaviorFile(body) {
-    const trimmed = body.replace(/\r\n/g, "\n").trim();
-    if (!trimmed)
-        return BEHAVIOR_HEADER;
-    return `${BEHAVIOR_HEADER}${trimmed}\n`;
-}
-export function detectBehaviorPreset(fileText) {
-    const body = normalizeBehaviorBody(fileText);
-    if (body === normalizeBehaviorBody(HUMANIZER_BEHAVIOR_PRESET))
-        return "humanizer";
-    if (body === normalizeBehaviorBody(CONCISE_BEHAVIOR_PRESET))
-        return "concise";
-    if (body === normalizeBehaviorBody(DEFAULT_BEHAVIOR_PRESET))
-        return "default";
-    return "custom";
-}
-export function readBehaviorFile(agentDir) {
-    const file = behaviorFilePath(agentDir);
-    if (!existsSync(file))
-        return "";
-    return readFileSync(file, "utf-8");
-}
-export function writeBehaviorFile(body, agentDir) {
-    const file = behaviorFilePath(agentDir);
-    const dir = agentDir ?? getAgentDir();
-    if (!existsSync(dir))
-        mkdirSync(dir, { recursive: true });
-    writeFileSync(file, wrapBehaviorFile(body), "utf-8");
-}
-export function writeBehaviorPreset(preset, agentDir) {
-    writeBehaviorFile(builtinBehaviorBody(preset), agentDir);
-}
-/**
- * Persist a preset and, for built-ins, replace behavior.md.
- * Custom never writes. Switching onto a built-in while the file is custom
- * requires `{ overwrite: true }` so the settings UI can confirm first.
- */
-export function applyBehaviorPreset(settingsManager, preset, agentDir, options = {}) {
-    if (preset === "custom") {
-        settingsManager.setBehaviorPreset("custom");
-        return { ok: true, preset: "custom" };
-    }
-    const fingerprint = detectBehaviorPreset(readBehaviorFile(agentDir));
-    if (fingerprint === "custom" && !options.overwrite) {
-        return { ok: false, reason: "needs-overwrite" };
-    }
-    writeBehaviorPreset(preset, agentDir);
-    settingsManager.setBehaviorPreset(preset);
-    return { ok: true, preset };
-}
-/**
- * Align the stored preset with the file.
- * Custom stored always wins (file is the source of truth).
- * A custom file while a built-in is stored flips the setting to custom.
- * A missing/empty file while a non-default built-in is stored restores that template.
- * A different built-in already on disk is adopted (file wins).
- */
-export function reconcileBehaviorPreset(settingsManager, agentDir) {
-    const stored = settingsManager.getBehaviorPreset();
-    const fingerprint = detectBehaviorPreset(readBehaviorFile(agentDir));
-    if (stored === "custom")
-        return "custom";
-    if (fingerprint === stored)
-        return stored;
-    if (fingerprint === "custom") {
-        settingsManager.setBehaviorPreset("custom");
-        return "custom";
-    }
-    if (fingerprint === "default" && stored !== "default") {
-        writeBehaviorPreset(stored, agentDir);
-        return stored;
-    }
-    settingsManager.setBehaviorPreset(fingerprint);
-    return fingerprint;
-}
-let activeSettingsManager;
-const bridge = {
-    getPreset() {
-        return activeSettingsManager?.getBehaviorPreset() ?? "default";
-    },
-    setPreset(preset) {
-        activeSettingsManager?.setBehaviorPreset(preset);
-    },
-    isCapExempt() {
-        const preset = activeSettingsManager?.getBehaviorPreset() ?? "default";
-        return isBuiltinBehaviorPreset(preset);
-    },
-    syncFromFile(fileText) {
-        const fingerprint = detectBehaviorPreset(fileText);
-        const stored = activeSettingsManager?.getBehaviorPreset() ?? "default";
-        // Per-turn: only flip a built-in to custom when the file drifted. Restoring a
-        // missing template or adopting another built-in is reconcileBehaviorPreset.
-        if (stored !== "custom" && fingerprint === "custom") {
-            activeSettingsManager?.setBehaviorPreset("custom");
-            return "custom";
-        }
-        return stored;
-    },
-};
-export function registerBehaviorPresetBridge(settingsManager) {
-    activeSettingsManager = settingsManager;
-    globalThis[BEHAVIOR_PRESET_BRIDGE_SYMBOL] = bridge;
-}
-export function getBehaviorPresetBridge() {
-    return globalThis[BEHAVIOR_PRESET_BRIDGE_SYMBOL];
-}
-//# sourceMappingURL=behavior-preset.js.map

package/dist/core/behavior-preset.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"behavior-preset.js","sourceRoot":"","sources":["../../src/core/behavior-preset.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,UAAU,EAAE,SAAS,EAAE,YAAY,EAAE,aAAa,EAAE,MAAM,SAAS,CAAC;AAC7E,OAAO,EAAE,IAAI,EAAE,MAAM,WAAW,CAAC;AACjC,OAAO,EAAE,WAAW,EAAE,MAAM,cAAc,CAAC;AAG3C;;;;;;;GAOG;AAEH,MAAM,CAAC,MAAM,6BAA6B,GAAG,MAAM,CAAC,GAAG,CAAC,uBAAuB,CAAC,CAAC;AAIjF,MAAM,CAAC,MAAM,gBAAgB,GAA8B,CAAC,SAAS,EAAE,WAAW,EAAE,SAAS,EAAE,QAAQ,CAAC,CAAC;AAEzG,MAAM,CAAC,MAAM,eAAe,GAC3B,8FAA4F,CAAC;AAE9F,4DAA4D;AAC5D,MAAM,CAAC,MAAM,uBAAuB,GAAG,EAAE,CAAC;AAE1C,MAAM,CAAC,MAAM,yBAAyB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;oIA4C2F,CAAC;AAErI,MAAM,CAAC,MAAM,uBAAuB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;aAgE1B,CAAC;AAEd,MAAM,UAAU,gBAAgB,CAAC,KAAc,EAA2B;IACzE,OAAO,KAAK,KAAK,SAAS,IAAI,KAAK,KAAK,WAAW,IAAI,KAAK,KAAK,SAAS,IAAI,KAAK,KAAK,QAAQ,CAAC;AAAA,CACjG;AAED,MAAM,UAAU,uBAAuB,CAAC,MAAsB,EAAW;IACxE,OAAO,MAAM,KAAK,SAAS,IAAI,MAAM,KAAK,WAAW,IAAI,MAAM,KAAK,SAAS,CAAC;AAAA,CAC9E;AAED,MAAM,UAAU,gBAAgB,CAAC,QAAQ,GAAW,WAAW,EAAE,EAAU;IAC1E,OAAO,IAAI,CAAC,QAAQ,EAAE,aAAa,CAAC,CAAC;AAAA,CACrC;AAED,MAAM,UAAU,qBAAqB,CAAC,IAAY,EAAU;IAC3D,OAAO,IAAI;SACT,OAAO,CAAC,OAAO,EAAE,IAAI,CAAC;SACtB,KAAK,CAAC,IAAI,CAAC;SACX,MAAM,CAAC,CAAC,IAAI,EAAE,EAAE,CAAC,CAAC,IAAI,CAAC,UAAU,CAAC,MAAM,CAAC,CAAC;SAC1C,IAAI,CAAC,IAAI,CAAC;SACV,IAAI,EAAE,CAAC;AAAA,CACT;AAED,MAAM,UAAU,mBAAmB,CAAC,MAAyC,EAAU;IACtF,IAAI,MAAM,KAAK,WAAW;QAAE,OAAO,yBAAyB,CAAC;IAC7D,IAAI,MAAM,KAAK,SAAS;QAAE,OAAO,uBAAuB,CAAC;IACzD,OAAO,uBAAuB,CAAC;AAAA,CAC/B;AAED,MAAM,UAAU,gBAAgB,CAAC,IAAY,EAAU;IACtD,MAAM,OAAO,GAAG,IAAI,CAAC,OAAO,CAAC,OAAO,EAAE,IAAI,CAAC,CAAC,IAAI,EAAE,CAAC;IACnD,IAAI,CAAC,OAAO;QAAE,OAAO,eAAe,CAAC;IACrC,OAAO,GAAG,eAAe,GAAG,OAAO,IAAI,CAAC;AAAA,CACxC;AAED,MAAM,UAAU,oBAAoB,CAAC,QAAgB,EAAkB;IACtE,MAAM,IAAI,GAAG,qBAAqB,CAAC,QAAQ,CAAC,CAAC;IAC7C,IAAI,IAAI,KAAK,qBAAqB,CAAC,yBAAyB,CAAC;QAAE,OAAO,WAAW,CAAC;IAClF,IAAI,IAAI,KAAK,qBAAqB,CAAC,uBAAuB,CAAC;QAAE,OAAO,SAAS,CAAC;IAC9E,IAAI,IAAI,KAAK,qBAAqB,CAAC,uBAAuB,CAAC;QAAE,OAAO,SAAS,CAAC;IAC9E,OAAO,QAAQ,CAAC;AAAA,CAChB;AAED,MAAM,UAAU,gBAAgB,CAAC,QAAiB,EAAU;IAC3D,MAAM,IAAI,GAAG,gBAAgB,CAAC,QAAQ,CAAC,CAAC;IACxC,IAAI,CAAC,UAAU,CAAC,IAAI,CAAC;QAAE,OAAO,EAAE,CAAC;IACjC,OAAO,YAAY,CAAC,IAAI,EAAE,OAAO,CAAC,CAAC;AAAA,CACnC;AAED,MAAM,UAAU,iBAAiB,CAAC,IAAY,EAAE,QAAiB,EAAQ;IACxE,MAAM,IAAI,GAAG,gBAAgB,CAAC,QAAQ,CAAC,CAAC;IACxC,MAAM,GAAG,GAAG,QAAQ,IAAI,WAAW,EAAE,CAAC;IACtC,IAAI,CAAC,UAAU,CAAC,GAAG,CAAC;QAAE,SAAS,CAAC,GAAG,EAAE,EAAE,SAAS,EAAE,IAAI,EAAE,CAAC,CAAC;IAC1D,aAAa,CAAC,IAAI,EAAE,gBAAgB,CAAC,IAAI,CAAC,EAAE,OAAO,CAAC,CAAC;AAAA,CACrD;AAED,MAAM,UAAU,mBAAmB,CAAC,MAAyC,EAAE,QAAiB,EAAQ;IACvG,iBAAiB,CAAC,mBAAmB,CAAC,MAAM,CAAC,EAAE,QAAQ,CAAC,CAAC;AAAA,CACzD;AAID;;;;GAIG;AACH,MAAM,UAAU,mBAAmB,CAClC,eAAgC,EAChC,MAAsB,EACtB,QAAiB,EACjB,OAAO,GAA4B,EAAE,EACT;IAC5B,IAAI,MAAM,KAAK,QAAQ,EAAE,CAAC;QACzB,eAAe,CAAC,iBAAiB,CAAC,QAAQ,CAAC,CAAC;QAC5C,OAAO,EAAE,EAAE,EAAE,IAAI,EAAE,MAAM,EAAE,QAAQ,EAAE,CAAC;IACvC,CAAC;IACD,MAAM,WAAW,GAAG,oBAAoB,CAAC,gBAAgB,CAAC,QAAQ,CAAC,CAAC,CAAC;IACrE,IAAI,WAAW,KAAK,QAAQ,IAAI,CAAC,OAAO,CAAC,SAAS,EAAE,CAAC;QACpD,OAAO,EAAE,EAAE,EAAE,KAAK,EAAE,MAAM,EAAE,iBAAiB,EAAE,CAAC;IACjD,CAAC;IACD,mBAAmB,CAAC,MAAM,EAAE,QAAQ,CAAC,CAAC;IACtC,eAAe,CAAC,iBAAiB,CAAC,MAAM,CAAC,CAAC;IAC1C,OAAO,EAAE,EAAE,EAAE,IAAI,EAAE,MAAM,EAAE,CAAC;AAAA,CAC5B;AAED;;;;;;GAMG;AACH,MAAM,UAAU,uBAAuB,CAAC,eAAgC,EAAE,QAAiB,EAAkB;IAC5G,MAAM,MAAM,GAAG,eAAe,CAAC,iBAAiB,EAAE,CAAC;IACnD,MAAM,WAAW,GAAG,oBAAoB,CAAC,gBAAgB,CAAC,QAAQ,CAAC,CAAC,CAAC;IACrE,IAAI,MAAM,KAAK,QAAQ;QAAE,OAAO,QAAQ,CAAC;IACzC,IAAI,WAAW,KAAK,MAAM;QAAE,OAAO,MAAM,CAAC;IAC1C,IAAI,WAAW,KAAK,QAAQ,EAAE,CAAC;QAC9B,eAAe,CAAC,iBAAiB,CAAC,QAAQ,CAAC,CAAC;QAC5C,OAAO,QAAQ,CAAC;IACjB,CAAC;IACD,IAAI,WAAW,KAAK,SAAS,IAAI,MAAM,KAAK,SAAS,EAAE,CAAC;QACvD,mBAAmB,CAAC,MAAM,EAAE,QAAQ,CAAC,CAAC;QACtC,OAAO,MAAM,CAAC;IACf,CAAC;IACD,eAAe,CAAC,iBAAiB,CAAC,WAAW,CAAC,CAAC;IAC/C,OAAO,WAAW,CAAC;AAAA,CACnB;AAUD,IAAI,qBAAkD,CAAC;AAEvD,MAAM,MAAM,GAAyB;IACpC,SAAS,GAAmB;QAC3B,OAAO,qBAAqB,EAAE,iBAAiB,EAAE,IAAI,SAAS,CAAC;IAAA,CAC/D;IACD,SAAS,CAAC,MAAsB,EAAQ;QACvC,qBAAqB,EAAE,iBAAiB,CAAC,MAAM,CAAC,CAAC;IAAA,CACjD;IACD,WAAW,GAAY;QACtB,MAAM,MAAM,GAAG,qBAAqB,EAAE,iBAAiB,EAAE,IAAI,SAAS,CAAC;QACvE,OAAO,uBAAuB,CAAC,MAAM,CAAC,CAAC;IAAA,CACvC;IACD,YAAY,CAAC,QAAgB,EAAkB;QAC9C,MAAM,WAAW,GAAG,oBAAoB,CAAC,QAAQ,CAAC,CAAC;QACnD,MAAM,MAAM,GAAG,qBAAqB,EAAE,iBAAiB,EAAE,IAAI,SAAS,CAAC;QACvE,8EAA8E;QAC9E,4EAA4E;QAC5E,IAAI,MAAM,KAAK,QAAQ,IAAI,WAAW,KAAK,QAAQ,EAAE,CAAC;YACrD,qBAAqB,EAAE,iBAAiB,CAAC,QAAQ,CAAC,CAAC;YACnD,OAAO,QAAQ,CAAC;QACjB,CAAC;QACD,OAAO,MAAM,CAAC;IAAA,CACd;CACD,CAAC;AAEF,MAAM,UAAU,4BAA4B,CAAC,eAAgC,EAAQ;IACpF,qBAAqB,GAAG,eAAe,CAAC;IACvC,UAAsC,CAAC,6BAA6B,CAAC,GAAG,MAAM,CAAC;AAAA,CAChF;AAED,MAAM,UAAU,uBAAuB,GAAqC;IAC3E,OAAQ,UAAsC,CAAC,6BAA6B,CAAqC,CAAC;AAAA,CAClH","sourcesContent":["import { existsSync, mkdirSync, readFileSync, writeFileSync } from \"node:fs\";\nimport { join } from \"node:path\";\nimport { getAgentDir } from \"../config.ts\";\nimport type { SettingsManager } from \"./settings-manager.ts\";\n\n/**\n * Built-in behavior.md presets.\n *\n * Selecting default / humanizer / concise replaces ~/.lunr/agent/behavior.md.\n * Custom leaves the file alone. lunr-behavior re-reads the file every turn, so\n * hand edits apply without a watcher. Fingerprint the body (header comments\n * stripped) to detect drift off a built-in template.\n */\n\nexport const BEHAVIOR_PRESET_BRIDGE_SYMBOL = Symbol.for(\"@lunr/behavior-preset\");\n\nexport type BehaviorPreset = \"default\" | \"humanizer\" | \"concise\" | \"custom\";\n\nexport const BEHAVIOR_PRESETS: readonly BehaviorPreset[] = [\"default\", \"humanizer\", \"concise\", \"custom\"];\n\nexport const BEHAVIOR_HEADER =\n\t\"<!-- lunR behavior rules — one rule per line. Edit freely or use the behavior tools. -->\\n\";\n\n/** Empty on purpose. Default content is a later fill-in. */\nexport const DEFAULT_BEHAVIOR_PRESET = \"\";\n\nexport const HUMANIZER_BEHAVIOR_PRESET = `# Humanizer (every reply)\n\nWrite like a person. Keep real claims. Never invent facts, names, numbers, dates, quotes, citations, rankings, or sources. Missing detail: ask or simplify. Fiction exempt when inventing is the task.\n\nMatch user voice when known. Personality (opinions, mixed feelings, humor, I, asides, uneven rhythm) only for essays/opinions/personal prose. Technical, legal, reference, factual stay neutral. Never invent facts for voice. Apply on the reply itself (no rewrite pass).\n\n1. Inflated legacy. Avoid: stands/serves as; is a testament/reminder; vital/significant/crucial/pivotal/key role/moment; underscores/highlights its importance/significance; reflects broader; symbolizing its ongoing/enduring/lasting; contributing to the; setting the stage for; marking/shaping the; represents/marks a shift; key turning point; evolving landscape; focal point; indelible mark; deeply rooted.\n2. Status name-drops. Avoid: independent coverage; local/regional/national media outlets; written by a leading expert; active social media presence. Cite only with what was said and where.\n3. Shallow -ing tack-ons. Avoid: highlighting/underscoring/emphasizing; ensuring; reflecting/symbolizing; contributing to; cultivating/fostering; encompassing; showcasing.\n4. Sales tone. Avoid: boasts a; vibrant; rich (figurative); profound; enhancing its; showcasing; exemplifies; commitment to; natural beauty; nestled; in the heart of; groundbreaking (figurative); renowned; breathtaking; must-visit; stunning.\n5. Vague authorities. Avoid: Industry reports; Observers have cited; Experts argue; Some critics argue; several sources/publications (unnamed). Real source or drop claim. Never invent one.\n6. Stock challenges/outlook. Avoid: Despite its... faces several challenges; Despite these challenges; Challenges and Legacy; Future Outlook.\n7. Stock AI words (esp. clustered): Actually; additionally; align with; crucial; delve; emphasizing; enduring; enhance; fostering; garner; gate/gated/gating (figurative only; keep technical gate); highlight (verb); interplay; intricate/intricacies; key (adj); landscape (abstract); pivotal; quietly; showcase; tapestry (abstract); testament; underscore (verb); valuable; vibrant. Also: at the end of the day; when it comes to; in a world where; moving forward; circle back; deep dive; game-changer; double down; take a step back; on the same page; make no mistake; it turns out; let me be clear; navigate (for challenges); lean into; unpack (before analysis); straightforward (filler praise).\n8. Prefer is/are/has. Avoid: serves as/stands as/marks/represents [a]; boasts/features/offers [a].\n9. No not-X-but-Y or clipped negatives (Not only...but; It's not just X, it's Y; \"no guessing\"). Full clause.\n10. No forced groups of three for a complete-sounding list.\n11. No synonym cycling of one subject. No machine-repeated openings. One clear name. Deliberate rhythm OK.\n12. No false from-X-to-Y when ends are not a real scale.\n13. Prefer active voice with a clear subject.\n14. No em/en dash characters, spaced dash pairs, or double-hyphen used as a dash, unless the user uses them. Use period, comma, colon, or parentheses.\n15. No decorative bold on ordinary phrases.\n16. No bold-label lists (\\`- **Label:** text\\`). Normal bullets or prose.\n17. Headings in sentence case, not Title Case.\n18. No decorative emojis on headings or bullets.\n19. Straight quotes only, not curly quotes.\n20. No chatbot leftovers: I hope this helps; Of course!; Certainly!; You're absolutely right!; Would you like...; Want me to...?; Should I continue?; let me know; here is a...\n21. No cutoff padding or guessed biography: as of [date]; Up to my last training update; While specific details are limited/scarce; based on available information; not publicly available; maintains a low profile; keeps personal details private; prefers to stay out of the spotlight; likely [grew up/studied/began]; it is believed that. State unknown or omit. Never present a guess as fact.\n22. No sycophantic openers (Great question!; excellent point; absolutely right).\n23. Cut filler: In order to → To; Due to the fact that → Because; At this point in time → Now; In the event that → If; has the ability to → can; It is important to note that → (delete).\n24. One needed qualifier max. Avoid stacks: to be fair; it's also possible; could potentially; might arguably; in some cases it may; this is an inference.\n25. No generic positive endings (future looks bright; exciting times; journey toward excellence; step in the right direction). End on last concrete fact.\n26. Hyphen pairs: keep before a noun when needed (\\`high-quality report\\`); drop after (\\`report is high quality\\`). Watch: third-party; cross-functional; client-facing; data-driven; decision-making; well-known; high-quality; real-time; long-term; end-to-end.\n27. No deeper-truth framing: The real question is; at its core; in reality; what really matters; fundamentally; the deeper issue; the heart of the matter.\n28. Do not announce the next point: Let's dive in/explore/break this down; here's what you need to know; now let's look at; without further ado; heads up; quick note; before I forget.\n29. Do not restate a heading in the first sentence under it.\n30. Describe current behavior. Prior versions only in changelogs/release notes/migration guides.\n31. No forced punchlines or stacks of dramatic fragments. One short emphatic line OK.\n32. No formulaic sayings: X is the Y of Z; X becomes a trap; X is not a tool but a mirror; the language/currency/architecture of.\n33. No fake-candid hooks: Honestly?; Look; Here's the thing; The thing is; Let's be honest; Real talk.\n34. Do not answer unraised objections: This isn't (mainly) about; I'm not saying/arguing; To be clear; Don't get me wrong; This is not to say; You could argue... but; Some might say... but. Direct claims OK.\n35. Do not reject fake alternatives: A tempting option/approach would be; One might be tempted to; An obvious approach would be; You might think... but; It would be easy to just; Some would suggest. Keep real options a reader might choose.\n\nDo not over-flag alone: polish; mixed register; dry prose without stock tells; formal words outside #7; salutations/sign-offs; one however/additionally; curly quotes alone; one dash alone; one short emphatic sentence; deliberate repeated openings; honestly/look mid-sentence; useful scope/legal/safety limits; real alternatives; unsourced web claims; clean formatting; watched phrases inside quotes, titles, names, or examples under discussion. Several patterns together beat one.\n\nKeep: specific odd details; mixed feelings; era slang; deliberate first person; short/long mix; genuine asides or self-corrections.`;\n\nexport const CONCISE_BEHAVIOR_PRESET = `# Concise (every reply)\n\nBe extremely concise. Sacrifice grammar for concision.\n\nPlans are not novels. Terminals read bottom-up. Scanning beats reading. Fewer tokens = faster and cheaper.\n\n## Brevity swaps\n| Instead of | Write |\n|---|---|\n| The user will be able to... | User can... |\n| This component is responsible for... | Handles... |\n| In order to achieve this, we need to... | Requires: |\n| It should be noted that... | (delete) |\n\nPrefer: fragments over full sentences; tables over paragraphs; bullets over prose; diagrams over descriptions.\n\n## Output order (always)\n1. Brief overview (2-3 sentences max)\n2. Main content (tables, bullets, diagrams)\n3. Unresolved questions (if any)\n4. Numbered action steps (ALWAYS LAST)\n\nUnresolved questions go before action steps as short bullets. Catch ambiguity before it becomes a bug.\n\n## Action steps (last visible block)\nEnd every non-trivial reply with concrete numbered next steps. Most important = most visible at the bottom.\n\n\\`\\`\\`\n## Next steps\n1. ...\n2. ...\n\\`\\`\\`\n\nTrivial yes/no or single-fact answers may skip the scaffold. Any plan, fix, design, or multi-step answer must end on numbered steps.\n\n## Anti-patterns\n| Don't | Do |\n|---|---|\n| Long prose explanations | Bullet points |\n| Nested sub-bullets (3+ levels) | Flat structure, tables |\n| \"Let me explain...\" | Just explain |\n| Repeating context | Reference by ID/name |\n| Hedging language | Direct statements |\n\n## Shape\nBad: The authentication system will need to handle user login. In order to accomplish this, we will need to implement a JWT-based mechanism that allows users to securely log in.\n\nGood:\nAuth: JWT login\n\n| Piece | Detail |\n|---|---|\n| Endpoint | POST /auth/login |\n| Token | JWT, 24h |\n| Guard | verify on protected routes |\n\n## Unresolved questions\n- OAuth provider? (Google, GitHub, both)\n- Session duration?\n\n## Next steps\n1. Add auth module at src/auth/\n2. Add JWT dependency\n3. Implement login endpoint\n4. Add tests`;\n\nexport function isBehaviorPreset(value: unknown): value is BehaviorPreset {\n\treturn value === \"default\" || value === \"humanizer\" || value === \"concise\" || value === \"custom\";\n}\n\nexport function isBuiltinBehaviorPreset(preset: BehaviorPreset): boolean {\n\treturn preset === \"default\" || preset === \"humanizer\" || preset === \"concise\";\n}\n\nexport function behaviorFilePath(agentDir: string = getAgentDir()): string {\n\treturn join(agentDir, \"behavior.md\");\n}\n\nexport function normalizeBehaviorBody(text: string): string {\n\treturn text\n\t\t.replace(/\\r\\n/g, \"\\n\")\n\t\t.split(\"\\n\")\n\t\t.filter((line) => !line.startsWith(\"<!--\"))\n\t\t.join(\"\\n\")\n\t\t.trim();\n}\n\nexport function builtinBehaviorBody(preset: Exclude<BehaviorPreset, \"custom\">): string {\n\tif (preset === \"humanizer\") return HUMANIZER_BEHAVIOR_PRESET;\n\tif (preset === \"concise\") return CONCISE_BEHAVIOR_PRESET;\n\treturn DEFAULT_BEHAVIOR_PRESET;\n}\n\nexport function wrapBehaviorFile(body: string): string {\n\tconst trimmed = body.replace(/\\r\\n/g, \"\\n\").trim();\n\tif (!trimmed) return BEHAVIOR_HEADER;\n\treturn `${BEHAVIOR_HEADER}${trimmed}\\n`;\n}\n\nexport function detectBehaviorPreset(fileText: string): BehaviorPreset {\n\tconst body = normalizeBehaviorBody(fileText);\n\tif (body === normalizeBehaviorBody(HUMANIZER_BEHAVIOR_PRESET)) return \"humanizer\";\n\tif (body === normalizeBehaviorBody(CONCISE_BEHAVIOR_PRESET)) return \"concise\";\n\tif (body === normalizeBehaviorBody(DEFAULT_BEHAVIOR_PRESET)) return \"default\";\n\treturn \"custom\";\n}\n\nexport function readBehaviorFile(agentDir?: string): string {\n\tconst file = behaviorFilePath(agentDir);\n\tif (!existsSync(file)) return \"\";\n\treturn readFileSync(file, \"utf-8\");\n}\n\nexport function writeBehaviorFile(body: string, agentDir?: string): void {\n\tconst file = behaviorFilePath(agentDir);\n\tconst dir = agentDir ?? getAgentDir();\n\tif (!existsSync(dir)) mkdirSync(dir, { recursive: true });\n\twriteFileSync(file, wrapBehaviorFile(body), \"utf-8\");\n}\n\nexport function writeBehaviorPreset(preset: Exclude<BehaviorPreset, \"custom\">, agentDir?: string): void {\n\twriteBehaviorFile(builtinBehaviorBody(preset), agentDir);\n}\n\nexport type ApplyBehaviorPresetResult = { ok: true; preset: BehaviorPreset } | { ok: false; reason: \"needs-overwrite\" };\n\n/**\n * Persist a preset and, for built-ins, replace behavior.md.\n * Custom never writes. Switching onto a built-in while the file is custom\n * requires `{ overwrite: true }` so the settings UI can confirm first.\n */\nexport function applyBehaviorPreset(\n\tsettingsManager: SettingsManager,\n\tpreset: BehaviorPreset,\n\tagentDir?: string,\n\toptions: { overwrite?: boolean } = {},\n): ApplyBehaviorPresetResult {\n\tif (preset === \"custom\") {\n\t\tsettingsManager.setBehaviorPreset(\"custom\");\n\t\treturn { ok: true, preset: \"custom\" };\n\t}\n\tconst fingerprint = detectBehaviorPreset(readBehaviorFile(agentDir));\n\tif (fingerprint === \"custom\" && !options.overwrite) {\n\t\treturn { ok: false, reason: \"needs-overwrite\" };\n\t}\n\twriteBehaviorPreset(preset, agentDir);\n\tsettingsManager.setBehaviorPreset(preset);\n\treturn { ok: true, preset };\n}\n\n/**\n * Align the stored preset with the file.\n * Custom stored always wins (file is the source of truth).\n * A custom file while a built-in is stored flips the setting to custom.\n * A missing/empty file while a non-default built-in is stored restores that template.\n * A different built-in already on disk is adopted (file wins).\n */\nexport function reconcileBehaviorPreset(settingsManager: SettingsManager, agentDir?: string): BehaviorPreset {\n\tconst stored = settingsManager.getBehaviorPreset();\n\tconst fingerprint = detectBehaviorPreset(readBehaviorFile(agentDir));\n\tif (stored === \"custom\") return \"custom\";\n\tif (fingerprint === stored) return stored;\n\tif (fingerprint === \"custom\") {\n\t\tsettingsManager.setBehaviorPreset(\"custom\");\n\t\treturn \"custom\";\n\t}\n\tif (fingerprint === \"default\" && stored !== \"default\") {\n\t\twriteBehaviorPreset(stored, agentDir);\n\t\treturn stored;\n\t}\n\tsettingsManager.setBehaviorPreset(fingerprint);\n\treturn fingerprint;\n}\n\nexport interface BehaviorPresetBridge {\n\tgetPreset(): BehaviorPreset;\n\tsetPreset(preset: BehaviorPreset): void;\n\tisCapExempt(): boolean;\n\t/** Fingerprint the current file text; persist custom when a built-in selection drifted. */\n\tsyncFromFile(fileText: string): BehaviorPreset;\n}\n\nlet activeSettingsManager: SettingsManager | undefined;\n\nconst bridge: BehaviorPresetBridge = {\n\tgetPreset(): BehaviorPreset {\n\t\treturn activeSettingsManager?.getBehaviorPreset() ?? \"default\";\n\t},\n\tsetPreset(preset: BehaviorPreset): void {\n\t\tactiveSettingsManager?.setBehaviorPreset(preset);\n\t},\n\tisCapExempt(): boolean {\n\t\tconst preset = activeSettingsManager?.getBehaviorPreset() ?? \"default\";\n\t\treturn isBuiltinBehaviorPreset(preset);\n\t},\n\tsyncFromFile(fileText: string): BehaviorPreset {\n\t\tconst fingerprint = detectBehaviorPreset(fileText);\n\t\tconst stored = activeSettingsManager?.getBehaviorPreset() ?? \"default\";\n\t\t// Per-turn: only flip a built-in to custom when the file drifted. Restoring a\n\t\t// missing template or adopting another built-in is reconcileBehaviorPreset.\n\t\tif (stored !== \"custom\" && fingerprint === \"custom\") {\n\t\t\tactiveSettingsManager?.setBehaviorPreset(\"custom\");\n\t\t\treturn \"custom\";\n\t\t}\n\t\treturn stored;\n\t},\n};\n\nexport function registerBehaviorPresetBridge(settingsManager: SettingsManager): void {\n\tactiveSettingsManager = settingsManager;\n\t(globalThis as Record<symbol, unknown>)[BEHAVIOR_PRESET_BRIDGE_SYMBOL] = bridge;\n}\n\nexport function getBehaviorPresetBridge(): BehaviorPresetBridge | undefined {\n\treturn (globalThis as Record<symbol, unknown>)[BEHAVIOR_PRESET_BRIDGE_SYMBOL] as BehaviorPresetBridge | undefined;\n}\n"]}