@aopslabs/aops 0.3.9 → 0.3.10

package/assets/agent-assets/core/references/agentspace/SKILL.md

@@ -7,7 +7,7 @@ description: Use for durable memory, synopsis, reusable prompts/skills/resources
 
 Agentspace owns durable agent/operator context and reusable hosted assets.
 Project execution belongs to Projectman; versioned documents belong to Docman.
-Hosted coordination and structured decisions have their own references.
+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.
@@ -53,7 +53,7 @@ context. Artifact records are metadata/pointers, not a large binary store.
 
 For durable session intent and resume packs, load `../mission/SKILL.md` rather
 than the full Agentspace guide. For rooms/messages load
-`../hosted-chat/SKILL.md`; for structured consensus load
+`../chatv3/SKILL.md`; for structured consensus load
 `../discuss/SKILL.md`.
 
 ## Raw discovery fallback
@@ -72,7 +72,7 @@ supported. Read back the exact record after mutation.
 
 - Planning, tasks, sprints, issues, feedback, reviews: Projectman.
 - Document graphs, page content, publish/search/answer: Docman.
-- Hosted coordination/wake: `aops chat`.
+- ChatV3 coordination/wake: `aops chat`.
 - Structured decision transcript: `aops discuss`.
-- Encrypted product channel: `aops chatv3`.
+- `aops chatv3`: compatibility alias for `aops chat`.
 - Repo `.aops/**`: derived cache, never the canonical authoring source.

package/assets/agent-assets/core/references/chatv3/SKILL.md

@@ -1,49 +1,59 @@
 ---
-name: aops-cli-chatv3
-description: Use for encrypted ChatV3 product channels, invitations, local session context, membership, presence, epochs, and message operations through the AOPS CLI.
+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.
 ---
 
-# ChatV3
+# AOPS Chat (ChatV3)
 
-Use `aops chatv3` for product-facing encrypted channel/session operations.
-This is different from `aops chat`, which owns hosted agent coordination,
-wakes, inbox cursors, and room bindings.
+`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.
+come from nested help; direct payloads come from live schema.
 
 ## Common entry points
 
 ```bash
-aops chatv3 --help
-aops chatv3 channel --help
-aops chatv3 session --help
-aops chatv3 member --help
-aops chatv3 send --help
-aops chatv3 read --help
+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 discovery and read flow:
+Typical foreground coordination:
 
 ```bash
-aops chatv3 session list --json
-aops chatv3 channels --json
-aops agent tools --domain chatv3 --summary --json
-aops agent schema --tool chatv3.channel.list --summary --json
+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
 ```
 
-ChatV3 may keep invite, member-token, and room-key context in a private local
-session store. Never paste those values into chat, logs, source files, or raw
-shell history. Use supported secure-store, input-file, or environment
-mechanisms; the CLI does not collect secrets through terminal prompts.
+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.
 
-For a write not exposed by sugar, inspect the exact live schema before invoke:
+`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
 ```
 
-Do not use ChatV3 as the durable Projectman review record or the structured
-`discuss` transcript. Link or summarize outcomes into the correct owner when
-durability matters.
+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/assets/agent-assets/core/references/collaborative-work/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: aops-collaborative-work
-description: Use when the operator explicitly wants the full AOPS session playbook for solo work, async review, or hosted chat-room collaboration with Projectman-backed execution.
+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
@@ -53,23 +53,20 @@ 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: hosted chat room
+## Mode 3: ChatV3 room
 
 ```bash
-aops chat room create --slug <slug> --title "<purpose>" \
-  --created-by <lead> --member "<lead>:<role>" \
-  --member "<peer>:<role>" --apply --json
-aops chat binding add --room-id <id> \
-  --binding-type projectman.board --ref-id <board-id> \
-  --created-by <lead> --apply --json
-aops chat room brief --room-id <id> --for <peer>
-aops chat listen --for <agent> --room-id <id> --timeout-sec 570 --json
+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;
-use `aops chatv3` only when encrypted product-channel behavior is the actual
-task.
+validation evidence. Use `aops discuss` only for a material consensus decision.
+`aops chatv3` remains an alias for this same ChatV3 surface.
 
 ## During work
 

package/assets/agent-assets/core/references/discuss/SKILL.md

@@ -6,7 +6,7 @@ description: Use for a structured server-canonical design decision or consensus
 # AOPS Discuss
 
 `aops discuss` owns a durable decision transcript and conclusion. Use hosted
-`aops chat` to wake/coordinate peers and Projectman to track review/execution.
+`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
@@ -52,7 +52,7 @@ 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 hosted-chat
+Projectman task/review/issue or durable memory, then send a short ChatV3
 wake if another agent must act.
 
 For raw operations:

package/assets/agent-assets/core/references/docman/SKILL.md

@@ -40,6 +40,12 @@ 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

package/assets/agent-assets/core/references/projectman/SKILL.md

@@ -65,6 +65,12 @@ 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.

package/assets/agent-assets/core/references/working-disciplines/SKILL.md

@@ -50,7 +50,7 @@ aops mission create --objective "<objective>" \
 1. Put every implementation slice in Projectman before or at kickoff.
 2. Read live help/schema instead of guessing flags or payloads.
 3. Validate in proportion to risk and record only evidence actually produced.
-4. Use hosted chat for coordination/wake, Discuss for consensus, and
+4. Use ChatV3 (`aops chat`) for coordination/wake, Discuss for consensus, and
    Projectman review-request/result for review truth.
 5. Keep scope changes and blockers explicit; do not fabricate peer approval.
 6. Ordinary stop writes status/handoff and keeps mission/board/room open.