Status: partial Trinity Tool Contract v1.0 implementation.
This document tracks how browser-cli maps to the public Trinity Tool Contract.
--response-schema=v3 and --input envelope mode are implemented, while
write-boundary enforcement remains partial.
| Contract Surface | browser-cli Implementation | Status |
|---|---|---|
| Input envelope | --input request.json or --input - |
Done |
| Output envelope | --response-schema=v3 |
Done |
| Exit codes | docs/COMMANDS.md / CLI process status |
Partial |
| Artifact declaration | v3 artifacts[] with file hashes when files exist |
Done |
| Error taxonomy | v3 errors[] mapped from lib/errors.js |
Done |
| Retry semantics | v3 retry object + @retry=<n> runtime option |
Done |
| Idempotency expectation | docs/IDEMPOTENCY.md + lib/idempotency.js |
Done |
| Audit log requirements | lib/action-logger.js NDJSON |
Partial |
| Security boundary | lib/policy.js tier system |
Partial |
- Text output is normalized by default for lower-token machine output.
--clean=falseand@clean=falsepreserve the previous raw-ish text behavior for deterministic regression checks.- Sensitive action values are redacted in the AI action log for
fillandforce-fill. snapshot.globalsis config-driven; public default is empty.- v3 output follows the Trinity Tool Contract v1.0 output envelope.
--inputreads a Trinity Tool Contract v1.0 input envelope and maps supportedbrowser.*actions to browser-cli commands.
ไฟล์นี้เป็นตัวตามสถานะว่า browser-cli เข้าใกล้ Trinity Tool Contract v1.0 แค่ไหน ตอนนี้ --response-schema=v3 และ --input envelope mode ทำแล้ว แต่ write-boundary enforcement ยังเป็น partial