Skip to content

Latest commit

 

History

History
34 lines (26 loc) · 1.88 KB

CONTRACT_COMPLIANCE.md

File metadata and controls

34 lines (26 loc) · 1.88 KB

Browser CLI Contract Compliance

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.

Compliance Map

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

Current Compliance Work

  • Text output is normalized by default for lower-token machine output.
  • --clean=false and @clean=false preserve the previous raw-ish text behavior for deterministic regression checks.
  • Sensitive action values are redacted in the AI action log for fill and force-fill.
  • snapshot.globals is config-driven; public default is empty.
  • v3 output follows the Trinity Tool Contract v1.0 output envelope.
  • --input reads a Trinity Tool Contract v1.0 input envelope and maps supported browser.* actions to browser-cli commands.

Thai Note

ไฟล์นี้เป็นตัวตามสถานะว่า browser-cli เข้าใกล้ Trinity Tool Contract v1.0 แค่ไหน ตอนนี้ --response-schema=v3 และ --input envelope mode ทำแล้ว แต่ write-boundary enforcement ยังเป็น partial