polyctl 0.7.0__py3-none-any.whl
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.
- polyctl/__init__.py +7 -0
- polyctl/__main__.py +5 -0
- polyctl/a2a.py +226 -0
- polyctl/a2a_mcp.py +546 -0
- polyctl/acp.py +417 -0
- polyctl/adapters/README.md +101 -0
- polyctl/adapters/aider.json +32 -0
- polyctl/adapters/amazon-q.json +15 -0
- polyctl/adapters/amp.json +16 -0
- polyctl/adapters/antigravity.json +120 -0
- polyctl/adapters/claude-code.json +229 -0
- polyctl/adapters/cloud-generic.json +57 -0
- polyctl/adapters/codex.json +47 -0
- polyctl/adapters/command-code.json +45 -0
- polyctl/adapters/copilot.json +17 -0
- polyctl/adapters/cursor-agent.json +29 -0
- polyctl/adapters/deepseek.json +13 -0
- polyctl/adapters/droid.json +34 -0
- polyctl/adapters/gemini.json +30 -0
- polyctl/adapters/grok.json +22 -0
- polyctl/adapters/hermes.json +34 -0
- polyctl/adapters/kilocode.json +30 -0
- polyctl/adapters/kimi.json +23 -0
- polyctl/adapters/kiro.json +332 -0
- polyctl/adapters/ollama.json +29 -0
- polyctl/adapters/omp.json +34 -0
- polyctl/adapters/openai-api.json +68 -0
- polyctl/adapters/opencode.json +162 -0
- polyctl/adapters/pi.json +24 -0
- polyctl/adapters/pr-agent.json +54 -0
- polyctl/adapters/profiles.json +9 -0
- polyctl/adapters/qoder.json +163 -0
- polyctl/adapters/qwen.json +27 -0
- polyctl/adapters/reasonix.json +25 -0
- polyctl/adapters/rewriters/rtk.json +24 -0
- polyctl/adapters/trae.json +31 -0
- polyctl/adapters/vendors.json +42 -0
- polyctl/adapters/warp.json +88 -0
- polyctl/allowlist.py +1756 -0
- polyctl/api_review.py +920 -0
- polyctl/cli.py +835 -0
- polyctl/conformance_harness.py +9 -0
- polyctl/demo.py +503 -0
- polyctl/drivers.py +146 -0
- polyctl/email.py +160 -0
- polyctl/features.py +98 -0
- polyctl/journal.py +144 -0
- polyctl/language.py +945 -0
- polyctl/lib.py +1296 -0
- polyctl/matrix.py +660 -0
- polyctl/mcp.py +1362 -0
- polyctl/ntfy.py +169 -0
- polyctl/outbound.py +39 -0
- polyctl/parts/__init__.py +5 -0
- polyctl/parts/cli_authority.py +2615 -0
- polyctl/parts/cli_channels.py +1325 -0
- polyctl/parts/cli_checks.py +2293 -0
- polyctl/parts/cli_completion.py +686 -0
- polyctl/parts/cli_evidence.py +141 -0
- polyctl/parts/cli_gain.py +375 -0
- polyctl/parts/cli_harness.py +392 -0
- polyctl/parts/cli_hooks.py +1816 -0
- polyctl/parts/cli_install.py +638 -0
- polyctl/parts/cli_lanes.py +106 -0
- polyctl/parts/cli_maintenance.py +2536 -0
- polyctl/parts/cli_next.py +248 -0
- polyctl/parts/cli_pr.py +53 -0
- polyctl/parts/cli_project.py +2857 -0
- polyctl/parts/cli_review.py +5158 -0
- polyctl/parts/cli_status.py +898 -0
- polyctl/parts/lib_adapters.py +2933 -0
- polyctl/parts/lib_alarms.py +2106 -0
- polyctl/parts/lib_events.py +224 -0
- polyctl/parts/lib_evidence.py +412 -0
- polyctl/parts/lib_gates.py +2099 -0
- polyctl/parts/lib_lanes.py +829 -0
- polyctl/parts/lib_mail.py +1541 -0
- polyctl/parts/lib_next.py +652 -0
- polyctl/parts/lib_pr.py +331 -0
- polyctl/parts/lib_slices.py +3337 -0
- polyctl/parts/lib_state.py +2415 -0
- polyctl/parts/lib_transcript.py +4118 -0
- polyctl/pressure.py +325 -0
- polyctl/prices.json +47 -0
- polyctl/procs.py +1194 -0
- polyctl/settings.py +505 -0
- polyctl/skill/SKILL.md +365 -0
- polyctl/skillkit.py +503 -0
- polyctl/storage.py +2055 -0
- polyctl/telegram.py +327 -0
- polyctl/tiers.py +123 -0
- polyctl/verdicts.py +41 -0
- polyctl/watchdog.py +3887 -0
- polyctl/web.py +337 -0
- polyctl-0.7.0.dist-info/METADATA +235 -0
- polyctl-0.7.0.dist-info/RECORD +99 -0
- polyctl-0.7.0.dist-info/WHEEL +4 -0
- polyctl-0.7.0.dist-info/entry_points.txt +5 -0
- polyctl-0.7.0.dist-info/licenses/LICENSE +21 -0
|
@@ -0,0 +1,31 @@
|
|
|
1
|
+
{
|
|
2
|
+
"id": "trae", "name": "Trae Agent (ByteDance)", "verified": "untested",
|
|
3
|
+
"disclaimer": "Written from the documented interface, not verified against an install. Flags drift; correct and open a PR.",
|
|
4
|
+
"detect": { "headless": ["run"] },
|
|
5
|
+
"send": { "argv": ["trae-cli", "run", "{prompt}"], "cwd_matters": true },
|
|
6
|
+
"options": {
|
|
7
|
+
"provider": ["--provider", "{provider}"],
|
|
8
|
+
"provider_values": ["openai", "anthropic", "google", "openrouter", "doubao", "ollama"],
|
|
9
|
+
"model": ["--model", "{model}"],
|
|
10
|
+
"cwd": ["--working-dir", "{cwd}"],
|
|
11
|
+
"max_steps": ["--max-steps", "{max_steps}"],
|
|
12
|
+
"trace_file": ["--trajectory-file", "{path}"],
|
|
13
|
+
"trust_none": null,
|
|
14
|
+
"trust_none_why": "No documented read-only or tool-less mode. Until one exists this adapter is ineligible for the reviewer role: a reviewer that can write is not a reviewer, and guessing a flag would be worse than refusing.",
|
|
15
|
+
"trust_all": null,
|
|
16
|
+
"trust_all_why": "Tools are on by default; there is no flag to widen or narrow them."
|
|
17
|
+
},
|
|
18
|
+
"roles": {
|
|
19
|
+
"implementer": "eligible",
|
|
20
|
+
"reviewer": "ineligible: cannot be run without tools",
|
|
21
|
+
"architect": "untested: no resume, so a woken architect would start without its history"
|
|
22
|
+
},
|
|
23
|
+
"model_selection": {
|
|
24
|
+
"shape": "provider-and-model",
|
|
25
|
+
"why": "Unlike harnesses that take a single model id, this one names the provider separately, so a role binding here carries both and the family is read from the provider rather than inferred from the model string."
|
|
26
|
+
},
|
|
27
|
+
"resume": { "argv": null, "why": "No documented resume or continue; each run starts fresh." },
|
|
28
|
+
"transcript": { "kind": "json", "path": "trajectories/trajectory_*.json", "cwd_relative": true, "todo": "confirm record shape against an install" },
|
|
29
|
+
"busy": { "mtime_glob": "trajectories/trajectory_*.json", "cwd_relative": true, "idle_seconds": 240 },
|
|
30
|
+
"directives": { "config": "trae_config.yaml", "legacy_config": "trae_config.json" }
|
|
31
|
+
}
|
|
@@ -0,0 +1,42 @@
|
|
|
1
|
+
{
|
|
2
|
+
"about": "The canonical vendor list (#89). Every surface that names a harness derives from it: each shipped adapter is named by exactly one vendor, and a vendor with no adapter says why. `traycer` marks the vendors in Traycer's canonical enum (protocol/src/host/agent/shared.ts, read 2026-09-14), the coverage this list is measured against. `surfaces` are the names keyflip's surface list gives a vendor. `pr-agent` is not an agent but a reviewer polyctl runs as a tool (#86), and so is `openai-api`, polyctl's own client for an OpenAI-compatible chat API (API-REVIEWER).",
|
|
3
|
+
"vendors": [
|
|
4
|
+
{ "id": "claude", "adapter": "claude-code", "traycer": true },
|
|
5
|
+
{ "id": "codex", "adapter": "codex", "traycer": true, "surfaces": ["codex cli"] },
|
|
6
|
+
{ "id": "opencode", "adapter": "opencode", "traycer": true },
|
|
7
|
+
{ "id": "traycer", "adapter": null, "traycer": true,
|
|
8
|
+
"why": "an orchestrator of agents, as polyctl is, not an agent polyctl drives" },
|
|
9
|
+
{ "id": "cursor", "adapter": "cursor-agent", "traycer": true, "surfaces": ["cursor"] },
|
|
10
|
+
{ "id": "grok", "adapter": "grok", "traycer": true },
|
|
11
|
+
{ "id": "qwen", "adapter": "qwen", "traycer": true },
|
|
12
|
+
{ "id": "kiro", "adapter": "kiro", "traycer": true },
|
|
13
|
+
{ "id": "droid", "adapter": "droid", "traycer": true },
|
|
14
|
+
{ "id": "kimi", "adapter": "kimi", "traycer": true },
|
|
15
|
+
{ "id": "copilot", "adapter": "copilot", "traycer": true, "surfaces": ["github copilot"] },
|
|
16
|
+
{ "id": "kilocode", "adapter": "kilocode", "traycer": true },
|
|
17
|
+
{ "id": "openrouter", "adapter": null, "traycer": true,
|
|
18
|
+
"why": "a model router reached through a harness that takes provider/model, such as opencode or kilocode; not a harness itself" },
|
|
19
|
+
{ "id": "amp", "adapter": "amp", "traycer": true },
|
|
20
|
+
{ "id": "devin", "adapter": null, "traycer": true,
|
|
21
|
+
"why": "a hosted agent with no local command line; the pull requests it opens are observed through cloud-generic" },
|
|
22
|
+
{ "id": "pi", "adapter": "pi", "traycer": true },
|
|
23
|
+
{ "id": "hermes", "adapter": "hermes", "traycer": true },
|
|
24
|
+
{ "id": "omp", "adapter": "omp", "traycer": true },
|
|
25
|
+
{ "id": "huggingface", "adapter": null, "traycer": true,
|
|
26
|
+
"why": "a model hub and inference provider reached through a harness, not a harness" },
|
|
27
|
+
{ "id": "reasonix", "adapter": "reasonix", "traycer": true },
|
|
28
|
+
{ "id": "antigravity", "adapter": "antigravity", "traycer": true },
|
|
29
|
+
{ "id": "aider", "adapter": "aider" },
|
|
30
|
+
{ "id": "amazon-q", "adapter": "amazon-q" },
|
|
31
|
+
{ "id": "command-code", "adapter": "command-code" },
|
|
32
|
+
{ "id": "deepseek", "adapter": "deepseek" },
|
|
33
|
+
{ "id": "gemini", "adapter": "gemini", "surfaces": ["gemini cli"] },
|
|
34
|
+
{ "id": "ollama", "adapter": "ollama" },
|
|
35
|
+
{ "id": "qoder", "adapter": "qoder" },
|
|
36
|
+
{ "id": "trae", "adapter": "trae" },
|
|
37
|
+
{ "id": "warp", "adapter": "warp" },
|
|
38
|
+
{ "id": "cloud", "adapter": "cloud-generic" },
|
|
39
|
+
{ "id": "pr-agent", "adapter": "pr-agent" },
|
|
40
|
+
{ "id": "openai-api", "adapter": "openai-api" }
|
|
41
|
+
]
|
|
42
|
+
}
|
|
@@ -0,0 +1,88 @@
|
|
|
1
|
+
{
|
|
2
|
+
"id": "warp",
|
|
3
|
+
"name": "Warp (the Oz agent CLI)",
|
|
4
|
+
"project_config": [".warp", ".agents"],
|
|
5
|
+
"contract": 1,
|
|
6
|
+
"verified": "partial",
|
|
7
|
+
"verified_version": "Oz v0.2026.10.07.08.29.stable_00, macOS; the command surface read 2026-10-15, a completed turn and the two records that answer for it read 2026-10-16",
|
|
8
|
+
"observation_mode": "call-return",
|
|
9
|
+
"disclaimer": "The command surface and one completed turn are measured. Every flag below came from this build's own `--help` on 2026-10-15, and one real turn measured the failure path: `oz agent run -p ... --model <a custom endpoint's model id> --no-snapshot --output-format json` authenticated as the person's Warp account, sent the request to the endpoint that person configured, and ended at that provider's daily token cap with exit 1 and the cap's own JSON on stderr. On 2026-10-16, with the cap reset, a run completed: its stdout stream is three JSON lines ending in the agent's own text; `oz run get <task id> --output-format json` answers state, run time and usage for it (`result_record`); `oz run conversation get <conversation id> --output-format json` answers its messages, the assistant's words among them (`conversation`); and `--conversation` continued the same conversation. Still unmeasured, and declared nowhere: a tool call's event, the stdout of a completed `--output-format json` run, whether an id the desktop app's store names means anything to `--conversation`, and whether a turn that edits writes in place or in a cloud workspace.",
|
|
10
|
+
"notes": "The desktop app and the CLI are one bundle: /Applications/Warp.app/Contents/Resources/bin/oz is a two-line script that execs Contents/MacOS/stable, the app's own binary, under a different argv[0]. `warp` on PATH is Cloudflare's VPN (`warp-cli`), a different product that shares the first letter, and nothing here keys on that name. The app keeps its state in ~/Library/Group Containers/2BBY89MBSN.dev.warp/Library/Application Support/dev.warp.Warp-Stable/warp.sqlite, mapped on this machine 2026-10-15: 52 tables, 250 turns in `ai_queries` across 24 conversations in `agent_conversations`, one working directory and one title each. This adapter declares no store over it, for a measured reason: the CLI run above changed none of those counts and its conversation id is in no table, so the store holds the app's conversations and not the ones polyctl starts, and a store that names another agent's sessions to a panel reading them as an implementer's is the misreading this project refuses. Watching the app's own sessions is a second adapter's work; its queries, its timestamps and the three readings it supports are written up in docs/audit/2026-10-15-warp-store.md, amended 2026-10-16 with the runs that answered. CLI logs live in ~/Library/Logs/oz; neither that log directory nor the app's state container is a program installation directory. `oz mcp` manages servers, and `--mcp <path|json>` attaches some to one run, with `--strict-mcp-startup` and `--mcp-startup-timeout <duration>` beside it (this build's help). Where the app keeps its own list was not read: `active_mcp_servers` and `mcp_server_installations` hold 0 rows here, so no file and no key is declared, and `polyctl init` writes no Warp configuration.",
|
|
11
|
+
"detect": {
|
|
12
|
+
"dirs": [".warp"],
|
|
13
|
+
"binaries": ["oz"],
|
|
14
|
+
"headless": ["-p", "--prompt", "--saved-prompt"],
|
|
15
|
+
"config": ["~/.warp"],
|
|
16
|
+
"install_dirs": ["/Applications/Warp.app/Contents/Resources/bin", "~/Applications/Warp.app/Contents/Resources/bin"],
|
|
17
|
+
"note": "Nothing named `oz` was on PATH on the machine measured: the app had made no link for it, and `command -v oz` answered nothing. polyctl finds the bundle's oz where Warp installs it, in /Applications/Warp.app/Contents/Resources/bin or ~/Applications/Warp.app/Contents/Resources/bin, even when it is not on PATH. A headless turn is `agent run` with its prompt flag; `run` is deliberately not declared headless, because `oz run list`, `oz run get` and `oz run conversation get` are reads polyctl must not mistake for a turn it owns and may stop. `oz run list --output-format json` answered with no runs on the machine measured although two runs of 2026-10-16 exist and both are readable by id, so it is no session index either."
|
|
18
|
+
},
|
|
19
|
+
"send": {
|
|
20
|
+
"argv": ["oz", "agent", "run", "-p", "{prompt}"],
|
|
21
|
+
"cwd_matters": true,
|
|
22
|
+
"note": "The measured run took the directory it was given, ran with `--no-snapshot` so it uploaded no copy of it, and left the throwaway directory it worked in empty - a prompt that asked for no tool changes. Whether a turn that edits writes in place or in a cloud workspace was not answered by it, and polyctl has no reading of that until one does."
|
|
23
|
+
},
|
|
24
|
+
"resume": {
|
|
25
|
+
"argv": ["oz", "agent", "run", "--conversation", "{session}", "-p", "{prompt}"],
|
|
26
|
+
"note": "`--conversation <ID>` reads, in the same help, as 'Continue an existing cloud conversation by ID'. Exercised 2026-10-16: a second run given the first run's conversation id continued that conversation - its `conversation_started` event named the id it was given, and the conversation record then held both turns' messages, both under one step. What it accepts from elsewhere is still unmeasured: whether an id the desktop app's store names means anything here has not been tried. The CLI keeps its conversations on the server; the app's store holds none of them."
|
|
27
|
+
},
|
|
28
|
+
"options": {
|
|
29
|
+
"trust_none": null,
|
|
30
|
+
"trust_none_why": "no flag denies tools: `oz agent run --help` (this build, 2026-10-15) names no permission, tool, read-only or sandbox argument, and what the agent may do is decided in the person's app or in an agent profile. Ineligible for the reviewer role until a way to deny tools exists.",
|
|
31
|
+
"trust_all": null,
|
|
32
|
+
"trust_all_why": "no flag approves every tool either. Auto-execution is a setting a run inherits rather than an argument: `autoexecute_override` read 'RespectUserSettings' in all 24 of the app's stored conversations, and the CLI names no override for it. polyctl can neither widen a Warp turn nor narrow one, which means a Warp wake runs with whatever the person's app already allows - and polyctl cannot claim that grant is scoped.",
|
|
33
|
+
"model": ["--model", "{model}"],
|
|
34
|
+
"model_format": "an id `oz model list` prints: named models (auto, auto-genius, claude-4-5-haiku, ...) beside one UUID per model of every custom endpoint the person configured",
|
|
35
|
+
"agent_profile": ["--profile", "{agent}"],
|
|
36
|
+
"output_json": ["--output-format", "json"],
|
|
37
|
+
"output_stream": ["--output-format", "ndjson"],
|
|
38
|
+
"cwd": ["-C", "{cwd}"],
|
|
39
|
+
"effort": null,
|
|
40
|
+
"note": "`--model` was measured to route: the run named the UUID of a model of the person's own custom endpoint and the request went to that endpoint's /v1/chat/completions, which answered with its daily cap - so a BYOK endpoint configured in the app is a model a headless turn can take. `--profile` takes an id from `oz agent profile list`, which holds one here (Unsynced, named Default). No effort, mode, step-limit or timeout argument exists in this help, so none is declared, and no flag pins the permission mode: see trust_all_why."
|
|
41
|
+
},
|
|
42
|
+
"transcript": {
|
|
43
|
+
"kind": "call-return",
|
|
44
|
+
"note": "What a completed turn wrote on standard output, one JSON object to a line: {\"type\":\"system\",\"event_type\":\"run_started\",\"run_id\":\"<run id>\",\"run_url\":\"https://oz.warp.dev/runs/<run id>\"}, then {\"type\":\"system\",\"event_type\":\"conversation_started\",\"conversation_id\":\"<conversation id>\"}, then {\"type\":\"agent\",\"text\":\"<the agent's words>\"} - three lines and nothing after, measured 2026-10-16 on a first turn and on a resumed one. The turn of 2026-10-15 that died at the provider wrote the first two and then its error on stderr with exit 1. No line above is read as a record kind or as words: the ids they carry are the handles the two reads `result_record` and `conversation` below take, and a tool call's event was never seen, so tool calls are read nowhere. The stdout of a completed `--output-format json` run (one object, not lines) was not captured, and nothing reads it."
|
|
45
|
+
},
|
|
46
|
+
"result_record": {
|
|
47
|
+
"argv": ["oz", "run", "get", "{run}", "--output-format", "json"],
|
|
48
|
+
"session_id": "conversation_id",
|
|
49
|
+
"status": "state",
|
|
50
|
+
"status_values": ["SUCCEEDED"],
|
|
51
|
+
"duration": "run_time",
|
|
52
|
+
"verified_example": "{\"conversation_id\":\"<conversation id>\",\"state\":\"SUCCEEDED\",\"run_time\":\"PT33S\",\"request_usage\":{\"total_tokens\":87739,\"model_token_usage\":[{\"model_id\":\"<model id>\",\"total_tokens\":87739,\"usage_type\":\"custom_endpoint\"}]},\"status_message\":{\"message\":\"…\"}}",
|
|
53
|
+
"note": "`{run}` is the run id the stream's `run_started` event carries; the record repeats it as both `task_id` and `run_id` (equal in the measured runs). `oz run get <task id> --output-format json` prints one JSON object; the keys measured include state, run_time, conversation_id, request_usage, status_message, started_at, updated_at, prompt, title, session_link and finished_at - and without `--output-format json` it prints a TUI box even when no terminal is attached. The answer is not in the object: `status_message.message` is the harness's own summary of the turn, not its words, and the words are read from `conversation` instead. `run_time` is an ISO 8601 duration (PT55S and PT33S measured). Usage is the conversation's as of the read, not the turn's: the same run's record answered 40898 tokens before its conversation's second turn and 87739 after it, with `updated_at` unmoved. `finished_at` read null on a run whose state was SUCCEEDED, so it is no finish clock."
|
|
54
|
+
},
|
|
55
|
+
"conversation": {
|
|
56
|
+
"argv": ["oz", "run", "conversation", "get", "{session}", "--output-format", "json"],
|
|
57
|
+
"returns": "{conversation_id, steps: [{id, description, started_at, completed_at, steps: [], messages: [{role: user | assistant, content: [{type: text, text, message_id}], message_ids, request_id, timestamp}]}]}",
|
|
58
|
+
"note": "`{session}` is the conversation id the stream's `conversation_started` event carries, which is also the id `--conversation` accepts. The words of a turn are the `text` of an `assistant` message's `content[]` block; `user` messages hold the prompt. A resumed turn joins the last step rather than opening one: two runs of one conversation left four messages under one step. A message's `timestamp` is the step's write time, not when the words were said - the first turn's messages carried the moment its run completed. `oz run get <task id> --conversation --output-format json` returns the same object, and without `--output-format json` both print a TUI box. Declared for reference, like `list_sessions` elsewhere: nothing reads it yet, and it is no store - these steps are not polyctl's turns and no session is resolved from them."
|
|
59
|
+
},
|
|
60
|
+
"busy": {
|
|
61
|
+
"kind": "orchestrator-owned",
|
|
62
|
+
"note": "polyctl starts the run and waits on it, so it knows a turn is in flight without asking a file. The app's database is not that clock: its -wal moves whenever the desktop agent writes anything, whatever the CLI is doing."
|
|
63
|
+
},
|
|
64
|
+
"telemetry": {
|
|
65
|
+
"cost": {
|
|
66
|
+
"from": "call-return",
|
|
67
|
+
"fields": ["request_usage.total_tokens"],
|
|
68
|
+
"unit": "token",
|
|
69
|
+
"verified": true,
|
|
70
|
+
"note": "Read from the run record whose command `result_record.argv` names. It is the conversation's total as of the read, not one turn's: the same run answered 40898 tokens before its conversation's second turn and 87739 after it, with `updated_at` unmoved. `request_usage.model_token_usage[]` splits it per model with a `usage_type` ('custom_endpoint' measured). The per-category split was read and is written down, not declared: `request_usage.usage_by_category.<category>.custom_endpoint_inference_usage.<model id>.token_count` held input 87479 and output 260 in the measured example, and inference_cost, inference_cost_usd and the cost_in_cents blocks all read 0 there - a Warp-hosted model's breakdown was never seen."
|
|
71
|
+
},
|
|
72
|
+
"duration": { "from": "call-return", "field": "run_time", "verified": true,
|
|
73
|
+
"note": "ISO 8601 duration in the run record: PT55S and PT33S measured." },
|
|
74
|
+
"context": {
|
|
75
|
+
"from": "none",
|
|
76
|
+
"note": "The app keeps a context percentage per conversation - `context_window_usage` inside a JSON column of `agent_conversations`, 0.166 on the newest one measured - but that is a conversation of the desktop app, not one polyctl starts, and the CLI's own reply is unmeasured. Nothing is declared over either."
|
|
77
|
+
},
|
|
78
|
+
"failure": {
|
|
79
|
+
"from": "none",
|
|
80
|
+
"note": "One measured failure of a run reaches polyctl as exit status and stderr text, not as a record: the provider's own answer came through inside the harness's error line, with its reset time in it, which is the reading `polyctl wake` would need and does not have a path to yet. No failed run's record was read: SUCCEEDED is the only `state` value seen, and what a failed run's state and status_message hold is unmeasured, so nothing is declared from them."
|
|
81
|
+
},
|
|
82
|
+
"balance": { "from": "none" }
|
|
83
|
+
},
|
|
84
|
+
"directives": {
|
|
85
|
+
"skills_dir": ".warp/skills",
|
|
86
|
+
"note": "`--skill <SKILL>` reads, in this build's help: skills are searched in `.agents/skills/`, `.warp/skills/`, `.claude/skills/` and `.codex/skills/`, so `.warp/skills` is the one declared. Whether a Warp turn honours AGENTS.md was not measured; the app keeps a `project_rules` table and it holds 0 rows on this machine, so nothing is claimed about rules."
|
|
87
|
+
}
|
|
88
|
+
}
|