[Daniel-Deepak-Dev]

Daily Salesforce scan for 2026-07-30, filed as dated notes in the three area folders plus refreshed topic files.

Note on scope

The scheduled prompt asked for a direct commit to main. This session's harness policy pins development to claude/peaceful-maxwell-gfqvti and forbids pushing elsewhere, so the work landed on that branch and this PR is the route to main — merging it puts the notes on main with one click.

Because days 07-27 → 07-29 were never merged (PR #1 removed the dated folders when it restructured into topic files), this PR carries that backlog too. Today's scan is the new work; the earlier dated notes come along with it.

Today's findings

Agentforce — in-window, July 29, 20:21–22:22 UTC. The DX Node library stack cut majors on a single breaking change: @salesforce/core 9.0.0, @salesforce/source-deploy-retrieve 13.0.0, @salesforce/agents 2.0.0 — engines.node >= 22.0.0, Node 18 and 20 dropped. This is the consequential item because @salesforce/agents implements the sf agent command family (generate, test, preview) and SDR is the engine behind sf project deploy, so it sits under agent testing and every metadata deploy. The break is quiet: npm installs on Node 20 with an EBADENGINE warning and proceeds, then fails later in ways that look like metadata problems. Installer/tarball sf bundles its own Node (v24 since Feb 2026) and is insulated; npm install -g and actions/setup-node pinned to 18/20 are not.

Also in-window: sf-pi v0.250.0/v0.251.0 added native Agent Script quality analysis — an 18-rule catalogue where High findings block publication, and release evidence that expires on identity rather than on time ("valid while the exact org, BotVersion, baseline identity and suite digest are unchanged"). @salesforce/react-native-agentforce 0.3.0 reached npm (voice for Service Agents, configurable silence timeout, UIDelegate event bridge, native SDKs at 262.1).

Two open, unmerged PRs are recorded as proposals, with their state stated in the entry rather than buried: an Agent Script doctor in agentforce-adlc (#46), whose six named anti-patterns — misleading pipe-text indentation, fake step sequencing, ungated actions, turn-ending setters, stale state, competing side-effect owners — are usable as a review checklist today with no tooling; and a GIFT-Eval leaderboard submission (#182).

Data 360 — no product news for the fifth consecutive scan. What the window produced is in the developer surface: the Node 22 floor reaches Data 360 metadata deploys through SDR; the Python salesforce-cdp-connector is deprecated with salesforce-datacloud-connector still at 2.0.0b1 beta and no GA date; and next-gen-wealth added fail-safe messaging to its Data 360-grounded prompt templates — the standing question for every template: what does it say when its grounding returns nothing?

Salesforce AI Research — no new paper, model, benchmark or repository. The GIFT-Eval note covers the transferable part, its submission protocol: 98 fixed configurations, a declared test-data-leakage flag printed beside every result, a required replication link. AnchorBench's paper is still not on arXiv, re-verified.

Files

File	Change
01-agentforce/2026-07-30.md	New — 5 entries + scan coverage, mermaid diagram of the dependency wave
02-data-cloud/2026-07-30.md	New — 3 entries + scan coverage, mermaid diagram of the deploy chain
03-salesforce-ai-research/2026-07-30.md	New — 2 entries + scan coverage, mermaid diagram of the submission protocol
developer-tooling-and-apis.md	Two entries added (Node 22 wave, sf-pi quality gates)
data-360.md	One entry added (Python connector deprecation + deploy floor)
README.md	Index, state of play, new open question, date

Honesty notes carried in the files

• Every open PR is labelled open and unreviewed, with an explicit caveat that it may change or not land.
• arxiv.org and huggingface.co returned HTTP 403, so "no new paper" is well-supported for GitHub-visible artifacts and weaker for arXiv/Hugging Face — stated in the AI Research note rather than implied.
• An org-wide OSPO CODEOWNERS sweep on July 29 made several repositories look freshly updated; recorded as metadata noise to filter, not as activity.
• One inconsistency flagged rather than smoothed over: the React Native SDK releases page shows a 2024 date that contradicts its own commit timestamps; the note cites the commit feed and says why.
• arXiv:2607.07985 (LALM audio judges, Salesforce Applied AI Research) is recorded as a lead to verify, not a finding — its date could not be confirmed.

All markdown anchors validated against their headings (github-slugger rules) and all relative links resolve.

---

Generated by Claude Code