Repository navigation
Use D1-only AI settings and remove configuration bundling - #61
Merged
Merged
Conversation
jackm43
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
AI requests now read their prompts and model settings exclusively from a fresh primary D1 snapshot. Missing, invalid, or unavailable D1 settings stop inference instead of falling back to packaged files or KV. Mentions and /ask use the configured chat prompt directly, without appended command-specific instructions.
Remove the generated configuration module and build hooks. Keep Markdown and JSON files outside the Worker source as operator inputs for initial D1 setup. Initialization preserves existing D1 settings and legacy live KV values. The local debugging launcher initializes only an empty sandbox.
The debugging UI runs natively on Windows by default, with Docker available through DEV_UI_DOCKER=1. Runtime test bundles stay on the project drive to avoid Pyodide's cross-drive path bug. Document same-drive global uv interpreter/cache settings, fix UTF-8 runtime logs, and regenerate platform type hints.
Validation: static checks, all 130 behavior tests, isolated native Worker runtime tests (including missing-D1 rejection), local initialization and repeat-run preservation, native Pywrangler dependency synchronization and deployment dry run, and native debugging UI startup with live D1 settings loading passed. Production D1 settings were verified and the D1-only Worker was deployed successfully; its gateway health was connected.