This page is now historical. The Nick launch blocker described below was closed by Nick Attorney Hub Agentforce deployed and verified - 2026-06-01. Live cleanup verification also found Nick_Attorney_Hub_Agent Bot metadata in LITIFY_ORG. Treat older timeout, missing Bot, or unpublished wording below as stale context, not a current blocker.
Continue equipping and testing the Nick attorney hub Agentforce section, improve clarity for agent capabilities, and keep pushing toward deployability while the publish path remains unresolved.
scripts/diagnose-nick-agentforce-publish.mjs to create a sanitized support packet for the Nick Agentforce publish lane.codex/nick-agentforce-hub-2026-05-29 in PR #9.tmp/nick-agentforce-publish-diagnostic-full-20260531.json.LITIFY_ORG is connected to production org samaguiarinjurylawyers2.my.salesforce.com.sf agent validate authoring-bundle --api-name Nick_Attorney_Hub_Agent --target-org LITIFY_ORG --json succeeds.node scripts/run-nick-agentforce-qa.mjs --org LITIFY_ORG succeeds across open matter search, since-2024 archive search, report/dashboard advisor, insurance knowledge, and document draft prep lanes.node scripts/run-nick-agentforce-preview-qa.mjs --org LITIFY_ORG --mode live succeeds and ends the preview session cleanly.sf agent preview sessions --target-org LITIFY_ORG --json returns no active sessions after QA.sf org list metadata --metadata-type Bot --target-org LITIFY_ORG --json still lists only Litify Conflict Check Agent and Litify Matter Summary Agent. No Nick Bot metadata exists yet.sf agent publish authoring-bundle --api-name Nick_Attorney_Hub_Agent --target-org LITIFY_ORG --skip-retrieve --json still fails with FetchError and ETIMEDOUT against https://test.api.salesforce.com/einstein/ai-agent/v1.1/authoring/agents.agent 1.40.3, with @salesforce/agents package 1.6.6.https://api.salesforce.com/einstein/ai-agent/v1.1/authoring/agents and falls back to test.api.salesforce.com only after a 404 from production.sfdc_app_id and scope, including SFAP scope fields.