Skip to content

feat(plugin) + fix(tool) + ci: plugin system, tool improvements, and GitHub CI#1

Merged
lIang70 merged 5 commits into
mainfrom
chore/tool-improvements-and-ci
Apr 14, 2026
Merged

feat(plugin) + fix(tool) + ci: plugin system, tool improvements, and GitHub CI#1
lIang70 merged 5 commits into
mainfrom
chore/tool-improvements-and-ci

Conversation

@lIang70

@lIang70 lIang70 commented Apr 14, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • feat(plugin): Add gRPC-based plugin system for out-of-process tool execution, including protobuf definitions, server scaffolding, and tests
  • fix(tool): Unify schema definition style across all tool modules (memory, extract → DefineSchema builder), deduplicate Required(), and make Registry.Execute return ToolResult only for consistent error semantics
  • fix(memory): Align summary index test assertions with current English header text
  • ci: Add GitHub Actions with path-filtered jobs (sdk/sdkx/plugin/examples), gate job for branch protection, and lightweight post-merge build

Commits

# Commit Scope
1 feat(plugin): add gRPC-based plugin system plugin/, go.work
2 fix(tool): unify schema style and Execute error semantics sdk/tool/, sdk/memory/tools.go, sdkx/extract/tool.go
3 fix(memory): align summary index tests with English header text sdk/memory/summary_index_test.go
4 ci: add GitHub Actions with path-filtered jobs .github/workflows/

Test plan

  • go test ./sdk/... -count=1 passes
  • go test ./sdkx/... -count=1 passes
  • go test ./plugin/... -count=1 passes
  • CI gate job (CI) reports green on this PR

Made with Cursor

lIang70 added 5 commits April 14, 2026 17:07
Introduce a plugin module that enables out-of-process tool execution
via gRPC. Includes protocol definitions (protobuf), server scaffolding,
type mappings, and tests.

Made-with: Cursor
- SchemaBuilder.Required() now deduplicates field names
- Add PropertyWithDefault() for properties with default values
- Migrate memory and extract tool definitions to DefineSchema builder,
  eliminating hand-written map[string]any for consistent style
- Registry.Execute returns ToolResult only (no error), so tool-not-found
  is handled identically to tool execution failures

Made-with: Cursor
Tests were asserting Chinese text but the implementation was changed
to English. Update assertions to match current output.

Made-with: Cursor
- ci.yml: runs on PRs with path-based filtering (sdk, sdkx, plugin,
  examples). Gate job "CI" aggregates results for branch protection.
- post-merge.yml: lightweight build+vet on push to main.
- Branch protection configured to require "CI" check before merge.

Made-with: Cursor
voice-pipeline depends on portaudio which is unavailable in CI.
Drop examples from CI jobs and fix formatting in plugin/serve_test.go.

Made-with: Cursor
@lIang70
lIang70 merged commit 2e3a5e9 into main Apr 14, 2026
9 checks passed
@lIang70
lIang70 deleted the chore/tool-improvements-and-ci branch April 14, 2026 13:14
lIang70 added a commit that referenced this pull request May 14, 2026
Silent multi-minute ingest is the #1 driver of "is it stuck?" pages
on the bm25-only path (no embedder = no network log line for 5183
docs × ~60ms tokenize/index). The lane phase already emitted
milestone events but only the Feishu adapter saw them — operators
running the binary directly or tailing nohup-style logs got nothing.

Two changes:

  * ingest() now emits "ingest_start" once and "ingest_progress" at
    each opts.ProgressPct milestone (mirrors the runLane progress
    pattern). Default 10% steps means scifact's 5183-doc ingest
    emits ~10 lines, which is the right resolution to distinguish
    "BM25 indexing" from "stuck on a network call".

  * CLI Hook now mirrors a small allow-list of lifecycle events
    (start / ingest_* / lane_* / done / error) to stderr alongside
    forwarding them to the notifier. The allow-list keeps any future
    debug-y emits off the operator's screen.

Verified end-to-end on a 3-doc / 2-query mini-dataset with
`--notify-progress-pct 50`: stderr now prints 8 lifecycle lines in
order; the existing TestRun_HookEvents lifecycle-sequence assertion
was updated to expect "ingest_start" between "start" and
"ingest_done".

No behavioural change to the report payload — this is pure visibility.

Co-authored-by: Cursor <cursoragent@cursor.com>
lIang70 added a commit that referenced this pull request May 21, 2026
Harden lease-recycle recovery under scope lock, transient retry with
RetryAt/Attempt persistence, and require Scope/RuntimeID for drain and
stats so workers cannot claim or observe cross-tenant queue state.

Co-authored-by: Cursor <cursoragent@cursor.com>
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