codeply-cli 0.3.1 → 0.4.1

package/skills/ito-compute/SKILL.md

@@ -1,129 +1,129 @@
----
-name: ito-compute
-description: Query live GPU inventory, submit an authenticated Itô fixed-rate RFQ, inspect RFQ or procurement status, and run explicitly gated node qualification through the separately installed canonical CLI. Use when a user asks to find H100/H200 capacity, request a fixed compute rate, check Itô compute status, or validate GPU nodes.
-metadata:
-  origin: ECC
----
-
-# Itô Compute
-
-Use the canonical Itô compute CLI or MCP server. ECC does not implement a
-parallel client, browser handoff, local simulation, reservation, workload
-runner, or inference server.
-
-## Install the canonical local package
-
-`ito-compute-cli` is currently unpublished. Build it from its canonical
-repository instead of using `npx`, `npm exec`, or an unverified package:
-
-```sh
-git clone https://github.com/Ito-Markets/ito-cloud-runtime.git
-cd ito-cloud-runtime/cli/ito-compute-cli
-npm ci
-npm run check
-```
-
-Set `ECC_ITO_CLI_EXECUTABLE` to the explicit absolute built entry:
-
-```text
-/absolute/path/to/ito-cloud-runtime/cli/ito-compute-cli/dist/bin/ito.js
-```
-
-ECC never discovers this credential-bearing client through `PATH`.
-Inject `ITO_API_KEY` through 1Password or the launching process environment.
-Never put it in arguments, tracked files, MCP results, logs, or chat.
-
-## CLI workflow
-
-1. Run `ecc ito auth` before the first operation.
-2. Before `ecc ito find`, obtain explicit buyer authority to submit an RFQ.
-   - Require `gpu`, `count`, whole `days`, `max-rate`, `nodes`,
-     `gpus-per-node`, `storage-tb`, `start-window`, `form-factor`,
-     `contract-type`, `fabric`, `region`, and the split-fill decision.
-   - Require `count == nodes * gpus-per-node`; never derive topology.
-   - Use `any` only when the buyer explicitly accepts any fabric or region.
-   - Omitted `--allow-split` means false.
-3. Run the live RFQ command:
-
-   ```sh
-   ecc ito find \
-     --gpu h200 \
-     --count 8 \
-     --nodes 1 \
-     --gpus-per-node 8 \
-     --days 30 \
-     --storage-tb 1 \
-     --start-window 2099-08-15 \
-     --max-rate 3.00 \
-     --form-factor bare_metal \
-     --contract-type reservation \
-     --fabric infiniband \
-     --region us-east-1
-   ```
-
-4. Run `ecc ito status` to inspect RFQs and procurement orders.
-   After an ambiguous transport failure, check status before repeating `find`.
-
-Inventory prices are indicative. An RFQ is not reserved capacity. Treat a rate
-as fixed only when the canonical result contains a non-null firm quote.
-
-## Live node qualification
-
-`ecc ito evals` exposes the canonical CLI's narrow live adapter to a separately
-installed `sixtytwo-cli==0.3.33`. It does not expose local fixture execution
-through ECC.
-Require all of the following before invoking it:
-
-- operator authorization to contact the named nodes;
-- `ITO_ENABLE_SIXTYTWO_LIVE=1`;
-- `--live-sixtytwo`;
-- an explicit node list; and
-- an existing absolute config directory containing `sixtytwo.yaml`.
-
-```sh
-ecc ito evals \
-  --cluster clu_prod_example \
-  --live-sixtytwo \
-  --nodes gpu-01,gpu-02 \
-  --config-dir /absolute/path/to/qualification-config
-```
-
-The canonical adapter can run only the pinned version check and
-`sixtytwo test --full` against the explicit nodes. It cannot rent, launch,
-recover, repair, reset, purchase, or order resources. ECC does not forward
-`ITO_API_KEY` or model/cloud credentials into node qualification.
-
-## MCP workflow
-
-Build the canonical package, then configure the stdio server with an absolute
-path:
-
-```json
-{
-  "mcpServers": {
-    "ito-compute": {
-      "command": "node",
-      "args": [
-        "/absolute/path/to/ito-cloud-runtime/cli/ito-compute-cli/dist/bin/ito-mcp.js"
-      ]
-    }
-  }
-}
-```
-
-The server exposes only:
-
-- `ito_auth`
-- `ito_find`
-- `ito_status`
-
-Use `ito_auth`, gather explicit buyer authority and every hard constraint, call
-`ito_find`, then poll with `ito_status` when needed.
-
-## Unsupported operations
-
-The supported client surface cannot lock quotes, reserve capacity, execute
-workloads, or serve inference. The MCP server does not expose qualification;
-use the explicit CLI command above. Do not invent additional tools or a
-purchase path. Do not substitute a browser or fixture when the local CLI is
-missing or a live operation fails. Report the missing capability and stop.
+---
+name: ito-compute
+description: Query live GPU inventory, submit an authenticated Itô fixed-rate RFQ, inspect RFQ or procurement status, and run explicitly gated node qualification through the separately installed canonical CLI. Use when a user asks to find H100/H200 capacity, request a fixed compute rate, check Itô compute status, or validate GPU nodes.
+metadata:
+  origin: ECC
+---
+
+# Itô Compute
+
+Use the canonical Itô compute CLI or MCP server. ECC does not implement a
+parallel client, browser handoff, local simulation, reservation, workload
+runner, or inference server.
+
+## Install the canonical local package
+
+`ito-compute-cli` is currently unpublished. Build it from its canonical
+repository instead of using `npx`, `npm exec`, or an unverified package:
+
+```sh
+git clone https://github.com/Ito-Markets/ito-cloud-runtime.git
+cd ito-cloud-runtime/cli/ito-compute-cli
+npm ci
+npm run check
+```
+
+Set `ECC_ITO_CLI_EXECUTABLE` to the explicit absolute built entry:
+
+```text
+/absolute/path/to/ito-cloud-runtime/cli/ito-compute-cli/dist/bin/ito.js
+```
+
+ECC never discovers this credential-bearing client through `PATH`.
+Inject `ITO_API_KEY` through 1Password or the launching process environment.
+Never put it in arguments, tracked files, MCP results, logs, or chat.
+
+## CLI workflow
+
+1. Run `ecc ito auth` before the first operation.
+2. Before `ecc ito find`, obtain explicit buyer authority to submit an RFQ.
+   - Require `gpu`, `count`, whole `days`, `max-rate`, `nodes`,
+     `gpus-per-node`, `storage-tb`, `start-window`, `form-factor`,
+     `contract-type`, `fabric`, `region`, and the split-fill decision.
+   - Require `count == nodes * gpus-per-node`; never derive topology.
+   - Use `any` only when the buyer explicitly accepts any fabric or region.
+   - Omitted `--allow-split` means false.
+3. Run the live RFQ command:
+
+   ```sh
+   ecc ito find \
+     --gpu h200 \
+     --count 8 \
+     --nodes 1 \
+     --gpus-per-node 8 \
+     --days 30 \
+     --storage-tb 1 \
+     --start-window 2099-08-15 \
+     --max-rate 3.00 \
+     --form-factor bare_metal \
+     --contract-type reservation \
+     --fabric infiniband \
+     --region us-east-1
+   ```
+
+4. Run `ecc ito status` to inspect RFQs and procurement orders.
+   After an ambiguous transport failure, check status before repeating `find`.
+
+Inventory prices are indicative. An RFQ is not reserved capacity. Treat a rate
+as fixed only when the canonical result contains a non-null firm quote.
+
+## Live node qualification
+
+`ecc ito evals` exposes the canonical CLI's narrow live adapter to a separately
+installed `sixtytwo-cli==0.3.33`. It does not expose local fixture execution
+through ECC.
+Require all of the following before invoking it:
+
+- operator authorization to contact the named nodes;
+- `ITO_ENABLE_SIXTYTWO_LIVE=1`;
+- `--live-sixtytwo`;
+- an explicit node list; and
+- an existing absolute config directory containing `sixtytwo.yaml`.
+
+```sh
+ecc ito evals \
+  --cluster clu_prod_example \
+  --live-sixtytwo \
+  --nodes gpu-01,gpu-02 \
+  --config-dir /absolute/path/to/qualification-config
+```
+
+The canonical adapter can run only the pinned version check and
+`sixtytwo test --full` against the explicit nodes. It cannot rent, launch,
+recover, repair, reset, purchase, or order resources. ECC does not forward
+`ITO_API_KEY` or model/cloud credentials into node qualification.
+
+## MCP workflow
+
+Build the canonical package, then configure the stdio server with an absolute
+path:
+
+```json
+{
+  "mcpServers": {
+    "ito-compute": {
+      "command": "node",
+      "args": [
+        "/absolute/path/to/ito-cloud-runtime/cli/ito-compute-cli/dist/bin/ito-mcp.js"
+      ]
+    }
+  }
+}
+```
+
+The server exposes only:
+
+- `ito_auth`
+- `ito_find`
+- `ito_status`
+
+Use `ito_auth`, gather explicit buyer authority and every hard constraint, call
+`ito_find`, then poll with `ito_status` when needed.
+
+## Unsupported operations
+
+The supported client surface cannot lock quotes, reserve capacity, execute
+workloads, or serve inference. The MCP server does not expose qualification;
+use the explicit CLI command above. Do not invent additional tools or a
+purchase path. Do not substitute a browser or fixture when the local CLI is
+missing or a live operation fails. Report the missing capability and stop.

package/skills/ito-data-atlas-agent/SKILL.md

@@ -1,64 +1,64 @@
----
-name: ito-data-atlas-agent
-description: Design background Data Atlas style agents for Itô basket research, market discovery, parameter drafting, and human-in-the-loop editing. Use for architecture and workflow planning, not live order execution.
-metadata:
-  origin: ECC
----
-
-# Itô Data Atlas Agent
-
-Use this skill to design an agent that watches data sources, builds candidate
-prediction-market baskets, drafts parameter changes, and hands the result to a
-human for review.
-
-This skill describes architecture and workflow. It does not run live trading.
-
-## Guardrails
-
-- Keep all execution behind explicit human approval.
-- Require `ITO_API_KEY` only for read-only Itô data access unless a separate
-  private implementation explicitly adds execution controls.
-- Do not persist private user data unless the target repo already has a storage
-  contract and the user asks for it.
-- Do not expose private strategy logic, venue credentials, or local paths in
-  public docs.
-
-## Architecture Pattern
-
-Use four lanes:
-
-1. Research collector: public web, X, GitHub, venue docs, API metadata, and
-   Itô read endpoints when gated access exists.
-2. Basket drafter: turns sources into candidate underliers, weights, rules, and
-   questions.
-3. Risk reviewer: checks data freshness, venue limits, resolution ambiguity,
-   compliance notes, and prompt-injection exposure.
-4. Human editor: opens a chat or UI state where the user can approve, reject,
-   adjust, or ask for more research.
-
-## Workflow
-
-1. Define the user objective and excluded actions.
-2. List data sources and access requirements.
-3. Draft a basket spec with provenance for every underlier.
-4. Produce editable parameters rather than executable orders.
-5. Store an audit trail: inputs, model output, sources, and human decision.
-
-## Useful Skill Chains
-
-- `deep-research` for source collection.
-- `x-api` for current social/event signal.
-- `ito-market-intelligence` for venue and underlier context.
-- `ito-basket-compare` for user knowledge-base matching.
-- `prediction-market-risk-review` before any execution-capable integration.
-
-## Output Contract
-
-Return an implementation-ready workflow spec with:
-
-- data sources
-- access gates
-- agent roles
-- human approval points
-- storage/audit boundary
-- non-goals
+---
+name: ito-data-atlas-agent
+description: Design background Data Atlas style agents for Itô basket research, market discovery, parameter drafting, and human-in-the-loop editing. Use for architecture and workflow planning, not live order execution.
+metadata:
+  origin: ECC
+---
+
+# Itô Data Atlas Agent
+
+Use this skill to design an agent that watches data sources, builds candidate
+prediction-market baskets, drafts parameter changes, and hands the result to a
+human for review.
+
+This skill describes architecture and workflow. It does not run live trading.
+
+## Guardrails
+
+- Keep all execution behind explicit human approval.
+- Require `ITO_API_KEY` only for read-only Itô data access unless a separate
+  private implementation explicitly adds execution controls.
+- Do not persist private user data unless the target repo already has a storage
+  contract and the user asks for it.
+- Do not expose private strategy logic, venue credentials, or local paths in
+  public docs.
+
+## Architecture Pattern
+
+Use four lanes:
+
+1. Research collector: public web, X, GitHub, venue docs, API metadata, and
+   Itô read endpoints when gated access exists.
+2. Basket drafter: turns sources into candidate underliers, weights, rules, and
+   questions.
+3. Risk reviewer: checks data freshness, venue limits, resolution ambiguity,
+   compliance notes, and prompt-injection exposure.
+4. Human editor: opens a chat or UI state where the user can approve, reject,
+   adjust, or ask for more research.
+
+## Workflow
+
+1. Define the user objective and excluded actions.
+2. List data sources and access requirements.
+3. Draft a basket spec with provenance for every underlier.
+4. Produce editable parameters rather than executable orders.
+5. Store an audit trail: inputs, model output, sources, and human decision.
+
+## Useful Skill Chains
+
+- `deep-research` for source collection.
+- `x-api` for current social/event signal.
+- `ito-market-intelligence` for venue and underlier context.
+- `ito-basket-compare` for user knowledge-base matching.
+- `prediction-market-risk-review` before any execution-capable integration.
+
+## Output Contract
+
+Return an implementation-ready workflow spec with:
+
+- data sources
+- access gates
+- agent roles
+- human approval points
+- storage/audit boundary
+- non-goals

package/skills/ito-market-intelligence/SKILL.md

@@ -1,61 +1,61 @@
----
-name: ito-market-intelligence
-description: Research prediction-market events, venues, underliers, liquidity, and news context for Itô basket workflows. Use for read-only market intelligence, API-gated Itô exploration, and source-grounded prediction-market briefings without investment advice or live trading.
-metadata:
-  origin: ECC
----
-
-# Itô Market Intelligence
-
-Use this skill when a user wants prediction-market context, event discovery,
-venue comparison, basket theme exploration, or an Itô API-backed market brief.
-
-This is a public teaser skill. It can work with public sources by default. Any
-Itô-backed data call requires explicit API access through `ITO_API_KEY`.
-
-## Guardrails
-
-- Do not provide investment, legal, tax, or trading advice.
-- Do not place, cancel, route, or simulate live orders.
-- Do not infer the user's financial situation unless they provide it.
-- Treat Polymarket, Kalshi, Itô, X, Exa, GitHub, and web data as source inputs,
-  not as truth by themselves.
-- Separate facts, market-implied signals, and your interpretation.
-
-## Workflow
-
-1. Clarify the market theme, venue, geography, and time horizon.
-2. Gather public market data from venue docs/APIs or source-grounded research.
-3. If `ITO_API_KEY` is present and the user explicitly asks for Itô data, call
-   only read endpoints and state that access is gated.
-4. Normalize event, underlier, liquidity, fee, resolution, and data-latency
-   differences across venues.
-5. Produce a decision brief:
-   - market/event summary
-   - available venues and underliers
-   - liquidity and data-quality caveats
-   - relevant news/source context
-   - open questions before any user action
-
-## Useful Skill Chains
-
-- Use `deep-research` or `exa-search` for source discovery.
-- Use `x-api` for public social signal discovery when X access is configured.
-- Use `market-research` for market sizing, competitors, or business use cases.
-- Use `prediction-market-risk-review` before any workflow touches user capital,
-  portfolio data, or execution-capable credentials.
-
-## Output Contract
-
-Default to a compact brief with source links and a clear caveat:
-
-```text
-This is market intelligence, not investment or trading advice.
-```
-
-If access is missing, say:
-
-```text
-Itô live basket/API data requires gated access. Request an ITO_API_KEY before
-using Itô-backed reads.
-```
+---
+name: ito-market-intelligence
+description: Research prediction-market events, venues, underliers, liquidity, and news context for Itô basket workflows. Use for read-only market intelligence, API-gated Itô exploration, and source-grounded prediction-market briefings without investment advice or live trading.
+metadata:
+  origin: ECC
+---
+
+# Itô Market Intelligence
+
+Use this skill when a user wants prediction-market context, event discovery,
+venue comparison, basket theme exploration, or an Itô API-backed market brief.
+
+This is a public teaser skill. It can work with public sources by default. Any
+Itô-backed data call requires explicit API access through `ITO_API_KEY`.
+
+## Guardrails
+
+- Do not provide investment, legal, tax, or trading advice.
+- Do not place, cancel, route, or simulate live orders.
+- Do not infer the user's financial situation unless they provide it.
+- Treat Polymarket, Kalshi, Itô, X, Exa, GitHub, and web data as source inputs,
+  not as truth by themselves.
+- Separate facts, market-implied signals, and your interpretation.
+
+## Workflow
+
+1. Clarify the market theme, venue, geography, and time horizon.
+2. Gather public market data from venue docs/APIs or source-grounded research.
+3. If `ITO_API_KEY` is present and the user explicitly asks for Itô data, call
+   only read endpoints and state that access is gated.
+4. Normalize event, underlier, liquidity, fee, resolution, and data-latency
+   differences across venues.
+5. Produce a decision brief:
+   - market/event summary
+   - available venues and underliers
+   - liquidity and data-quality caveats
+   - relevant news/source context
+   - open questions before any user action
+
+## Useful Skill Chains
+
+- Use `deep-research` or `exa-search` for source discovery.
+- Use `x-api` for public social signal discovery when X access is configured.
+- Use `market-research` for market sizing, competitors, or business use cases.
+- Use `prediction-market-risk-review` before any workflow touches user capital,
+  portfolio data, or execution-capable credentials.
+
+## Output Contract
+
+Default to a compact brief with source links and a clear caveat:
+
+```text
+This is market intelligence, not investment or trading advice.
+```
+
+If access is missing, say:
+
+```text
+Itô live basket/API data requires gated access. Request an ITO_API_KEY before
+using Itô-backed reads.
+```

package/skills/ito-trade-planner/SKILL.md

@@ -1,68 +1,68 @@
----
-name: ito-trade-planner
-description: Build a non-advisory prediction-market trade planning worksheet for Itô or venue workflows. Use to inspect venues, underliers, constraints, order prerequisites, and manual execution steps without placing trades or recommending positions.
-metadata:
-  origin: ECC
----
-
-# Itô Trade Planner
-
-Use this skill when a user wants a structured worksheet for a prediction-market
-idea, basket adjustment, venue comparison, or manual execution plan.
-
-The skill is intentionally non-executing. It produces checklists and parameter
-tables the user can review manually.
-
-## Guardrails
-
-- Do not say a trade is good, bad, optimal, or recommended.
-- Do not provide investment advice or position sizing advice.
-- Do not place, cancel, route, or sign orders.
-- Do not request private keys, seed phrases, exchange passwords, or wallet
-  credentials.
-- Require explicit user approval before any workflow moves from research to
-  execution-capable tooling.
-
-## Planning Workflow
-
-1. Restate the user's idea as a neutral hypothesis.
-2. Identify markets, venues, underliers, resolution rules, fees, and data
-   freshness constraints.
-3. If `ITO_API_KEY` is configured and requested, read Itô basket metadata.
-4. Build a manual worksheet:
-   - market/underlier
-   - venue
-   - data source
-   - current observable price or status
-   - resolution rule
-   - liquidity caveat
-   - open questions
-   - manual action link or next review step
-5. Run `prediction-market-risk-review` before discussing automation, keys,
-   venue auth, or capital constraints.
-
-## Allowed Language
-
-Use:
-
-- "manual planning worksheet"
-- "questions to answer before acting"
-- "observable venue data"
-- "risk and constraint review"
-
-Avoid:
-
-- "you should buy/sell"
-- "best trade"
-- "guaranteed"
-- "risk-free"
-- "optimal size"
-
-## Output Contract
-
-End every plan with:
-
-```text
-This is a planning worksheet, not investment or trading advice. Review venue
-rules and make any trading decisions yourself.
-```
+---
+name: ito-trade-planner
+description: Build a non-advisory prediction-market trade planning worksheet for Itô or venue workflows. Use to inspect venues, underliers, constraints, order prerequisites, and manual execution steps without placing trades or recommending positions.
+metadata:
+  origin: ECC
+---
+
+# Itô Trade Planner
+
+Use this skill when a user wants a structured worksheet for a prediction-market
+idea, basket adjustment, venue comparison, or manual execution plan.
+
+The skill is intentionally non-executing. It produces checklists and parameter
+tables the user can review manually.
+
+## Guardrails
+
+- Do not say a trade is good, bad, optimal, or recommended.
+- Do not provide investment advice or position sizing advice.
+- Do not place, cancel, route, or sign orders.
+- Do not request private keys, seed phrases, exchange passwords, or wallet
+  credentials.
+- Require explicit user approval before any workflow moves from research to
+  execution-capable tooling.
+
+## Planning Workflow
+
+1. Restate the user's idea as a neutral hypothesis.
+2. Identify markets, venues, underliers, resolution rules, fees, and data
+   freshness constraints.
+3. If `ITO_API_KEY` is configured and requested, read Itô basket metadata.
+4. Build a manual worksheet:
+   - market/underlier
+   - venue
+   - data source
+   - current observable price or status
+   - resolution rule
+   - liquidity caveat
+   - open questions
+   - manual action link or next review step
+5. Run `prediction-market-risk-review` before discussing automation, keys,
+   venue auth, or capital constraints.
+
+## Allowed Language
+
+Use:
+
+- "manual planning worksheet"
+- "questions to answer before acting"
+- "observable venue data"
+- "risk and constraint review"
+
+Avoid:
+
+- "you should buy/sell"
+- "best trade"
+- "guaranteed"
+- "risk-free"
+- "optimal size"
+
+## Output Contract
+
+End every plan with:
+
+```text
+This is a planning worksheet, not investment or trading advice. Review venue
+rules and make any trading decisions yourself.
+```