Goal
Verify the complete flow for anolisa adapter install tokenless hermes and anolisa adapter remove tokenless hermes.
Current Status
adapter install has complete implementation (artifact download, manifest parsing, file extraction, state writing, CLI registration)
adapter remove has complete implementation (state query, file deletion, CLI deregistration, central log)
- However, the end-to-end path for tokenless + hermes has not been actually verified
Verification Needed
-
anolisa adapter install tokenless hermes
- Correctly resolves tokenless distribution index
- Downloads and extracts to
~/.local/share/anolisa/adapters/tokenless/hermes
- Registers with hermes framework successfully
- Writes
ObjectKind::Adapter record to installed.toml
-
anolisa adapter remove tokenless hermes
- Finds installed adapter record
- Deletes all ANOLISA-owned files
- Deregisters from hermes framework
- Cleans up state record
-
Both commands in --dry-run mode only print plans without executing
Acceptance Criteria
- On a clean Linux machine, install → remove → reinstall three cycles without errors
installed.toml state matches actual filesystem
- Central log records complete install/remove operation chain
- All code, comments, and documentation must be in English
Goal
Verify the complete flow for
anolisa adapter install tokenless hermesandanolisa adapter remove tokenless hermes.Current Status
adapter installhas complete implementation (artifact download, manifest parsing, file extraction, state writing, CLI registration)adapter removehas complete implementation (state query, file deletion, CLI deregistration, central log)Verification Needed
anolisa adapter install tokenless hermes~/.local/share/anolisa/adapters/tokenless/hermesObjectKind::Adapterrecord toinstalled.tomlanolisa adapter remove tokenless hermesBoth commands in
--dry-runmode only print plans without executingAcceptance Criteria
installed.tomlstate matches actual filesystem