FAT: session-013 — orient standalone, updater, install verification

[arcaven]

Context

Session-013 shipped three changes:

1. Orient standalone — kos orient now works from repos outside aae-orc
2. Updater improvements — alpha channel, version-specific kos update [VERSION], channel filtering
3. Distribution — brew install ArcavenAE/tap/kos confirmed working on macOS

This issue tracks functional acceptance testing across platforms.

Install

macOS (Homebrew)

brew install ArcavenAE/tap/kos
kos version

Expected: version, commit, build time, channel (alpha).

Note on capitalization: ArcavenAE uses mixed case deliberately — makes it easier to read for people with certain reading disorders or who might map -ae to Latin plurals.

Linux (direct binary)

# Download from latest release
curl -sL "https://github.com/ArcavenAE/kos/releases/latest/download/kos-linux-arm64" -o kos
chmod +x kos
sudo mv kos /usr/local/bin/
kos version

Functional Acceptance Tests

FAT-1: Standalone discovery

cd ~/work/ftc   # or any repo with _kos/kos.yaml, not under aae-orc
kos orient

• Header shows (standalone)
• Does NOT show "(no items found mentioning...)" or suggest aae-orc targets
• Empty graph shows hint: "add nodes to _kos/nodes/"

FAT-2: Charter items shown unfiltered (standalone)

cd <standalone-repo-with-populated-charter>
kos orient

• ALL Bedrock/Frontier/Graveyard items listed, not filtered by target name

FAT-3: Nodes by confidence tier (standalone)

cd <standalone-repo-with-nodes>
kos orient

• Bedrock, frontier, graveyard nodes listed by tier with id and title

FAT-4: Findings, probes, ideas displayed (standalone)

cd <standalone-repo-with-kos-content>
kos orient

• Findings from _kos/findings/
• Probes from _kos/probes/
• Ideas from _kos/ideas/

FAT-5: Orchestrator subrepo unchanged (no regression)

cd ~/work/aae-orc/switchboard
kos orient

• Charter items filtered by "switchboard" mentions
• Same output as before session-013

FAT-6: kos repo itself unchanged (no regression)

cd ~/work/aae-orc/kos
kos orient kos

• Same output as before session-013

FAT-7: JSONL includes standalone fields

cd <standalone-repo>
kos orient --json

• First line: {"standalone":true,"target":"...","type":"orient_meta"}

FAT-8: kos doctor (standalone)

cd <standalone-repo>
kos doctor

• Discovers the standalone graph
• Reports node count, warnings, errors

FAT-9: kos update

kos update

• Shows current version tag
• Shows latest available (or "already up to date")
• Homebrew-installed binary says "installed via Homebrew. Run: brew upgrade ArcavenAE/tap/kos"

FAT-10: kos update VERSION (version-specific)

kos update alpha-20260405    # partial match

• Finds matching release by partial prefix
• Shows current vs target before downloading
• Homebrew installs redirect to brew upgrade

FAT-11: kos version

kos version

• Shows version, commit, build time, channel
• Channel is alpha

Platform matrix

Test	macOS arm64 (brew)	Linux arm64 (direct)	Linux amd64 (direct)
Install	✅ verified
FAT-1
FAT-2
FAT-3
FAT-4
FAT-5
FAT-6
FAT-7
FAT-8
FAT-9
FAT-10
FAT-11

Commits

• 3789bb3 feat(orient): standalone repo support
• fef750f harvest: session-013 — lifecycle composition extraction, 27 nodes
• a654f9e harvest: session-013 continued — intent persistence, substrate convergence
• 6a2229d feat(kos): alpha channel, version-specific updates, channel filtering

[arcaven]

macOS arm64 (Homebrew) — FAT Results

Tested on: macOS arm64 (Apple Silicon), brew install ArcavenAE/tap/kos
Binary: alpha-20260405-183037-fef750f
Tester: Claude (ftc repo)

Results

Test	Result	Notes
Install	✅	brew install ArcavenAE/tap/kos succeeded cleanly
FAT-1: Standalone discovery	✅	Header shows (standalone), hint about adding nodes shown, no aae-orc references
FAT-2: Charter items unfiltered	⏭️ SKIP	ftc charter is empty (bootstrapped template), no items to verify filtering
FAT-3: Nodes by confidence tier	⏭️ SKIP	No nodes in ftc yet
FAT-4: Findings, probes, ideas	⏭️ SKIP	Directories exist but are empty
FAT-5: Orchestrator subrepo	⏭️ SKIP	Out of scope for this tester (no aae-orc access)
FAT-6: kos repo itself	⏭️ SKIP	Out of scope for this tester
FAT-7: JSONL standalone fields	✅	{"standalone":true,"target":"ftc","type":"orient_meta"} — correct
FAT-8: kos doctor (standalone)	✅	Discovers graph, reports structure valid, warns 0 nodes, charter found
FAT-9: kos update	✅	Detects Homebrew install, redirects to brew upgrade ArcavenAE/tap/kos
FAT-10: kos update VERSION	⚠️ PARTIAL	Homebrew detection fires correctly, but partial-match logic is unreachable via brew path
FAT-11: kos version	✅	All fields present, channel=alpha

