Reconcile enterprise/cloud doc divergence + add bump-last-updated tooling

[justinegeffen]

Summary

• Fixes drift bugs surfaced by an enterprise vs cloud doc audit (broken refs, half-completed rebrands, regressions, UI-label inconsistencies, stale Bitbucket flow, etc.)
• Normalizes frontmatter date format across both trees to date created: "YYYY-MM-DD" + last updated: "YYYY-MM-DD"
• Adds a bump-last-updated pre-commit hook + extends pre-commit-fix.yaml to auto-trigger on PRs so last updated: stays current without manual effort

The full per-file rationale (decisions, ports, audit corrections, deliberately-untouched items) lives in enterprise-cloud-divergence-audit.md. That doc is the canonical decision log — it deliberately keeps this PR description short.

Test plan

• Confirm the new bump-last-updated hook works locally (pre-commit run bump-last-updated --all-files)
• Confirm the extended pre-commit-fix.yaml workflow runs on this PR's synchronize event and that the bot only commits a bump if dates are stale
• Spot-check a few of the user-direction calls (R-IDE rebrand, "Revision" UI label, studio:execute Launch=❌, j21-26.04 launcher row)
• Verify the Antigravity skill port renders correctly on the preview build
• Verify the Bitbucket section update on Enterprise renders correctly

🤖 Generated with Claude Code

[netlify]

✅ Deploy Preview for seqera-docs ready!

Name	Link
🔨 Latest commit	a370e98
🔍 Latest deploy log	https://app.netlify.com/projects/seqera-docs/deploys/6a4c11b5f744a80008897499
😎 Deploy Preview	https://deploy-preview-1547--seqera-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[christopher-hakkaart]

Most of this PR is cosmetic and date added and changed improvements. So it looks worse than it actually is.

95% of these changes are not offensive.

I've been through the changes and flagged anything that I think needs checked. IMO - everything else can be skimmed.

The report at the end flags some important differences and can be reviewed separately for quick wins.

[christopher-hakkaart]

I'll check the scripts again next week. But otherwise looking good.

[christopher-hakkaart]

This is a massive PR. I worry it could get stuck in an endless review loop if we try to address everything in the audit file. I suggest we verify the changes made as a part of this PR, and move everything else to new, smaller PRs.

Editorially, everything looks okay to me. Vale and other checks might light up as so many files are being touched.

Enterprise ↔ Cloud divergence — content verification checklist

Verify each applied change against the live product. Tick once confirmed correct (or flag if it needs reverting).

Content ports — confirm the ported content is accurate for its destination

• Bitbucket API tokens — platform-enterprise_docs/git/overview.md: confirm the API-tokens flow is correct for Enterprise's supported Bitbucket integration — Username = account email, Password field renamed to Token, and the deprecation dates.
• Antigravity / Gemini skill — platform-enterprise_docs/co-scientist/skill-antigravity.md (new file) + Antigravity bullet in co-scientist/coding-agents.md: confirm the Antigravity/Gemini integration actually works on Enterprise deployments, not just Cloud.
• AWS Secrets Manager ListSecrets warning — platform-enterprise_docs/secrets/overview.md: confirm the IAM gotcha (scoping the policy down without keeping ListSecrets on * → secret-deletion failures / stuck workflows) genuinely applies to Enterprise.
• Launch form fields — platform-enterprise_docs/getting-started/quickstart-demo/launch-pipelines.md: confirm Version name, Version ID, Main script, and Schema (Repository default / Repository path / Seqera Platform schema) all appear in the Enterprise launch form.
• /migrate-from-wdl and /write-nf-test skills — platform-cloud/docs/co-scientist/reference/skills-reference.md: confirm both skills exist and are available on Cloud.

Product-fact decisions — confirm the value matches the live product

• studio:execute for Launch role — platform-enterprise_docs/orgs-and-teams/roles.md: confirm the Launch role's studio:execute is actually False (now ❌ on both trees).
• Default launcher j21-26.04 — platform-enterprise_docs/functionality_matrix/overview.md, 26.1.0 row: confirm the default launcher from 26.1.0 is j21-26.04 (new format) on both Cloud and Enterprise.
• Token placeholder <ACCESS_TOKEN> — credentials/agent_credentials.md (both trees), getting-started/quickstart-demo/automation.md (Enterprise), supported_software/agent/overview.md (both trees): confirm <ACCESS_TOKEN> is the right placeholder and doesn't contradict any literal token name the CLI/API actually requires.

versioning.md reconciliation — confirm the ported content

• Complete JSON params example — platform-enterprise_docs/pipelines/versioning.md: confirm the full "my_parameter": { ... } example (which replaced the old truncated { "track_changes": false } fragment) is correct and valid.
• Deletion-scope wording — platform-enterprise_docs/pipelines/versioning.md: confirm "Individual draft versions cannot be deleted" is accurate — i.e., that non-draft versions behave differently.

[justinegeffen]

@copilot resolve the merge conflicts in this pull request

[Copilot]

@copilot resolve the merge conflicts in this pull request

The merge conflicts were already resolved in commit 89536a1.

The branch also had a failing pre-commit check due to three files with stale last updated: dates after the master merge — fixed in the latest commit by bumping them to today (2026-07-06):

• platform-cloud/docs/compute-envs/preflight-checks.mdx
• platform-cloud/docs/getting-started/quickstart-demo/add-data.md
• platform-cloud/docs/getting-started/deployment-options.md

The Lint prose failure is a GitHub API size limit — the PR touches >300 files, so reviewdog can't fetch the diff. That's a known limitation of large PRs and isn't blocking.

[justinegeffen]

@copilot resolve the merge conflicts in this pull request

[Copilot]

@copilot resolve the merge conflicts in this pull request

Resolved in commit a370e98. Two new master commits (#1632, #1633) had landed since the last merge, causing conflicts in three files. Resolved by taking master's updated content and keeping the normalized frontmatter date format from the branch:

• platform-cloud/docs/data-privacy/overview.md
• platform-enterprise_docs/data-privacy/overview.md
• platform-enterprise_docs/limits/overview.md