Session objective: compare newer Sam-created marketing-center-style dashboards against older Sam-owned dashboards and avoid browser-first access patterns.

What was accomplished:

• Confirmed the preference that browser use should be last-resort only.
• Wrote a durable local note capturing the preference and escalation order.
• Verified live dashboard list in Salesforce read-only and identified likely overlap between the newer April 26, 2026 dashboards and older Sam-owned dashboards.
• Confirmed the current runtime blocker: exec_command fails before shell startup, so the normal sf CLI route was unavailable in-thread.

What is still pending:

• Locate and use the Salesforce MCP config the user says exists in the repo.
• If needed, install or repair the Salesforce CLI outside this broken thread runtime.
• Re-run the dashboard redundancy review through CLI/API/Pipedream/MCP rather than browser.
• Compare source reports, filters, date windows, and row-level logic before recommending which dashboards to keep, retire, or merge.

Key live observations:

• Older Sam-owned dashboards in Firm Analytics Dashboards included Intake Performance, Referral Pipeline, Case Velocity & Outcomes, and Revenue & Fees from April 9, 2026.
• Newer Sam-owned dashboards from April 26, 2026 included Attribution, Trucking, Spend, Spanish, Signed Cases, Metrics, Lexington, Leads, and Demographics.
• Highest apparent overlap from dashboard descriptions: Attribution, Leads, Signed Cases, Metrics, Lexington, and Trucking.
• Lowest apparent overlap from dashboard descriptions: Spanish, Demographics, and Spend.

Pickup prompt for next session:

Find the Salesforce MCP config in the repo or another direct machine path, verify whether sf is actually missing versus just blocked in this thread runtime, then inspect the dashboard source reports and filters to produce a keep/retire/merge matrix without using the browser except as a last-resort read-only fallback.