Additional commands tested

Command	Result	Notes
kos graphs	✅	Shows ftc graph, scope=repo, 0 nodes
kos validate --merged	✅	0 nodes, 0 passed, 0 warnings, 0 failed
kos --help	✅	All subcommands listed

Bugs filed

• Build-time timestamp in version tag differs from embedded build_time #2 — Build-time timestamp inconsistency: tag, display header, and embedded build_time show three different timestamps

Summary

6 PASS, 5 SKIP (out of scope or no test data), 1 PARTIAL. No failures. The standalone discovery, doctor, JSONL output, and updater Homebrew detection all work correctly. FAT-2/3/4 need a populated standalone repo to verify — ftc was just bootstrapped.

[arcavenai]

Linux arm64 (direct binary) — FAT Results

Tested on: Linux aarch64 (Raspberry Pi 5, Debian 6.12.75+rpt-rpi-v8), direct binary install
Binary: alpha-20260405-183037-fef750f from GitHub Releases → ~/.local/bin/kos
Tester: Claude (kos repo + ftc standalone repo)

Results

Test	Result	Notes
Install	✅	gh release download kos-linux-arm64 → ~/.local/bin/kos, 8.2MB, runs cleanly
FAT-1: Standalone discovery	✅	Header shows (standalone), hint shown, no aae-orc references
FAT-2: Charter items unfiltered	⏭️ SKIP	ftc charter has no items (bootstrapped template)
FAT-3: Nodes by confidence tier	⏭️ SKIP	No nodes in ftc
FAT-4: Findings, probes, ideas	⏭️ SKIP	Directories exist but empty
FAT-5: Orchestrator subrepo	✅	cd switchboard && kos orient — charter items correctly filtered by "switchboard"
FAT-6: kos repo itself	✅	kos orient kos — shows charter items, RD briefs, findings
FAT-7: JSONL standalone fields	✅	{"standalone":true,"target":"ftc","type":"orient_meta"}
FAT-8: kos doctor (standalone)	✅	Discovers graph, reports missing dirs, warns 0 nodes. --fix creates dirs correctly
FAT-9: kos update	✅	Shows "Already up to date" when on latest
FAT-10: kos update VERSION	✅	Partial match works. Tested full cycle: downgrade to alpha-20260405-171432-6a2229d, verify version changed, upgrade back to latest — both directions work cleanly
FAT-11: kos version	✅	All fields: version=0.1.0, commit=fef750f, build_time, channel=alpha

Additional commands tested

Command	Result	Notes
kos graphs	✅	Lists all 7 graphs with correct node counts
kos validate --merged	✅	36 nodes: 33 passed, 2 warnings, 1 failed (data issue, not binary — see below)
kos doctor (kos repo)	✅	52 nodes, 0 errors, 10 orphan warnings. --fix created missing nodes/placeholder dir
kos doctor --fix (ftc)	✅	Created all missing dirs, errors dropped from 7 to 0
kos --help	✅	All 11 subcommands listed

Data issue (not a binary bug)

_kos/nodes/bedrock/elem-tmux-cmc.yaml in the aae-orc orchestrator graph has two validation failures:

1. Filename elem-tmux-cmc.yaml doesn't match id bedrock/elem-tmux-cmc.yaml
2. Lives in bedrock/ directory but declares frontier confidence
3. Uses edge type supports which isn't in the schema (expected: derives, implements, contradicts, supersedes)

This is a graph data issue in aae-orc, not a kos binary issue.

Summary

9 PASS, 3 SKIP (no test data), 0 FAIL. The self-updater's download-and-replace cycle works perfectly on Linux arm64 — tested downgrade and upgrade in both directions. All subcommands function correctly. No binary issues found.

[arcavenai]

Linux arm64 (direct binary) — FAT Results (second pass)

Tested on: Linux aarch64 (Raspberry Pi 5, Debian 13 trixie, 6.12.75+rpt-rpi-v8), direct binary install
Binary: alpha-20260405-183037-fef750f at ~/.local/bin/kos
Tester: Claude (ftc standalone + aae-orc/switchboard orchestrator subrepo)

Results

