/aria-probe

name: aria-probe
description: >
  Run a 4-step validation probe for the aria-cowork spec. Tests whether this Cowork plugin can verify cwd, write to the user-attached knowledge folder, read a file pre-placed by aria-knowledge in Code, and capture or fall back gracefully on the transcript surface. Outputs structured results both to the conversation and to a probe-results file. Use when validating the aria-cowork spec before Phase 1 build. Triggers: "/aria-probe", "run aria probe", "validate aria-cowork", "test cowork filesystem".

aria-probe

You are running a **validation probe** for the aria-cowork plugin spec. Your goal is to determine whether this Cowork environment supports the bidirectional knowledge folder pattern that aria-cowork's design depends on.

You will perform **4 probes** in sequence. For each probe, output a clear PASS/FAIL/INCONCLUSIVE verdict to the conversation AND append a structured result line to `probe-results-<timestamp>.md` at the cwd root.

Setup

Before the first probe, ensure both expected folders are attached. Ask the user:

> This probe needs **two folder attaches** for full coverage: > 1. **Required:** your knowledge folder (e.g. `~/Projects/knowledge/`) — used by probes 11, 2, 3, 7 > 2. **Optional but recommended:** `~/.claude/` — used by probe 12 (tests whether Cowork can read the legacy aria-knowledge.local.md config) > > If both are attached via Cowork's folder picker, confirm the absolute paths. If only the knowledge folder is attached, probes 11/2/3/7 will run but probe 12 will be skipped. If neither is attached, attach at least the knowledge folder via Cowork's folder picker, then re-run /aria-probe.

If the user confirms at least the knowledge folder is attached, proceed. Probe 12 has its own gate that handles the absent-`~/.claude/` case gracefully.

Once attached, create the results file at the cwd root with this header:

# aria-cowork validation probe results

**Date:** <ISO 8601 timestamp>
**Cowork version:** <ask user; if not known, write "unknown">
**Attached folder:** <absolute path the user confirmed>

---

## Results

---

Probe 11 — Folder attachment / cwd resolution

**Question:** Does cwd resolve to the user-attached folder?

**Action:** 1. Output the current working directory. 2. Compare to the path the user confirmed.

**Verdict:**

• **PASS** — cwd matches the user-confirmed attached folder.
• **FAIL** — cwd is different (e.g. resolves to a sandbox path or empty).
• **INCONCLUSIVE** — cwd cannot be determined.

**Append to results file:**

### Probe 11 — Folder attachment
- cwd resolved to: `<actual cwd>`
- user-confirmed attach: `<user path>`
- **Verdict:** PASS | FAIL | INCONCLUSIVE

If FAIL, stop here and report. The remaining probes depend on this one.

---

Probe 2 — Filesystem write to attached folder

**Question:** Can this plugin write a new file under the user-attached folder?

**Action:** 1. Generate a timestamp: `YYYY-MM-DDTHH-MM-SS`. 2. Create a directory `probe-test/` at cwd root if it doesn't exist. 3. Write the following file at `probe-test/cowork-write-test-<timestamp>.md`:

---
written_by: aria-probe (running in Cowork)
written_at: <timestamp>
purpose: validation probe 2 — confirm Cowork plugin can write user folder
---

This file was written by aria-probe in Cowork to verify probe 2 of the aria-cowork validation gate.

If aria-knowledge (in Code) can read this file, probes 2 and 3 of the validation gate pass.

4. Verify the file exists by reading it back.

**Verdict:**

• **PASS** — file was created and read-back content matches what was written.
• **FAIL** — write was rejected, or read-back failed, or content didn't match.
• **INCONCLUSIVE** — error during the operation that doesn't clearly indicate write capability.

**Append to results file:**

### Probe 2 — Filesystem write
- write target: `probe-test/cowork-write-test-<timestamp>.md`
- write succeeded: yes | no
- read-back matches: yes | no
- error (if any): `<error text>`
- **Verdict:** PASS | FAIL | INCONCLUSIVE

---

Probe 3 — Cross-surface read

**Question:** Can this plugin read a file that aria-knowledge (in Code) wrote earlier?

**Setup pre-condition:** A fixture file should already exist at `probe-test/code-write-test.md`. (If not, the user is instructed via README.md to place it first.)

**Action:** 1. Check whether `probe-test/code-write-test.md` exists. 2. If it exists, read it. 3. Validate that the content has the expected fixture marker (the fixture file contains the literal string `FIXTURE_MARKER:ARIA_PROBE_3_CODE_SIDE_WROTE_THIS`).

**Verdict:**

• **PASS** — file was found, read, and contained the expected marker.
• **FAIL** — file was not found, or didn't contain the expected marker.
• **INCONCLUSIVE** — read attempt errored in a way that doesn't indicate file absence (e.g. permission error mid-read).

**Append to results file:**

### Probe 3 — Cross-surface read
- target: `probe-test/code-write-test.md`
- file found: yes | no
- expected marker present: yes | no
- file contents (first 200 chars): `<excerpt>`
- error (if any): `<error text>`
- **Verdict:** PASS | FAIL | INCONCLUSIVE

---

Probe 7 — Transcript capture surface

**Question:** Can this plugin capture the current conversation transcript, or must it fall back to user-paste?

**Action:** 1. Attempt to read the conversation history. Cowork may expose this via:

• A built-in tool (try invoking it if you know one)
• A file in the Cowork app data directory (try common paths if any are documented)
• No mechanism (then fall back to user-paste)

2. If automated capture works, write a snippet of the conversation to `probe-test/transcript-capture-<timestamp>.md`. 3. If no automated capture, prompt the user: "Cowork does not appear to expose a transcript API. Paste the relevant part of this conversation here, or skip this probe."

**Verdict:**

• **PASS (auto)** — transcript captured automatic