Skip to content

Use core v0.60.0: auxiliary requests are answered locally or forwarded - #274

Merged
fylorn merged 1 commit into
devfrom
feat/probe-forward
Oct 3, 2026
Merged

fylorn merged 1 commit into
devfrom
feat/probe-forward

Conversation

@fylorn

@fylorn fylorn commented Oct 3, 2026

Copy link
Copy Markdown
Contributor

Why

Core v0.60.0 (ThinkWatch-Core#281) gives client helper requests two modes instead of three. "Pass through" and "Use routing" both went through the routing rules and differed only in whether a rule's auxiliary-request condition could match, while the names and the dry run suggested that "Pass through" skipped routing. They are now one mode, "Forward": a forwarded helper request carries its class, so a rule's auxiliary-request condition takes effect as soon as it is written.

What

  • Auxiliary tab: two-way segmented control (Answer locally / Forward). The forward row says the request follows the routing rules; the footer says rules can match forwarded kinds with the auxiliary-request condition.
  • Rule dialog: the "set these categories to be routed on save" checkbox is gone. A warning names the classes the condition picks that are answered locally (they never reach routing) and points to the Auxiliary tab. It is not shown when "any auxiliary request" is chosen, since that means any forwarded kind.
  • Route dialog: no longer sends route_probes (removed from RouteSave).
  • Dry run: the pass-through outcome is gone; only locally answered requests short-circuit.
  • Pin core v0.60.0 (protocol 36, schema unchanged at 25); regenerate tw-api.ts; update fixtures, shot data and core.zh.json (control.unknown_probe_class removed).

Upgrade note

A config.yaml that sets client_probes.<class> to passthrough or route does not load in core 0.60.0 (safe mode). Configs that never changed the Auxiliary tab are unaffected. Agreed to cover this in the release notes only, without a compatibility path.

Tests

  • pnpm typecheck, pnpm test (744 passed)
  • cargo fmt --check, cargo clippy --all-targets -D warnings, cargo test with a twcore built at v0.60.0 (all passed, including control_plane handshake tests)
  • Preview harness: Auxiliary tab in zh and en; the rule dialog warning with an intercepted class, hidden with "any auxiliary request"

🤖 Generated with Claude Code

Core v0.60.0 has two modes for client helper requests instead of three.
"Pass through" and "Use routing" both went through the routing rules
and differed only in whether a rule's auxiliary-request condition could
match; they are now one mode, "Forward", and that condition takes effect
as soon as a rule uses it.

- Auxiliary tab: two-way segmented control, copy says forwarded requests
  follow the routing rules
- Rule dialog: the "set these categories to be routed on save" checkbox
  is gone; a warning names the classes the condition picks that are
  answered locally (they never reach routing), unless "any auxiliary
  request" is chosen
- Route dialog: no longer sends route_probes
- Dry run: the pass-through outcome is gone
- Pin core v0.60.0 (protocol 36); regenerated tw-api.ts, fixtures and
  the zh message table

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@fylorn
fylorn merged commit 29b7d08 into dev Oct 3, 2026
4 checks passed
@fylorn
fylorn deleted the feat/probe-forward branch October 3, 2026 15:42
@fylorn fylorn mentioned this pull request Oct 3, 2026
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