@aopslabs/aops 0.3.31 → 0.3.33

package/agent-assets-release/agent-assets/core/bc42dd7792dbe66040e99a7ef3d80b3bc788c72b369b5a065cf936aef29f53fb/files/SKILL.md

@@ -1,47 +0,0 @@
----
-name: aops
-description: Route AOPS Community requests to concise packaged references, current CLI help, or live tool schema without selecting a work method.
----
-
-# AOPS Community
-
-AOPS is a self-hostable operations layer. The `aops` command installs and
-operates a local server, connects to remote servers, discovers live domain
-capabilities, and manages verified machine-local agent assets.
-
-This root skill is deliberately small. Read exactly one matching reference,
-then open only the relevant heading in its linked user guide. Working
-disciplines are available after setup, but are never selected merely because
-this gateway loaded.
-
-## Route the request
-
-| Need | Read first |
-| --- | --- |
-| install/setup, PostgreSQL, auth, server, health, sync, views, client assets | `references/aops-cli-core/SKILL.md` |
-| read-only local dashboard, sprint/task/board views, focused digest | `references/view/SKILL.md` |
-| durable memory, reusable prompts/skills/resources/artifacts, experience | `references/agentspace/SKILL.md` |
-| boards, tasks, sprints/plans, issues, feedback, reviews, handoffs | `references/projectman/SKILL.md` |
-| versioned documents, sections, links, search, answer, mirrors | `references/docman/SKILL.md` |
-| encrypted coordination rooms, foreground listen, messages, membership | `references/chatv3/SKILL.md` |
-| structured multi-agent decision/consensus topics | `references/discuss/SKILL.md` |
-| counters, countries, event store, rate limits | `references/sys/SKILL.md` |
-| choose or explain a working method | `references/working-disciplines/SKILL.md` |
-| run the full optional collaborative session playbook | `references/collaborative-work/SKILL.md` |
-| another installed/custom domain | `aops agent tools --domain <domain> --summary --json` |
-
-`aops chat` is the canonical ChatV3 surface; `aops chatv3` is a compatibility
-alias for the same command tree. Fileman, Tasker/Runner, and the
-interactive loop are not part of the default Community capability closure;
-discover them only if the connected server actually advertises them.
-
-## Authority order
-
-1. Packaged references explain ownership, safety, and common examples.
-2. Current nested `aops ... --help` owns sugar command flags.
-3. `aops agent schema --tool <domain.operation> --summary --json` owns raw invoke payload fields.
-4. `aops agent invoke --tool <domain.operation> --input '@payload.json' --preview --json` is the generic fallback.
-
-Use `aops agent tools --summary --json` when the installed server differs from
-the packaged core. Do not load every reference or whole guide into context, and
-do not infer server topology or capabilities from a repository checkout.

package/agent-assets-release/agent-assets/core/bc42dd7792dbe66040e99a7ef3d80b3bc788c72b369b5a065cf936aef29f53fb/files/references/agentspace/SKILL.md

@@ -1,72 +0,0 @@
----
-name: aops-cli-agentspace
-description: Use for durable memory, synopsis, reusable prompts/skills/resources/artifacts, experience, agent profiles, and other Agentspace-owned context through the AOPS CLI.
----
-
-# Agentspace
-
-Agentspace owns durable agent/operator context and reusable hosted assets.
-Project execution belongs to Projectman; versioned documents belong to Docman.
-ChatV3 coordination and structured decisions have their own references.
-
-Read only the needed section of `../../user-guides/agentspace.md`. Exact flags
-come from live nested help.
-
-## Durable memory
-
-```bash
-aops mem --help
-aops mem list --json
-aops mem search --q "migration decision" --limit 10 --json
-aops mem write --mode resume --subject project --content "<bounded handoff>" --apply
-aops mem list --durability sticky --json
-aops mem synopsis --subject project --json
-```
-
-Use memory for decisions, constraints, handoffs, and facts that must survive a
-session. Keep content concise and scoped. Do not use memory as a duplicate task
-tracker or paste secrets, logs, or large documents into it.
-
-## Reusable hosted assets
-
-```bash
-aops prompt list --json
-aops skill list --json
-aops resource list --json
-aops artifact list --json
-aops exp list --json
-```
-
-Create/update/version commands are guarded writes. Inspect their help first:
-
-```bash
-aops skill version create --help
-aops skill version publish --help
-aops prompt version create --help
-aops resource create --help
-```
-
-Hosted prompt/skill truth lives on the server. Local mirrors are read-only
-context. Artifact records are metadata/pointers, not a large binary store.
-
-
-## Raw discovery fallback
-
-```bash
-aops agent tools --domain agentspace --q memory --limit 20 --summary --json
-aops agent schema --tool agentspace.<operation> --summary --json
-aops agent invoke --tool agentspace.<operation> --input '@payload.json' --preview --json
-```
-
-Always inspect schema before raw writes. Use `--apply` only after scope and
-payload are clear; use an idempotency key for retryable mutations when
-supported. Read back the exact record after mutation.
-
-## Boundaries
-
-- Planning, tasks, sprints, issues, feedback, reviews: Projectman.
-- Document graphs, page content, publish/search/answer: Docman.
-- ChatV3 coordination/wake: `aops chat`.
-- Structured decision transcript: `aops discuss`.
-- `aops chatv3`: compatibility alias for `aops chat`.
-- Repo `.aops/**`: derived cache, never the canonical authoring source.

