Update developer dashboard documentation to reflect recent release/testing framework changes

[annakrystalli]

Context

Significant changes have landed (and are landing) across the dashboard pipeline's release and testing framework. The developer-facing docs in hubverse-org/hubDocs have not yet been updated to match, and a new contributor following the existing pages would miss several load-bearing concepts.

The changes touch multiple repos and affect overlapping pages, so the right first step is to scope what needs updating where, before anyone writes prose.

High-level changes to reflect (non-exhaustive)

This list is intentionally rough; treat it as input to scoping, not a checklist:

• CI workflow restructure in hubverse-org/hubPredEvalsData-docker: split into chain-build, publish-base-dev, and publish-production, each with narrow path filters and a single concern (Split CI workflows and base production on shared base image hubPredEvalsData-docker#32).
• Base + dev + production image architecture: shared base image, dev image for lockfile updates and exploratory testing, production image as the consumer surface. Includes the renv-as-installer-only pattern in production (autoloader disabled) versus the conventional renv project in dev.
• Orchestrator refactor in create-predevals-data.R (Refactor create-predevals-data.R into thin orchestrator (#6, #22) hubPredEvalsData-docker#36): default oracle discovery now uses hubData::connect_target_oracle_output(), with a deprecated -d shim and a transitional --legacy-oracle-fallback option for the control-room workflow's migration window.
• Control-room workflow migration (Migrate evals pipeline off legacy oracle probe (#108) hub-dashboard-control-room#109): drops the legacy CSV-only probe and the dashboard oracle-data branch fallback; uses the new docker invocation surface.
• Three dev container workflow patterns for renv.lock work: just update (ephemeral), update + verify (ephemeral, one-shot), update + verify + explore (persistent). Documented in hubverse-org/hubPredEvalsData-docker's README.
• Role of dashboard-test-hub-dashboard in release waves: this test fixture leads release waves (config can reflect r-universe state ahead of :latest). A sanity-check workflow is in scope to automate that staging signal (Add a CI sanity-check workflow that exercises this config against latest upstream releases dashboard-test-hub-dashboard#8).
• Local dashboard build skill in hubverse-org/hubverse-claude-skills (Add dashboard-local-build and dashboard-smoke-test skills hubverse-claude-skills#3): a Claude skill for spinning up the local dashboard build flow. Once it lands, the local-build docs page should reference it.

Affected pages (approximate, scoping will refine)

Best-guess starting set, will need confirmation:

• developer/dashboard-local.md
• developer/dashboard-workflows.md
• developer/dashboard-predevals.md
• developer/dashboard-staging.md
• developer/dashboard-tools.md

First step: scope

Before writing any prose, decide:

1. Which concepts above belong on which page (some may need new sections or even new pages).
2. Which pages need light edits vs. substantial rewrites.
3. Whether any concepts are better tracked as their own dedicated docs issues that this one links to.
4. Which changes are still in flight (e.g. the sanity-check workflow on dashboard-test-hub-dashboard) and should be left as TODO links until they land vs. documented as-implemented.

Update this issue body (or open child issues) with the scoped plan, then proceed to writing.

Cross-links

• Split CI workflows and base production on shared base image hubPredEvalsData-docker#32 (CI restructure + base/dev/production architecture)
• Refactor create-predevals-data.R into thin orchestrator (#6, #22) hubPredEvalsData-docker#36 (orchestrator refactor + renv bump)
• Migrate dashboard pipeline off legacy -d <oracle> argument and dashboard oracle-data branch fallback hub-dashboard-control-room#108 / Update software.md #109 (control-room migration plan + PR)
• Add a CI sanity-check workflow that exercises this config against latest upstream releases dashboard-test-hub-dashboard#8 (sanity-check workflow + README role note)
• Add dashboard-local-build and dashboard-smoke-test skills hubverse-claude-skills#3 (local dashboard build skill)