@kohala/devkit 0.1.5 → 0.1.7

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/docs/DEPLOY.md CHANGED
@@ -44,5 +44,13 @@ platform; do that in the Kohala dashboard.
44
44
  fresh `pk_` key, or check `KOHALA_API_KEY`.
45
45
  - **403 Forbidden** — your plan does not allow the operation. Check your
46
46
  plan at kohala.ai.
47
+ - **manual run not started: agent not enabled** — newly created agents start
48
+ disabled. Enable the agent in the kohala.ai dashboard, then re-run
49
+ `kohala deploy <agent> --run`. Enabling survives redeploys — the idempotent
50
+ upsert does not reset it.
51
+ - **manual run not started: nothing to run** — the platform only executes
52
+ scripts bound to an active cron schedule. Add `"schedule": "..."` (a
53
+ 5-field cron expression) to `kohala.json` and redeploy: deploy binds every
54
+ skill script to the schedule, which also makes manual runs work.
47
55
 
48
56
  Both messages tell you this directly; nothing is retried silently.
package/docs/MANIFEST.md CHANGED
@@ -37,7 +37,7 @@ is what goes live.
37
37
  | `toolAllowlist` | `agentToolAllowlist` | Exactly the tools the agent may call. No implicit grants. |
38
38
  | `runtimeMode` | `agentRuntimeMode` | `"wrap"` or `"llm"` (see below). |
39
39
  | `skills` | `agentSkills` | Map of skill name → script filename in `skills/`. |
40
- | `schedule` | `agentScheduleCron` + `agentScheduleEnabled` | Cron expression. Only used on deploy; local runs are manual. Deploy also PATCHes the schedule after the agent upsert (the platform ignores schedule fields when updating an existing agent by name) and verifies it persisted. |
40
+ | `schedule` | `agentScheduleCron` + `agentScheduleEnabled` + `agentScheduleEntries` | Cron expression. Only used on deploy; local runs are manual. After uploading the skills, deploy PATCHes the schedule (the platform ignores schedule fields when updating an existing agent by name) **and binds every skill script to the cron via `agentScheduleEntries`** — without the binding the platform has nothing to run (409 `nothing_to_run`). The round-trip is verified. |
41
41
  | `caps.perRunTokens` | `agentPerRunTokenCap` | Hard token ceiling per shift. |
42
42
  | `caps.perDayTokens` | `agentPerDayTokenCap` | Cumulative ceiling per UTC day. |
43
43
  | `caps.billingTokens` | `agentBillingCapTokens` | Billing-period cap. Ignored locally. |
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@kohala/devkit",
3
- "version": "0.1.5",
3
+ "version": "0.1.7",
4
4
  "description": "Open-source CLI, local agent emulator, and open MCP memory server for Kohala agents. Build and run agents entirely on your own machine — then push the same agent to Kohala when you want it hosted.",
5
5
  "license": "MIT",
6
6
  "type": "module",