Skip to content

fix: stabilize agent runtime and Zotero configuration - #56

Merged
zuowen7 merged 4 commits into
mainfrom
agent/agent-v2-hardening
Aug 1, 2026
Merged

fix: stabilize agent runtime and Zotero configuration#56
zuowen7 merged 4 commits into
mainfrom
agent/agent-v2-hardening

Conversation

@zuowen7

@zuowen7 zuowen7 commented Aug 1, 2026

Copy link
Copy Markdown
Owner

What changed

  • replace fixed Agent V2 tool-call ceilings with progress-aware leases and stalled-call detection
  • preserve compact thought summaries and uninterrupted multi-turn execution
  • make every Zotero route consume the merged runtime configuration
  • keep Zotero credentials and user ID in the ignored local override, and seed the runtime config from the tracked source template

Root cause

Agent runs were stopped by fixed per-turn counters even while making progress. Zotero settings were saved through the merged config service but read back through a legacy default-file-only path, so the saved API key was invisible to Zotero routes.

Validation

  • backend full suite: 2347 passed, 7 skipped
  • frontend suite: 825 passed
  • Zotero/config regression: 75 passed, 5 skipped
  • real Zotero status endpoint: HTTP 200, connected=true, verified=true
  • configured private-value scan: 0 values present in the push diff

@zuowen7
zuowen7 merged commit 6e9bb86 into main Aug 1, 2026
6 checks passed
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