H-6717: Dashboard config and refresh improvements

[CiaranMn]

🌟 What is the purpose of this PR?

Fix some bugs and improve behaviour related to the custom dashboard page:

1. Better handling of users manually defining chart config (as opposed to using the AI generation feature)
2. Improve cache-busting behaviour of users clicking to regenerate the chart

Also fix a bug in the document inference flow where patching an email was referring to the wrong property key.

Pre-Merge Checklist 🚀

🚢 Has this modified a publishable library?

This PR:

• does not modify any publishable blocks or libraries, or modifications do not need publishing

📜 Does this require a change to the docs?

The changes in this PR:

• are internal and do not require a docs change

🕸️ Does this require a change to the Turbo Graph?

The changes in this PR:

• do not affect the execution graph

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
hash	Ready	Preview, Comment	Jul 22, 2026 3:52pm

2 Skipped Deployments

Project	Deployment	Actions	Updated (UTC)
hashdotdesign-tokens	Ignored	Preview	Jul 22, 2026 3:52pm
petrinaut	Skipped		Jul 22, 2026 3:52pm

[cursor]

PR Summary

Medium Risk
Touches dashboard data caching and Temporal workflow deduplication behavior plus entity persistence for configuration status; changes are scoped but affect paid sandbox recomputation and when items become ready.

Overview
Dashboard chart refresh now uses an explicit recompute analysis argument instead of force. User-initiated refresh always sends recompute: true on the first request; the API starts Temporal with ALLOW_DUPLICATE only for that case so a new run can start even when a workflow id already exists, while normal and background refreshes keep deduplication via REJECT_DUPLICATE.

Manual configuration treats chart series as the source of truth: getPrimaryChartType derives display type from the first series, validation rejects empty series, saves persist chartType from the config, and partial saves can set configurationStatus to ready when query, script, and chart are all present. The grid renderer resolves chart type from config before falling back to the stored property and separates missing config vs missing data errors.

The document inference flow fixes author email property metadata to use systemPropertyTypes.email.propertyTypeBaseUrl instead of the data type base URL.

^{Reviewed by Cursor Bugbot for commit 8a9711a. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

Want reviews to match your repository better? Bugbot Learning can learn team-specific rules from PR activity. A team admin can enable Learning in the Cursor dashboard.

^{Reviewed by Cursor Bugbot for commit 8a9711a. Configure here.}

[cursor]

Maps require chart config now

Medium Severity

Position-based map items previously rendered from chartType and chart data alone via WorldMapRenderer, which does not use chartConfig. The new early chartConfig guard blocks that path, so map items that only have chartType set show “Missing chart configuration” instead of the map.

Additional Locations (1)

• apps/hash-frontend/src/pages/dashboard/[dashboard-id].page/dashboard-grid/dashboard-item/dashboard-item-content.tsx#L223-L232

 

^{Reviewed by Cursor Bugbot for commit 8a9711a. Configure here.}