package/agent-assets-release/agent-assets/core/bc42dd7792dbe66040e99a7ef3d80b3bc788c72b369b5a065cf936aef29f53fb/files/references/aops-cli-core/SKILL.md

@@ -1,110 +0,0 @@
----
-name: aops-cli-core
-description: Use for AOPS installation, PostgreSQL setup, server lifecycle, health, authentication, sync, views, verified agent assets, and schema-first capability discovery.
----
-
-# AOPS CLI core
-
-Use the installed `aops` command as runtime truth. Read only the matching
-section in `../../user-guides/aops-cli.md`, `../../user-guides/aops-system.md`,
-or `../../user-guides/agent-assets.md` when this quick map is insufficient.
-
-## Install and diagnose
-
-```bash
-aops --version
-aops setup init
-aops setup ai
-aops setup guide
-aops server status --json
-aops server health --json
-aops cockpit
-```
-
-Parameterless `aops` opens the Rust TUI for operator-led first-run choices.
-`aops setup init` is its argument-driven engine for an existing PostgreSQL,
-AOPS-managed PostgreSQL container, detected local PostgreSQL, or a remote AOPS
-server. Local server paths plan/apply/verify migrations, start the npm server,
-leave starter/demo user data untouched, and install verified agent assets. The
-CLI never opens a menu or asks a question. Database secrets belong only in TUI
-private fields or private input files/environment; never paste them into chat
-or argv.
-
-For an unattended run, inspect readiness before apply:
-
-```bash
-aops setup init --path 1 --yes --json
-aops setup init --path 2 --yes --json
-aops setup init --path 3 --yes --json
-```
-
-Use the exact next action returned by readiness. Do not bypass TLS choices,
-asset ownership conflicts, or migration lineage errors.
-
-## Server and target lifecycle
-
-```bash
-aops server start --json
-aops server stop --json
-aops server restart --json
-aops server logs --tail 100
-aops host health --json
-aops host diagnostics --json
-aops target list --json
-aops target doctor <name> --json
-```
-
-Use `aops server <command> --help` before reset, rollback, or recovery. Never
-remove operator-owned PostgreSQL/Docker resources. Setup path 2 may manage only
-its exact label-verified AOPS container and volume.
-
-## Verified agent assets
-
-```bash
-aops assets status --verify quick --json
-aops assets install --target all --apply --json
-aops assets resolve --gateway aops --json
-aops assets discover --query "sprint planning" --limit 5 --json
-```
-
-`--target all` means every registered runtime, not only Codex and Claude.
-Install/repair fails closed on unknown user files. The core makes rich guides
-and disciplines available but never selects a working method.
-
-## Cache and read-only views
-
-```bash
-aops sync status --json
-aops sync pull --apply --json
-aops view dashboard --style agent
-aops view digest --task <task-id> --depth deep
-```
-
-Hosted records remain canonical. Repository `.aops/**` content is a read-only
-cache/presentation surface; never hand-edit it as hosted truth.
-
-## Capability discovery
-
-```bash
-aops agent tools --summary --json
-aops agent tools --domain <domain> --q <intent> --limit 10 --summary --json
-aops agent schema --tool <domain.operation> --summary --json
-aops agent invoke --tool <domain.operation> --input '@payload.json' --preview --json
-```
-
-Use sugar when nested `--help` exposes it. Direct invoke requires live schema.
-If a write is intended, preview when supported and add `--apply`; destructive
-operations may additionally require `--confirm`. Stop guessing after a 400 or
-validation error and inspect full schema/OpenAPI.
-
-## Guard contract
-
-- `--json`: stable automation output.
-- `--yes`: compatibility/fail-fast behavior; never implies mutation approval.
-- `--preview`: validate/plan without applying when supported.
-- `--apply`: execute a guarded write.
-- `--confirm`: acknowledge destructive scope.
-- `--idempotency-key`: make supported retries deterministic.
-
-Current nested `--help` wins over packaged examples. Live schema wins for raw
-payload fields and the live catalog wins for mounted-domain availability.

package/agent-assets-release/agent-assets/core/bc42dd7792dbe66040e99a7ef3d80b3bc788c72b369b5a065cf936aef29f53fb/files/references/chatv3/SKILL.md

@@ -1,59 +0,0 @@
----
-name: aops-cli-chat
-description: Use for ChatV3 encrypted channels, invitations, agent-owned local sessions, membership, presence, bindings, messages, cursors, and foreground listening through aops chat.
----
-
-# AOPS Chat (ChatV3)
-
-`aops chat` is the canonical encrypted ChatV3 channel/room surface for agent
-coordination and product-room work. `aops chatv3` is a compatibility alias for
-the same command tree; it is not a second messaging system.
-
-Read only the relevant section of `../../user-guides/chatv3.md`. Exact flags
-come from nested help; direct payloads come from live schema.
-
-## Common entry points
-
-```bash
-aops chat --help
-aops chat channel --help
-aops chat session --help
-aops chat member --help
-aops chat send --help
-aops chat read --help
-aops chat listen --help
-```
-
-Typical foreground coordination:
-
-```bash
-aops chat session list --json
-aops chat listen --session <id> --room general --after-seq <n> --timeout-sec 60 --json
-aops chat send --session <id> --room general "<message>" --json
-aops chat read --session <id> --room general --after-seq <n> --mark-delivered --mark-read --json
-```
-
-Keep foreground listening active while work remains. A listen timeout means
-only “no message in this bounded interval”; it does not end the task.
-
-Local sessions are isolated by detected agent owner (for example a Codex
-thread), or by `AOPS_CHATV3_SESSION_OWNER` / `--session-owner`. Session ids,
-member tokens, and room keys must never be copied between agent owners or
-pasted into chat, logs, source, or shell history. Legacy shared stores are
-claimed once and migrated into the first local owner that uses that session.
-
-`send --mark-read` and `send --mark-delivered` advance cursors only when the
-pre-send cursor is exactly caught up. If another message arrived first, the
-send succeeds but the cursor advance is skipped; read the gap explicitly.
-
-For a write not exposed by sugar, inspect the exact live schema first:
-
-```bash
-aops agent tools --domain chatv3 --summary --json
-aops agent schema --tool chatv3.<operation> --summary --json
-aops agent invoke --tool chatv3.<operation> --input '@payload.json' --preview --json
-```
-
-ChatV3 is coordination/wake truth, not the durable Projectman review record or
-the structured `discuss` transcript. Bind or summarize outcomes into the
-correct owner when durability matters.

package/agent-assets-release/agent-assets/core/bc42dd7792dbe66040e99a7ef3d80b3bc788c72b369b5a065cf936aef29f53fb/files/references/collaborative-work/SKILL.md

