v0.1.4

Seamless agent workflows

• Keep the compact high-level Facebook/Messenger commands, with reliable profile-post extraction, verified post receipts, directly reusable refs, and scoped deletion.
• Continue past optional Messenger history-restore prompts through Facebook's own controls; explicitly unlock encrypted history when a PIN is required.
• Use fb page NAME for browser workflows without a dedicated command: bounded/filterable snapshots, trusted click/fill/key/scroll/upload, screenshot, targeted JavaScript, and raw page-session CDP. Named pages stay warm and separate from the command pool.
• Reject stale, renamed, covered, disabled and unsupported fill targets. Never replay uncertain mutations. A dispatch ok is not a save receipt: read the resulting state back.
• Tie post receipts to the actual create-story response and verify the exact resulting URL/content. Delayed old posts cannot be mistaken for newly created posts.

Validation and builds

Real-Chrome fixture E2E runs in CI on Linux, macOS and Windows. It exercises the real CLI with intercepted traffic and no real credentials. The opt-in live acceptance script creates one unique Only-me post, verifies privacy/content, and moves it to Trash with failure cleanup.

The release publishes five platform archives plus SHA256SUMS only after verification and every build succeed.

Browser-level primitives provide reach beyond the dedicated commands; every individual Facebook feature is not separately tested. Human login, 2FA, and a Messenger encryption PIN can still be required. Facebook may change its UI/protocol. Explicit eval/CDP/screenshots can expose private data; handle them accordingly.

Ordinary snapshots omit all native form values and text-editor contents, regardless of labels (including effective contenteditable modes). Use targeted explicit eval/CDP to read values. Messenger inserts a whole multiline draft in one input operation and verifies the exact draft and focus before submission, refusing changed drafts instead of sending partial text.