fix: validate Auggie matchers with JavaScript
This commit is contained in:
1 parent
453804dff9
commit
86152c8179
5 files changed
+127
-8
No files matched your search
@@ -25,6 +25,7 @@ This repository owns the published `elydora` package, its CLI, synchronous and a
|
||||
- Select Kimi Code and legacy kimi-cli config targets from existing runtime evidence; a fresh installation targets current Kimi Code and keeps migration markers isolated to active runtimes.
|
||||
- Keep Grok Build writes inside its native global `$GROK_HOME/hooks/*.json` contract. Treat Claude Code and Cursor compatibility files plus project `.grok/hooks` as read-only integration sources.
|
||||
- Write Auggie hooks only to `~/.augment/settings.json`; keep system and workspace settings read-only. Generate `.cmd` wrappers on Windows and `.sh` wrappers on Unix because Auggie dispatches supported script paths, and express hook timeouts in milliseconds.
|
||||
- Validate Auggie matcher syntax during installation with Node.js `new RegExp`; keep status and uninstall independent from the JavaScript validator so recovery remains available offline.
|
||||
|
||||
## Code Quality
|
||||
|
||||
|
||||
Reference in new issue
Block a user