This issue is the ledger of agentic-kit's upstream watch.
agentic-kit depends on fixes in Ruflo, Agentic QE, AgentDB, RuVector, RuvNet Brain, Codex and agent-browser. Every upstream thread ak relies on is recorded in one registry, src/lib/hook-audit/agentic-dependency-constraints.json. A daily check compares it with GitHub and npm.
On a day with events, one comment is added here: the event lines in a code block, then one plain sentence per line. Each line has the form
UPSTREAM-WATCH <id> <event> <yyyy-mm-dd> [key=value ...]
An exact line recorded here is never acted on twice. A released event leads to a draft pull request on an upstream/<id> branch. Nothing is merged automatically, and nothing is posted upstream automatically.
Only comments by the repository owner and the watch itself count; others are ignored. How it works: docs/UPSTREAM-WATCH.md.
This issue is the ledger of agentic-kit's upstream watch.
agentic-kit depends on fixes in Ruflo, Agentic QE, AgentDB, RuVector, RuvNet Brain, Codex and agent-browser. Every upstream thread ak relies on is recorded in one registry,
src/lib/hook-audit/agentic-dependency-constraints.json. A daily check compares it with GitHub and npm.On a day with events, one comment is added here: the event lines in a code block, then one plain sentence per line. Each line has the form
An exact line recorded here is never acted on twice. A
releasedevent leads to a draft pull request on anupstream/<id>branch. Nothing is merged automatically, and nothing is posted upstream automatically.Only comments by the repository owner and the watch itself count; others are ignored. How it works: docs/UPSTREAM-WATCH.md.