@kynver-app/runtime 0.2.51 → 0.2.53
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +5 -33
- package/dist/cli.js +82 -82
- package/dist/index.js +100 -100
- package/dist/server/cleanup.js +1 -1
- package/dist/server/monitor.js +1 -1
- package/dist/server/repo-search.js +1 -1
- package/dist/server/worker-policy.js +2 -2
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -95,38 +95,10 @@ Default Cursor model: `composer-2.5`. Override with `--model` on dispatch/worker
|
|
|
95
95
|
|
|
96
96
|
Website chat (delegated turns claimed by `kynver daemon`) follows `chatProvider` if set, otherwise `workerProvider`. Cursor boxes spawn `agent --print --mode agent` by default in `~/.kynver/chat-workspace` (created empty — no monorepo clone, no `defaultRepo` assumption). Ask mode is only used when the website toggle requests it. The hosted personal-agent loop handles Agent-mode / factory turns so MEMBER users can call factory tools. Claude/Anthropic boxes keep the local Anthropic Messages path (`ANTHROPIC_API_KEY` or `kynver start --chat-oauth`). Command turns are unchanged (allowlist + auth proof).
|
|
97
97
|
|
|
98
|
-
##
|
|
98
|
+
## Contributing
|
|
99
99
|
|
|
100
|
-
|
|
100
|
+
Development against a Kynver monorepo checkout — explicit harness verbs,
|
|
101
|
+
targeted dispatch, and the test suite — is documented in the monorepo at
|
|
102
|
+
`docs/runbooks/runtime-monorepo-development.md`.
|
|
101
103
|
|
|
102
|
-
|
|
103
|
-
kynver setup --api-base-url http://localhost:3000 --agent-os-id <id> [--repo /path/to/repo] --max-workers 13
|
|
104
|
-
kynver login --api-key "$KYNVER_API_KEY"
|
|
105
|
-
kynver runner credential --agent-os-id <id>
|
|
106
|
-
kynver config ensure-default-repo # persist defaultRepo in ~/.kynver/config.json
|
|
107
|
-
kynver run create [--repo /path/to/repo] --name my-run
|
|
108
|
-
kynver daemon --run <runId> --agent-os-id <id> --execute
|
|
109
|
-
```
|
|
110
|
-
|
|
111
|
-
New runs are cut from `origin/main`; when that ref does not exist the run falls back to the remote default branch (`origin/HEAD`), and `--base <ref>` / `KYNVER_RUN_BASE_REF` / `defaultBase` in `~/.kynver/config.json` override the base explicitly.
|
|
112
|
-
|
|
113
|
-
### Targeted dispatch (after creating a board task)
|
|
114
|
-
|
|
115
|
-
Broad `lane:any` dispatch still sweeps the ready queue (review lane first, then priority/age). To start **one specific task** you just created — without admitting an older ready row — pass the task id:
|
|
116
|
-
|
|
117
|
-
```bash
|
|
118
|
-
kynver run dispatch --run <runId> --agent-os-id <id> --execute \
|
|
119
|
-
--target-task-id <taskId> --max-starts 1
|
|
120
|
-
```
|
|
121
|
-
|
|
122
|
-
The server `dispatch-next` body field is `targetTaskId` (same semantics). When set, no candidate pages are scanned; the response includes `targetTaskMiss: true` if the row is missing or belongs to another workspace.
|
|
123
|
-
|
|
124
|
-
### PR-ready handoff
|
|
125
|
-
|
|
126
|
-
`ensurePrReadyHandoff` resolves `owner/repo` from `git remote get-url origin` via URL parsing (repo names with dots, e.g. `Totalsolutionsync/Kynver`, are no longer truncated).
|
|
127
|
-
|
|
128
|
-
## Tests
|
|
129
|
-
|
|
130
|
-
```bash
|
|
131
|
-
npm run kynver:test
|
|
132
|
-
```
|
|
104
|
+
Bug reports: see [Report a bug](#report-a-bug) above.
|