@@ -1,81 +0,0 @@
----
-name: aops-collaborative-work
-description: Use when the operator explicitly wants the full AOPS session playbook for solo work, async review, or ChatV3 room collaboration with Projectman-backed execution.
----
-
-# AOPS collaborative work
-
-Default to `solo`. Collaboration is an operator choice, not an automatic
-requirement. Select one mode at kickoff and use
-`../working-disciplines/SKILL.md` only when a working method must also be chosen.
-
-## Compact startup
-
-```bash
-aops sync status --json
-aops view dashboard --style agent
-aops start --task "<task>" --json --out ./aops-start.md
-aops pm board resume --board <slug> --json
-```
-
-Use `result.promptRef.path` or the output file; do not request inline/full output
-unless the prompt body is actually needed. Ask the operator only for fields
-explicitly marked operator-owned, especially agent identities and roles.
-
-## Mode 1: solo
-
-1. Read the smallest relevant guide/help surface.
-2. Create or identify the Projectman task/plan appropriate to the work size.
-3. Implement one bounded slice.
-4. Run focused validation and read back hosted mutations.
-5. Update status/handoff; keep the board open unless closeout was requested.
-
-Useful reads:
-
-```bash
-aops view digest --task <task-id> --depth shallow
-aops pm issue list --status open --json
-aops pm review-request list --status open --json
-```
-
-## Mode 2: solo plus async review
-
-After implementation and local validation, create a durable review request:
-
-```bash
-aops pm review-request create --help
-aops pm review-request list --status open --json
-aops pm review-request result --help
-```
-
-The reviewer records the result in Projectman. Material findings become
-Projectman issues or bounded fix slices; chat is only the optional wake channel.
-Do not claim review completion from a message alone.
-
-## Mode 3: ChatV3 room
-
-```bash
-aops chat join "<invite>" --handle <agent> --save-session --json
-aops chat binding add --session <id> --room general \
-  --binding-type projectman.kanban-task --ref-id <task-id> --json
-aops chat room brief --session <id> --room general --for <peer> --json
-aops chat listen --session <id> --room general \
-  --after-seq <last-seq> --timeout-sec 60 --json
-```
-
-Each participant owns a non-overlapping slice and reports completion with
-validation evidence. Use `aops discuss` only for a material consensus decision.
-`aops chatv3` remains an alias for this same ChatV3 surface.
-
-## During work
-
-```bash
-aops start --reminder --task "<task>" --area <area> --json
-aops mem checkpoint --help
-aops pm status audit --help
-```
-
-Prefer the detail ladder: this skill → one family reference → nested `--help` →
-live `agent schema`. Never preload every guide. Never invent another agent's
-stance, close operator-owned surfaces, or mark work done without requested
-validation and durable status.

package/agent-assets-release/agent-assets/core/bc42dd7792dbe66040e99a7ef3d80b3bc788c72b369b5a065cf936aef29f53fb/files/references/discuss/SKILL.md

@@ -1,66 +0,0 @@
----
-name: aops-cli-discuss
-description: Use for a structured server-canonical design decision or consensus topic with independent turns, explicit final stances, completeness checks, and deterministic conclusion.
----
-
-# AOPS Discuss
-
-`aops discuss` owns a durable decision transcript and conclusion. Use hosted
-`aops chat` (ChatV3) to wake/coordinate peers and Projectman to track review/execution.
-Do not start a discussion ritual for a small reversible implementation choice.
-
-The complete owner and troubleshooting model is in the Discuss sections of
-`../../user-guides/agentspace.md`.
-
-## Start and inspect
-
-```bash
-aops discuss --help
-aops discuss start --title "<decision>" --question "<question>" \
-  --participant <agent-a> --participant <agent-b> --apply --json
-aops discuss status --topic <topic> --json
-aops discuss get --topic <topic> --json
-```
-
-Give every participant enough neutral context to research independently. Role
-assignment belongs to the operator; an agent must not invent or swap identities.
-
-## Record turns
-
-```bash
-aops discuss turn --topic <topic> --agent <agent> \
-  --kind statement --from-file ./turn.md --apply --json
-aops discuss wait --topic <topic> --agent <agent> \
-  --timeout-sec 540 --interval-sec 5 --json
-```
-
-For material design decisions, record multiple substantive non-final turns so
-tradeoffs and objections are visible. Do not use chat messages as a substitute
-for the canonical topic transcript.
-
-## Finalize safely
-
-```bash
-aops discuss turn --topic <topic> --agent <agent> \
-  --kind final-stance --from-file ./final.md --apply --json
-aops discuss status --topic <topic> --json
-aops discuss conclude --topic <topic> --apply --json
-```
-
-Conclude only when every required participant has a `final-stance` and status
-reports no missing final stances. Outputs must contain real decisions and
-follow-ups, not `_TBD_` placeholders.
-
-There is no automatic bridge: explicitly reference the concluded topic from a
-Projectman task/review/issue or durable memory, then send a short ChatV3
-wake if another agent must act.
-
-For raw operations:
-
-```bash
-aops agent tools --domain agentspace --q discuss --limit 20 --summary --json
-aops agent schema --tool agentspace.<discuss-operation> --summary --json
-```
-
-Prefer slug/ID selectors returned by creation. Treat timeouts as state to
-report, not permission to fabricate another participant's stance.

package/agent-assets-release/agent-assets/core/bc42dd7792dbe66040e99a7ef3d80b3bc788c72b369b5a065cf936aef29f53fb/files/references/docman/SKILL.md

@@ -1,75 +0,0 @@
----
-name: aops-cli-docman
-description: Use for Docman document groups, documents, versions, sections/pages, search, answer, publish, mirrors, markdown import, and schema-first payloads through AOPS.
----
-
-# Docman
-
-Docman owns the versioned document graph and retrieval/publishing surfaces.
-Read the matching section of `../../user-guides/docman.md` for the complete
-model; use nested help for current flags.
-
-## Discover and read
-
-```bash
-aops doc --help
-aops doc group list --project-slug <slug> --json
-aops doc list --project-slug <slug> --json
-aops doc outline get --document-version-id <id> --titles-only --depth 0 --json
-aops doc search --document-version-id <id> --q "<query>" --json
-aops doc answer --help
-```
-
-Prefer IDs from list/get output. Search is retrieval, not necessarily the full
-page body. Use outline for structure and the supported page/version read
-surface for exact content.
-
-## Author and version
-
-```bash
-aops doc group create --help
-aops doc create --help
-aops doc version create --help
-aops doc section create --help
-aops doc page create --help
-aops doc page draft-save --help
-```
-
-Create graph nodes through CRUD commands when IDs are known. Use markdown
-import for intentional bulk import, not for a one-page edit. Every mutation is
-preview/apply guarded where supported; read back the current version after
-publishing.
-
-Compose or materialize the exact candidate before review and retain its
-version ids plus `contentHash`. Put the complete immutable evidence reference
-in both the Projectman review request and an approved review result. Saving a
-mutable draft changes its hash and requires a linked re-review; a page-version
-id alone is not approval evidence.
-
-## Search, answer, publish, and mirrors
-
-```bash
-aops doc scope search --project-slug <slug> --q "<query>" --json
-aops doc publish --help
-aops doc mirror pull --project-slug <slug> --group-uid <group> --out-dir <dir> --apply --json
-```
-
-Mirrors are read-only projections. Change the hosted document, publish/set the
-current version as required, then refresh the mirror. `aops sync pull` does not
-replace Docman mirror pull.
-
-## Raw fallback
-
-```bash
-aops agent tools --domain docman --q document --limit 20 --summary --json
-aops agent schema --tool docman.<operation> --summary --json
-aops agent invoke --tool docman.<operation> --input '@payload.json' --preview --json
-```
-
-If sugar reports a validation error, stop varying flags blindly. Compare the
-live operation schema/OpenAPI with the wrapper payload, then use raw invoke only
-with an exact reviewed payload.
-
-Docman owns document semantics; external storage owns binary file bytes and
-recovery, Projectman owns execution status, and Agentspace owns durable agent
-memory/reusable assets.

package/agent-assets-release/agent-assets/core/bc42dd7792dbe66040e99a7ef3d80b3bc788c72b369b5a065cf936aef29f53fb/files/references/projectman/SKILL.md

@@ -1,92 +0,0 @@
----
-name: aops-cli-projectman
-description: Use for Projectman boards, tasks, sprints and implementation plans, microtasks, issues, feedback, reviews, handoffs, and server-canonical planning through AOPS.
----
-
-# Projectman
-
-Projectman is the execution and review source of truth. It supports board-only,
-sprint-only, combined, and small-task flows; do not force a ceremony the
-operator did not choose. Read the relevant heading in
-`../../user-guides/projectman.md` for deeper examples.
-
-## Inspect the live surface
-
-```bash
-aops pm --help
-aops pm board --help
-aops pm ktask --help
-aops pm sprint --help
-aops pm utask --help
-aops pm issue --help
-aops pm feedback --help
-aops pm review-request --help
-aops pm handoff --help
-```
-
-## Common planning flow
-
-```bash
-aops pm board list --json
-aops pm board create --name "Delivery" --apply --json
-aops pm ktask create --board <board> --column Todo --title "<task>" --apply --json
-aops pm sprint create --task <task-id> --name "Sprint 1" --goal "<outcome>" --apply --json
-aops pm utask create --sprint <sprint-id> --title "<verifiable step>" --apply --json
-```
-
-Use clear outcome text: what is needed, why it matters, and how completion will
-be proven. IDs returned by writes should be reused; do not resolve ambiguous
-titles repeatedly.
-
-## Read and resume
-
-```bash
-aops pm board get --slug <board-slug> --json
-aops pm ktask get --id <task-id> --json
-aops pm sprint get --id <sprint-id> --json
-aops view digest --task <task-id> --depth deep
-aops pm handoff resume --subject ktask --id <task-id> --json
-```
-
-Local `view` output is a read-only presentation cache. Writes always go through
-hosted Projectman commands.
-
-## Issues, feedback, and review
-
-```bash
-aops pm issue create --help
-aops pm feedback create --help
-aops pm review-request create --help
-aops pm review-request result --help
-aops pm handoff write --help
-```
-
-Use an issue for a material blocker/defect, feedback for observations or
-suggestions, and review-request/result for an auditable review gate. A chat
-message may wake a reviewer but is not the review record.
-
-For mutable Docman drafts, bind the review request to the exact composed
-evidence reference containing the page/document version id and its
-`contentHash=sha256:<digest>`. An approved result must repeat that complete
-reference exactly. A later draft edit changes the hash, so the earlier approval
-does not cover the new bytes; open a linked re-review.
-
-## Status discipline
-
-1. Inspect the record before changing status.
-2. Use the exact nested help and stable IDs.
-3. Apply one bounded mutation and read it back.
-4. Mark done only after requested validation actually passes.
-5. Ordinary session stop writes a handoff/status; board/room closeout remains
-   an explicit operator decision.
-
-## Raw fallback
-
-```bash
-aops agent tools --domain projectman --q review --limit 20 --summary --json
-aops agent schema --tool projectman.<operation> --summary --json
-aops agent invoke --tool projectman.<operation> --input '@payload.json' --preview --json
-```
-
-Do not guess raw fields. If sugar returns validation errors, compare the sugar
-payload with live schema before using a direct invoke workaround.

package/agent-assets-release/agent-assets/core/bc42dd7792dbe66040e99a7ef3d80b3bc788c72b369b5a065cf936aef29f53fb/files/references/sys/SKILL.md

@@ -1,36 +0,0 @@
----
-name: aops-cli-sys
-description: Use for live Sys capabilities including counters, shared country lookup, event-store operations, and rate-limit state through schema-first AOPS agent tools.
----
-
-# Sys
-
-Sys is a mounted Community domain but has no dedicated sugar family. Start
-with compact live discovery and use raw invoke only after reading its schema.
-Detailed examples are in `../../user-guides/sys.md`.
-
-```bash
-aops agent tools --domain sys --summary --json
-aops agent tools --domain sys --q country --limit 10 --examples --summary --json
-aops agent schema --tool sys.country.resolve-iso2 --summary --json
-```
-
-The current capability families are:
-
-- `sys.counter.*` — tenant-scoped formatted counters;
-- `sys.country.*` — shared ISO country lookup/search;
-- `sys.event-store.*` — append/read/cleanup domain events;
-- `sys.rate-limiter.*` — check, record, reset, inspect, and cleanup limits.
-
-Reads can be invoked without `--apply`. Database mutations require `--apply`;
-cleanup/reset operations should be previewed and treated as destructive even
-when the live contract does not require a separate `--confirm` flag.
-
-```bash
-aops agent invoke --tool sys.country.resolve-iso2 --input '{"body":{"iso2Code":"TR"}}' --json
-aops agent invoke --tool sys.counter.preview-next --input '{"body":{"counterKey":"inventory.item.code","prefix":"ITM","width":5}}' --json
-aops agent invoke --tool sys.counter.next --input '@counter-next.json' --preview --json
-```
-
-Examples are illustrative. The connected server's `agent schema` and tool
-detail are authoritative for required fields, tenant context, and guard flags.