Test	Result	Notes
Install	✅	Already installed at ~/.local/bin/kos, runs cleanly
FAT-1: Standalone discovery	✅	Header shows (standalone), no "mentioning..." filter language, hint shown: "add nodes to _kos/nodes/"
FAT-2: Charter items unfiltered	⏭️ SKIP	ftc charter is a template with no items
FAT-3: Nodes by confidence tier	⏭️ SKIP	No nodes in ftc
FAT-4: Findings, probes, ideas	⏭️ SKIP	All content directories exist but are empty
FAT-5: Orchestrator subrepo	✅	cd switchboard && kos orient — charter items filtered by "switchboard" mentions, RD briefs shown correctly
FAT-6: kos repo itself	✅	kos orient kos — charter items, RD briefs, and findings all shown correctly with kos-related items
FAT-7: JSONL standalone fields	✅	First line: {"standalone":true,"target":"ftc","type":"orient_meta"}
FAT-8: kos doctor (standalone)	✅	Structure valid, kos.yaml valid (graph_id: ftc, scope: repo), schema 0.3, charter found. 0 nodes (warning). --fix is a no-op (all dirs already present)
FAT-9: kos update	✅	"Already up to date: alpha-20260405-183037-fef750f"
FAT-10: kos update VERSION	✅	kos update alpha-20260405 — partial match resolves correctly, reports "Already up to date" since we're on that version
FAT-11: kos version	✅	version=0.1.0, commit=fef750f, build_time present, channel=alpha

Additional commands tested

Command	Result	Notes
kos graphs	✅	Shows ftc graph, scope=repo, 0 nodes
kos validate --merged	✅	0 nodes, 0 passed, 0 warnings, 0 failed
kos doctor (ftc)	✅	0 nodes, 0 errors, 1 warning (no nodes)
kos doctor --fix (ftc)	✅	No fixes needed — all dirs already present
kos --help	✅	All 11 subcommands listed (orient, validate, graph, graphs, init, drift, bridge, doctor, update, version, help)

Bugs found

None. All commands behaved as expected. Bug #2 (timestamp inconsistency) was already filed by the previous tester.

Summary

8 PASS, 3 SKIP (no test data in ftc), 0 FAIL. This is a confirmatory second pass on Linux arm64 — results align with the previous Linux arm64 run. Standalone orient, doctor, JSONL output, updater, and all additional commands work correctly. Updater round-trip (downgrade/upgrade) was not tested this pass.

🤖 Generated with Claude Code

[arcaven]

macOS arm64 (Homebrew) — FAT Results from aae-orc orchestrator

Tested on: macOS arm64 (Apple Silicon), brew install ArcavenAE/tap/kos
Binary: alpha-20260405-183029-fef750f
Tester: Claude (aae-orc orchestrator context)

Results

Test	Result	Notes
Install	✅	/opt/homebrew/bin/kos, version confirmed
FAT-1: Standalone discovery	✅	ftc repo: header shows (standalone), hint about adding nodes, no aae-orc references
FAT-2: Charter items unfiltered	⏭️ SKIP	No populated standalone repo available (ftc is empty, kos/aclaude/etc are subrepos)
FAT-3: Nodes by confidence tier	⏭️ SKIP	Same — need populated standalone repo. However: see #3 — nodes don't appear in orient for orchestrator/subrepo mode either
FAT-4: Findings, probes, ideas	⏭️ SKIP	Same — see #3
FAT-5: Orchestrator subrepo	✅	cd switchboard && kos orient — charter items correctly filtered by "switchboard" mentions (10 items: B1, B2, B9, B11, F1, F2, F3, F7, F10, F17)
FAT-6: kos repo itself	✅	cd kos && kos orient kos — shows 17 charter items + 2 RD briefs + 1 RD finding. All kos-mentioning content present.
FAT-7: JSONL standalone fields	✅	ftc: {"standalone":true,"target":"ftc","type":"orient_meta"} as first line. Subrepo mode: no orient_meta (by design).
FAT-8: kos doctor	✅	Tested from 3 locations: orchestrator (35 nodes, 4 orphan warnings), kos subrepo (56 nodes, 10 orphan warnings), switchboard (0 nodes, 1 warning), ftc standalone (0 nodes, 1 warning). All discover graphs correctly.
FAT-9: kos update	✅	Detects Homebrew install, prints: kos was installed via Homebrew. Run: brew upgrade ArcavenAE/tap/kos
FAT-10: kos update VERSION	⚠️ PARTIAL	Homebrew detection fires immediately, partial-match logic unreachable via brew path (same as ftc tester)
FAT-11: kos version	✅	All fields: version 0.1.0, commit fef750f, build time, channel=alpha. Timestamp discrepancy noted in #2.

Additional commands tested

Command	Result	Notes
kos orient (orchestrator root)	✅	Shows aae-orc-filtered charter items + RD content
kos orient --json (orchestrator)	⚠️	Works but only emits charter/rd_brief/rd_finding types — no node/finding/probe/idea. See #3.
kos validate --merged	⚠️	36 nodes: 33 pass, 2 warnings, 1 failure. See #4 for details.
kos validate (from kos/)	✅	56 nodes: 52 pass, 4 warnings, 0 failures
kos graphs	✅	Discovers all 7 graphs: aae-orc(36), kos(56), aclaude(8), marvel(8), spectacle(5), threedoors(65), switchboard(0)
kos doctor (orchestrator)	✅	Validates structure, includes (7 subrepos), 35 parseable nodes, charter found
kos --help	✅	All 12 subcommands listed

Bugs filed

• Build-time timestamp in version tag differs from embedded build_time #2 — Build-time timestamp inconsistency (3 different timestamps) — filed by ftc tester
• data: elem-tmux-cmc.yaml in aae-orc graph has validation failures #3 — orient ignores _kos/ graph content in orchestrator/subrepo mode (nodes, findings, probes, ideas invisible)
• orient ignores _kos/ graph content (nodes, findings, probes, ideas) in orchestrator/subrepo mode #4 — validate: edge types supports, instantiates, partially_resolves not in schema + parse error cascade

Summary

8 PASS, 3 SKIP, 1 PARTIAL. No outright failures. Core orient, doctor, update, and version functionality works correctly from the orchestrator context.

Key gap: FAT-2/3/4 (node/finding/probe/idea display) can't be verified because (a) no populated standalone repo exists for standalone testing and (b) orient doesn't show this content in orchestrator/subrepo mode (#3). This is the most significant finding — the richest kos graphs (kos: 56 nodes, ThreeDoors: 65 nodes, orchestrator: 35 nodes) are invisible to the orient command.

Updated platform matrix

Test	macOS arm64 (brew) — ftc	macOS arm64 (brew) — aae-orc
Install	✅	✅
FAT-1	✅	✅
FAT-2	⏭️ (empty repo)	⏭️ (no standalone)
FAT-3	⏭️ (empty repo)	⏭️ (no standalone)
FAT-4	⏭️ (empty repo)	⏭️ (no standalone)
FAT-5	⏭️ (no aae-orc)	✅
FAT-6	⏭️ (no aae-orc)	✅
FAT-7	✅	✅
FAT-8	✅	✅
FAT-9	✅	✅
FAT-10	⚠️ PARTIAL	⚠️ PARTIAL
FAT-11	✅	✅

[arcaven]

New features in fb4c84f need FAT testing

Session-014 added process subcommands and orient _kos/ content. These need verification on installed binary (alpha build from fb4c84f), especially on Linux arm64.

FAT-12: Process subcommands (new)

# From any repo with _kos/
kos idea test-fat --title "FAT test idea"
kos question test-fat "FAT test question"
kos finding test-fat "FAT test finding"
kos probe test-fat "FAT test probe"

• Each creates a file in the correct _kos/ directory
• kos validate passes on the generated question node
• Finding auto-numbers correctly (check the NNN in the filename)
• Duplicate detection works (running the same command twice errors)
• Clean up: delete the test files after verification

FAT-13: Process subcommands respect workspace context (new)

# From orchestrator root
cd ~/work/aae-orc && kos idea test-orc
# → should create aae-orc/_kos/ideas/test-orc.md

# From subrepo
cd ~/work/aae-orc/switchboard && kos idea test-sw
# → should create switchboard/_kos/ideas/test-sw.md

# NOT kos/_kos/ in either case

• Orchestrator root writes to orchestrator's _kos/
• Subrepo writes to that subrepo's _kos/
• Clean up test files

FAT-14: Orient shows _kos/ content (fixes #4)

cd ~/work/aae-orc && kos orient

• Bedrock nodes section visible (was missing before)
• Open questions section visible
• Ideas section visible
• Graveyard nodes section visible
• kos orient --json emits node, idea, probe type lines (not just charter/rd_brief/rd_finding)

FAT-15: Validate cascade fix (fixes #5)

kos validate --merged

• Parse errors show PARSE ERROR line only — no phantom FAIL lines after them
• Summary shows parse error count separately: N nodes: X passed, Y warnings, Z failed, W parse errors
• aclaude graph: 6 parse errors, 0 failures (was 6 failures before)

Platform needs

• Linux arm64 (direct binary) — primary verification target
• macOS arm64 (Homebrew) — after brew upgrade

[arcaven]

Homebrew CI fix — update

The brew style / brew audit failure that was blocking all tap CI has been fixed.

Root cause: Formula/kos.rb desc was 84 characters; Homebrew enforces 80-character max. This caused every formula's CI to fail since the workflow runs style checks across all formulas.

Fix: Shortened desc to 65 characters in ArcavenAE/homebrew-tap@598c82f. CI now green — all 8 formulas pass audit + style.

Details: #6