Skip to content

Names for the thinkwatch-data tool rule, and two code rules missing from notifications - #281

Merged
fylorn merged 1 commit into
devfrom
guard-own-data-labels
Oct 4, 2026
Merged

fylorn merged 1 commit into
devfrom
guard-own-data-labels

Conversation

@fylorn

@fylorn fylorn commented Oct 4, 2026

Copy link
Copy Markdown
Contributor
  • Core's new built-in tool rule thinkwatch-data (Tool-call inspection guards ThinkWatch's own data directory; the docs say what protects config.yaml ThinkWatch-Core#287, "Read or change ThinkWatch's own data") gets its Chinese name and why in src/i18n/core.zh.json, and the matcher text for its builtin check (thinkwatch-data) in both languages in src/security/labels.i18n.tsx. Unused until a core release includes the rule; until then nothing changes, and after the bump the security page shows the Chinese name instead of falling back to core's English one.
  • Notifications for tool-call hits name built-in rules from their own table in src-tauri/src/notices/rules.rs, which never got secret-to-unknown-host or upload-file-to-host, so those two showed their raw ids. Both are added, together with thinkwatch-data.

Checked locally: pnpm typecheck, pnpm test (752 passed), cargo fmt --check on the changed Rust file.

🤖 Generated with Claude Code

…ng from notifications

Core's new built-in tool rule `thinkwatch-data` (ThinkWatch-Core#287) gets
its Chinese name and why in core.zh.json, and the matcher text for its
`builtin` check in both languages. Until core ships it these entries are
unused; the security page falls back to core's English name until then.

Notifications for tool-call hits name built-in rules from their own table,
which never got `secret-to-unknown-host` or `upload-file-to-host`, so those
two showed their raw ids. All three are added.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@fylorn
fylorn merged commit a936d16 into dev Oct 4, 2026
4 checks passed
@fylorn
fylorn deleted the guard-own-data-labels branch October 4, 2026 16:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant