feat: add --objective to alexandria feedback

[nickscamara]

Summary

firecrawl alexandria feedback now requires --objective <text>: the underlying goal behind the session, meaning what the agent or its user was ultimately trying to accomplish. This is broader than --requested-functionality, which only covers the one website.

• The value is trimmed and must be 1–2000 characters. It is sent as the top-level objective in POST /v2/feedback.
• The firecrawl-alexandria and firecrawl-agent skills and the README explain the field and include it in their examples. After merge, the skills sync to firecrawl/skills automatically.

Depends on

• feat(api): accept objective in Alexandria feedback firecrawl#4877 must be deployed before this is released. The API rejects unknown keys in Alexandria feedback until then.

Tests

vitest run: 657/657 pass. The tests cover the payload with a trimmed objective and rejection of a missing or blank --objective before any request is sent.

Made with Cursor

---

Summary by cubic

Adds a required --objective flag to firecrawl alexandria feedback so sessions capture the underlying goal of the task, which is broader than --requested-functionality. The value is trimmed, must be 1–2000 characters, and is sent as the top-level objective in POST /v2/feedback. The package version is bumped to 1.25.1.

• Missing or blank --objective is rejected before any request is sent.
• The firecrawl-alexandria and firecrawl-agent skills and the README document the field and include it in examples.
• Requires firecrawl/firecrawl#4877 to be deployed before release; the API rejects unknown keys until then.

^{Written for commit 254cd54. Summary will update on new commits.}

[cubic-dev-ai]

No issues found across 7 files

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

<sub>Shadow auto-approve: would require human review. Adds a required --objective flag to the Alexandria feedback CLI and sends it in the POST /v2/feedback payload; the decisive factor is the public CLI/API contract change and the dependency on backend deploy firecrawl/firecrawl#4877 for compatibility.

Re-trigger cubic</sub>