opencli-adapter-author

Writing an OpenCLI adapter involves an end-to-end workflow from reconnaissance through field decoding, coding, and verification. You use scaffold adaptation patterns and memory-driven validation to ensure the new site adapter is robust and reusable.

The best way to extend an existing OpenCLI adapter is by applying scaffold adaptation patterns for rapid iteration, followed by endpoint validation and verification fixtures. This ensures the new command integrates correctly without breaking existing site functionality.

Yes, the OpenCLI adapter workflow supports ad-hoc browser-driven debugging via opencli browser. This allows you to interactively inspect sites during reconnaissance and decode complex fields while developing the adapter.

This end-to-end adapter authoring process replaces older workflows like opencli-oneshot and opencli-explorer by providing comprehensive guidance from discovery to verification. It adds memory-driven validation and repository conventions to deliver more robust, reusable adapters.

You need verification fixtures during the final stage of adapter development to validate endpoint behavior and ensure field decoding works correctly. They are enforced by the workflow to maintain repository conventions and guarantee the adapter's output is accurate.