ci: retire push/PR triggers to workflow_dispatch (local-builds quota policy) - #1118
ci: retire push/PR triggers to workflow_dispatch (local-builds quota policy)#1118wrightpt wants to merge 37 commits into
Conversation
…tion Merge workstation AgentMemory hardening stack
Fix action list pagination
Add canonical AgentMemory project scope
Decouple hook capture from synchronous observe
Await asynchronous hook transport acknowledgements
Make observation ingestion durable and report disabled LLM work as skipped
Build runtime assets automatically before npm packaging.
Prevent duplicate workers from unregistering live AgentMemory routes.
Add resilient Streamable HTTP MCP transport
Fix iii 0.11.2 active-invocation leak
Exclude blocked actions from AgentMemory frontier
feat: add Actions v2 schema and safe migration
…eKV boundary The iii-engine resolves state::get with undefined for missing keys, not null. rebaseActionMutation's create path compares expectedBefore === null against current with strict equality, so every mem::action-create threw action_revision_conflict while updates kept working. The in-memory test mock coerced with ?? null and hid the real engine semantics; add an engine-faithful regression test (test/state-kv.test.ts).
state::get resolves undefined for missing keys; StateKV.get is the normalizing boundary (2026-07-17 action_revision_conflict outage). Also documents the symlinked global install so deploys are build + service restart.
Bounds action-store growth (the 15-min write-path canary alone adds ~96 cancelled actions/day). mem::action-gc collects done/cancelled actions older than maxAgeDays (default 30) that appear in no edge, dry-run by default, revalidating each candidate before deletion and emitting one batched action_delete audit row. Exposed as POST /agentmemory/actions/gc (REST 131).
|
@wrightpt is attempting to deploy a commit to the rohitg00's projects Team on Vercel. A member of the Team first needs to authorize it. |
|
Opened against the wrong base repo (meant for the wrightpt fork). Closing unmerged; correct PR follows on wrightpt/agentmemory. Sorry for the noise. |
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (2)
📒 Files selected for processing (122)
📝 WalkthroughWalkthroughThe PR adds Actions v2 storage and migration, revision-bound pagination, durable asynchronous observation ingestion, richer project/session context, Streamable HTTP MCP support, configurable tool visibility, LLM skip-state metrics, worker PID leases, and related documentation and tests. ChangesAgentMemory platform
Estimated code review effort: 5 (Critical) | ~120 minutes Possibly related PRs
Suggested reviewers: ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment Warning |
What
Trigger-only change: removes the
push:andpull_request:trigger blocks from.github/workflows/ci.yml, keepingworkflow_dispatch:. No job, step, matrix, or concurrency changes; both workflow files still parse as valid YAML.Fleet policy: the GitHub account has a 2,000-minute/month Actions quota with a $0 stop-usage budget (reference:
trading-system/docs/LOCAL_IMAGE_BUILDS.md). Push/PR-triggered workflows are being retired to manual runs; this repo'sAGENTS.mdalready requiresnpm testlocally before PR.Per-workflow decisions
ci.ymlpush+pull_requesttriggers on main; no repo doc declares it a keeper. Recent runs showaction_required(quota-blocked), and the file's own header already documentedworkflow_dispatchas the manual re-run path.publish.ymlrelease: [published]+workflow_dispatchonly; out of scope. The release trigger is the documented npm-publish mechanism in CONTRIBUTING.md and runs only on tagged releases.Manual runs remain available via the Actions tab ("Run workflow"). Do not merge without review.
Summary by CodeRabbit
New Features
Bug Fixes
Documentation