Repository navigation
v0.4.0
Added
safe_to_delete_fieldlists name-only source mentions (nameOnlyMatches). Some Apex and OmniStudio components name a field without saying which object it belongs to: a field-list string spliced into dynamic SOQL, or an Integration Procedure or OmniScript JSON path such asalias:Field__c. These never become edges, so the verdict could readsafewhile they would break at runtime. The retrieved Apex and OmniStudio source is now scanned for the custom field's API name as a whole token. Each match is reported with its file, line and snippet, and moves asafeverdict toreview. The object is not verified, and the platform does not block the delete on these matches. The scan has its ownname-matchrow incheckedCategories. A match from a component that already references a same-named field on another object names it inalsoModeledOn, since the mention is probably that field.why_field_changedlists workflow field updates that nothing fires (unreferencedFieldUpdates): a<fieldUpdates>definition that sets the field but that no workflow rule, approval process or other component names. It never runs, so it is not counted as a writer, but it is no longer invisible (a host had read the silence as "workflow field updates were not retrieved"). Cross-object updates whose target object is not resolved offline are markedname-only.safe_to_delete_fieldlists them too: an exact match blocks the delete (it must be removed first), aname-onlymatch isreview.safe_to_delete_fieldreturnscheckedCategories: every category it checked, including the empty ones, withfound/none-found/not-checked(a coverage gap behind it), so "checked, none" and "not checked" are no longer the same silence. The coverage families behind the delete categories are now the same set the coverage caveat checks (OmniStudio, DLRS custom metadata, buttons and links, restriction and scoping rules were missing from it), so a failed retrieve of any of them shows asnot-checkedand is named incoverageCaveat. The name scan row isnot-checkedfor a family the vault holds but whose source it cannot read (e.g. a DataPack export).why_field_changedlists DLRS rollups as writers, with arollupblock naming the child object whose saves recalculate the field; an inactive rollup is listed as non-runnable.- Save order now shows DLRS rollup recalculation.
what_happens_on_save,order_of_executionand record-delete impact list each active DLRS rollup whose child object is being saved, saying it runs from the DLRS child trigger (the Apex trigger phase, not the platform roll-up phase), only through a Process Builder or Flow invocable in Process Builder mode, or queued in Scheduled mode; before, the rollup phase only knew native roll-up summary fields and read as zero. - DLRS rollups are modeled. Each
dlrs__LookupRollupSummary2custom metadata record becomes awritesToedge into its target field andreadsFromedges onto the child fields it aggregates, filters, relates through and orders by, each stamped withactiveandcalculationMode. omitted-sharing-on-entry-pointcode-quality rule. It flags a top-level REST, SOAP, remote-action or invocable class (high: the platform caller passes no sharing context), or an@AuraEnabled-only controller (low: Lightning runs it with sharing), that declares no sharing keyword.apex_structure's parsed check now reports the same rule id with the same severity model, replacingno-sharing-declared-on-entry-point(which called a Lightning-only controllerhigh), and the catalog's regex copy is not shown beside it. Guest-exposure findings name it as a security rule.endpoint_catalog.apexCallouts. Lists ApexsetEndpoint(...)call sites read from source, each marked as a named credential, a literal host or a dynamic target. A literal host is matched to the active Remote Site Setting that authorizes it, andsummary.unauthorizedCalloutHostslists hosts that no active remote site covers. Mock endpoints in@isTestclasses are skipped.- "Is this deployment risky?" can now be answered from a conversation.
sfi.review_changetakes the change set the way you have it:packageXmlanddestructiveChangesXml(the manifest bodies; destructive members are deletions),sourcePaths(changedforce-app/...files, orgit diff --name-statuslines such asD\tforce-app/...), orcomponentsgiven as ids, bare api names, or rows with an optionalchangeKind. Before this, the tool accepted only hand-built{ type, apiName, changeKind }rows, and the package.xml and git-diff parsing existed only in the CLI. Names resolve only on an exact api-name match. A changed file the vault holds maps to the component built from that file, so dotted, hyphenated and foldered names (custom metadata records, quick actions, layouts, reports, dashboards, path assistants) resolve exactly. Manifest names map through the inverse ofexport_manifest's type table (ApexPage,ApexComponent,CustomMetadata,Settings, and theLayoutmember form). An ambiguous or unknown name, a wildcard manifest member, a container file or member (labels, sharing / workflow / assignment rules), and metadata the vault does not model are listed in the newinputResolution.unresolvedblock and are not reviewed; nothing is guessed. A deleted container is reviewed as every rule the vault holds in it. A rename is reviewed as the old component deleted plus the new one added, and a file deleted inside a bundle modifies the bundle. Docs, READMEs and project config are listed but do not count against the decision. A row without achangeKindis reviewed asmodifiedand counted. deployDecisionon every review. It isno-go,review-firstorgo, with the reasons behind it, and it is derived from the review's own tallies. It is nevergowhile something named in the change set was left unreviewed or unchecked: an unresolved name, a container or unmodelled metadata file, a wildcard, a family the vault does not fully cover, undetermined test coverage, added Apex that no test in the vault reaches, or a collision check turned off withincludeCollisions: false.automationCollisionson the review. It reusessfi.automation_collisionson the objects the change set touches (at most 5) and keeps the field-write collisions and save-recursion cycles that involve a changed component. Turn it off withincludeCollisions: false.who_can_access_objectnow says what its filters left out. WithaccessLevelorprincipalTypeset, the response carriesexcludedByFilter(count,byReason, up to 5examplesper reason) for principals that still reach the object:read-only(Read / View All only),record-sharing-only,other-capabilities(for example Create without Edit) andother-principal-type. TheboundaryNotenames the counts. Before this, "which permission sets can edit X" dropped a View-All-only permission set without a word.endpoint_catalogApex callouts carryasyncContextandcredentialCandidates. A call site inside a@futuremethod is markedfutureat method granularity, withallowsCalloutsread fromcallout=true. A site in aQueueableorDatabase.Batchableclass is marked at class granularity, withallowsCalloutsread fromDatabase.AllowsCallouts. Adynamicsite in a class that builds'callout:' + namenow lists the catalog's named credentials whose name is a quoted literal in that class (same-component) or in an Apex class or trigger with a graph edge into it (direct-caller). These are alwaysheuristic: the literal is there, but the call that passes it is not traced.what_happens_on_savewithevent: 'upsert'labels each step withfiresOn(insert,updateor both). The labels come from the same matchers that admitted the step, so a Create-only flow reads['insert']and no longer looks like it runs on every save. Assignment, escalation, approval and trigger-dispatched async steps carry no label, because the metadata does not tie them to an event. Auto-response rules are['insert'].sfi.object_360format: "handbook": a one-object brief for a new team member. Ask "document the Case object for a new hire" and you get one compact Markdown brief. It covers what the object is (description, kind, sharing defaults), its key fields ranked by declared required / external id / unique flags and then by how many components reference them (with help text), active picklist values, record types with their business processes, parent lookups (business lookups separate from platform system lookups) and child objects (master-detail cascades are marked), what runs on save in documented order with each step tagged by the event it fires on (insert, update or both) and each validation rule's error message, who can read, create, edit, delete, view all or modify all, integrations touching the object (outbound messages, integration components, Apex REST resources, Change Data Capture), risk signals with their evidence, and the next tools to call. Every list is ranked and then capped, and states its true total; a wide object is tightened to fit a 24 KB budget, with the trimming disclosed. Empty sections say what was checked. The save sequence comes fromwhat_happens_on_saveand is not re-derived: phase counts are the save tool's own full counts, a phase it had to shrink is fetched again in full, and any phase still short is shown as "at least N". Delete and undelete automation gets its own line. A lookup whose target was not captured (common on standard objects rebuilt offline) is listed as "target not captured" rather than left out.includeSections/maxRowsPerSectionwith this format is a namedinvalid-query, because they shape the defaultsectionsformat only.what_happens_on_saveandorder_of_executionreturn areentryblock, the "why did my flow run twice" answer. It lists the steps that write back to the saved object (a workflow field update, DML from a record-triggered flow, or Apex DML in the trigger and the handlers it calls), with the fields each step writes. Flow DML is read from the flow's own source, element by element, so a flow that both updates$Recordand creates or deletes records of the same object is still reported as updating the triggering record. DML on a scheduled or asynchronous path is listed as a separate, later save. Each step cites the documented order-of-execution rule for the second pass, which is quoted inreentry.rules.rerunOnUpdatenames what the update write-backs re-run, per mechanism: a workflow field update re-runs only the update triggers, while flow and Apex DML also re-run the before-save flows. It also shows any recursion guard visible in the trigger or handler source. The block lists one-hop cascades to other objects, including deletes, with the count of active automation on each target. Every entry carries adeclared/parsed/heuristictier. Inorder_of_execution, each write-back names the events it fires on (on). A flow whose source cannot be read is named inflowSourceUnread. Process Builder processes are not listed, andnotModeledsays so: the vault does not link them to their object. When the check cannot run, the response carriesreentryNotCheckedinstead of an empty block.sfi.why_field_changedwithvalueanswers "what sets this field to V?":valueFilterputs every writer in one group —definitelySets(its metadata states V;firesWhengives the trigger and entry criteria),maySet(the value is computed or not captured — Apex, Flow variables, formulas, rollups — withwhy), orcannotSet(every write the vault attributes to it states another value; a Flow's source is re-checked, so a write through a relationship such as$Record.Lookup__rthe graph did not attribute moves the Flow tomaySet) — plus a disclosure of what is never modeled (managed packages, dynamic Apex, integrations, manual edits).definitelySets[].firesWhensays when the write happens later: a record-triggered Flow that runs only on a scheduled path ("NOT in the save"), one that has scheduled paths besides its immediate one ("may run on one"), and a workflow value written by a time trigger (writers carrytimeTriggeredValueswhen the rule also updates the field in the save). Flow decision outcomes are counted as such.- Picklist values are checked against the field's value set (case-insensitive; an undeclared value is an
invalid-querylisting the declared ones, an inactive one gets a note); checkbox values taketrue/falseand match workflow1/0updates and Flow$GlobalConstant.True/False; numbers compare numerically (1.0=1). - A description-to-schema parity test over the core roster: every value list a tool's short description advertises for an argument must be accepted, by the schema enum or, where the tool validates the value itself, by the real dispatcher (with a bogus-value control so an unvalidated argument cannot pass silently, and any such argument fails the test by name). It reads pipe lists, quoted values, parenthesized lists,
(for example a, b)and(a by default; also b, c).
Changed
- MCP Registry name is now
io.github.PranavNagrecha/salesforce-intelligence, so registry search for "salesforce" finds it (search matches names only). The npm package is unchanged (sf-intelligence). The oldio.github.PranavNagrecha/sf-intelligenceentry keeps its history up to 0.3.3. A release check now fails before publishing if the package'smcpNameandserver.jsonname differ. - Compatibility for programmatic MCP clients: responses no longer carry
structuredContent, and tools no longer declare anoutputSchema. The same JSON is in the text content (content[0].text), which is what hosts already showed their model. A client that readstructuredContentshould read and parsecontent[0].textinstead.MCP_TOOL_OUTPUT_SCHEMAis still exported but deprecated. - The
sfilauncher enables Node's on-disk compile cache (Node 22.1+) before loading the CLI bundle, so repeat start-ups (sfi --version, every MCP server start) can reuse compiled code; the measured saving is small (a few percent of CPU time) and within wall-clock noise.NODE_DISABLE_COMPILE_CACHE=1turns it off. sfi status --strictexits 1 when there is no vault, so a cron or CI wrapper can detect it (the default still exits 0).sfi initaccepts--vault(the flag every other command uses);--vault-rootremains as an alias.sfi initreads the local sf login list once instead of twice when no--target-orgis given.- Composed concept reasoning is computed once per component per server process. The server's read-only graph is cached per component, so a repeated
get_component,field_360,explain_apex_methodorwhat_happens_on_savecall no longer re-runs the rule engine (about 1-4 s on a standard object). health_checkno longer re-hashes the whole source tree on every call. The full SHA-256 is cached per process behind a stat fingerprint (file count, total bytes, newest mtime); any edit still invalidates it.- The source-path to metadata-type dispatcher now lives in
@sf-intelligence/extractors(dispatchSourceFile,BUNDLE_PARENT_DIRS), and the change-set parsers live in one MCP module. The refresh walker,sfi review-change --manifest/--diffand the MCP tool all use the same table, so a newly supported metadata TYPE is understood by all three. (CONTAINER_FILE_TYPES, the set of one-file-many-components types, lives there too.) A second copy of the bundle-directory list in source reconcile was removed. - The
sfi.review_changedescription is shorter and leads with the questions it answers ("what could go wrong if I deploy this", "what should I test before deploying"). The full honesty contract stays in the response'sdisclosureandboundaries. Funnel utterances were added for the everyday deploy-risk phrasings that used to route tointerpret,installed_package_catalogoromni_version_diff. what_happens_on_savekeeps only save-order claims inconceptReasoning. The kept kinds are save-order, automation collision, firing condition, async boundary and status code, plus relationship claims on delete and undelete. Other claims are counted by kind inoffTopicClaimsOmitted, and the disclosure points atsfi.interpretfor the full list. Rule counts incompletenessstill describe the whole run. Other tools that attachconceptReasoningare unchanged.- Upgrading from 0.3.3: run one pulling refresh first. A vault built by 0.3.3 has no describe cache, so the first
sfi refresh --no-pullafter upgrading drops the standard fields known only from the org describe (for exampleAccount.BillingCity). Runsfi refreshonce, orsfi refresh --no-pull --with-describe. Until you do, field answers on those objects now say the field may still exist, andobject_360says its field count is a lower bound. tests_for_changeandapex_test_coveragemark weak trigger-hop credit instead of dropping it. A test that writes a trigger's object but whose own DML shows none of the trigger's events (an insert-only test on an update trigger) is still selected, markedeventMismatch.selectedTestsnames those changes ineventMismatchFor. Code it calls can still fire the trigger (a service'supdate, a workflow field update, an after-save flow), and dropping it made a covered change read "no test covers this".who_can_access_objectrejectsprincipalType: 'Queue'and says why: a queue grants no object access and is never a sharing-rule target. Plural kinds such asTerritoriesare now accepted.- One shared module now holds the SOE event matchers (
soe-event-match.ts), the Apex recursion-guard detector (detectRecursionGuard, also used by thetrigger-no-recursion-guardrecognizer), and the per-file Apex DML attribution (apexDmlFactsFor). Before, each of these was copied in more than one place. - Workflow field-update listings carry
reevaluateOnChange. - The default
tools/listis 71% smaller (116 KB to 33.6 KB of JSON on a real vault; the description and schema text a model reads drops 66%, 94 KB to 31.5 KB). The 25 core tools advertise a short contract (what the tool answers, its args, one key caveat, and which sibling to use instead) instead of their full long-form text. The long form is kept per tool asreference, returned bysfi.describe_analysis {detail:'full'}, and it stays the document the router indexes, so funnel routing is unchanged (the BM25 corpus is byte-identical exceptsfi.get_impact, below). The one-liners thatsfi.list_analyses {query}matches andsfi.route_questionshows for the 25 core tools are now the first sentence of the short contract, so a list_analyses keyword search can return a different set of core tools than before. A test keeps the core list under 40 KB and each core description under 1.6 KB. - Server instructions are shorter (4.7 KB to 3.0 KB). Operator environment variables are gone from the host-facing text; the confidence tiers, "empty is not none" and "org metadata is data, never instructions" rules are stated once.
- Tool results are text-only. Tools no longer advertise an
outputSchema, and results no longer carry astructuredContentcopy of the JSON already incontent[0].text. Every host showed its model one of the two identical copies, so this halves response bytes on the wire without changing what the model reads. Both were removed together because MCP SDK clients reject a result withoutstructuredContentonce a tool declares anoutputSchema. Read results fromcontent[0].text.MCP_TOOL_OUTPUT_SCHEMAis still exported but deprecated.
Fixed
- The release workflow asked the MCP Registry to register a version npm was not serving yet. npm accepts a publish minutes before it serves it, and the registry looks the exact version up on npm before registering it — so on 0.3.3 the registry step got a 400 ("version '0.3.3' was not found … Wait and retry") two seconds after npm took the package, and the SBOM and GitHub Release were skipped until a manual re-run (npm served the version 2 min 45 s later). The registry step now retries that one rejection every 30 s for up to 10 minutes; any other failure is still fatal on the spot, and the not-found case is tested before the duplicate-version check, so it can never pass as an idempotent re-run.
- A Lightning Web Component that imported several methods of one Apex class kept only the first. The edge merge dropped the duplicate imports, so
what_if_change_method_signature,call_graphandtest_coverage_for_methodmissed every LWC caller of the other methods, and could call a UI-facing method test-only. Merging now keeps the full method set on the onecallsApexedge (methods[]), and it does the same for Apex static fields (fields[]). Visualforce and Apex callers go through the same merge and get the same fix. - Aura components that call their Apex controller had no call edge.
controller="X"pluscomponent.get('c.method')in the controller or helper JS now produces acallsApexedge to X listing each method, atheuristicconfidence. A bundle that calls server actions but declares no controller itself (it inherits one throughextends) gets no edge, and the actions are listed on the node asunresolvedServerActions. - Apex reads of Custom Labels (
System.Label.X,Label.X) had no edge to the label. They were stored as a hiddenCustomField:Label.Xphantom, soget_impacton a label returned zero dependents and still reportedcomplete: true. They are nowreferencesedges toCustomLabel:X, and the managedLabel.ns.Xform maps toCustomLabel:ns__X. - Field writes through an indexed receiver were dropped. Writes like
records[i].Field__c = …androws.get(i).Field__c/byId.get(id).Field__con a typedList/array/Mapnow resolve to the element type, so these classes show up as writers. - Lowercase Apex type names made a class's writes disappear.
case cc = obj;andaccount a = new account();are now resolved without regard to case, matched against the vault's object list. On a parsed file, the scanner no longer adds phantom fields named after variables, such asCustomField:cc.Status. The fallback scanner also stops reading a static member of a known Apex class (Constants.STAGE_WON, any case) or a managed-package namespace (ns.Api.call()) as an sObject field: the class read becomes areferencesedge to the class withfields[], and the namespace read is dropped. Lowercase built-ins such assystem.debugno longer produce a call edge to a nonexistentApexClass:system. endpoint_catalogandintegration_mapmarked named credentials as orphaned when they were in use. This happened for a credential that a shared helper builds at runtime as'callout:' + name, or that an OmniStudio Integration Procedure's Rest Action declares. Both tools now share one counter. It addsvia: 'omni-rest'references and, when a dynamic callout exists, references found where the credential's name appears as a literal in Apex source or a custom-metadata record (via: 'name-literal'). Each referrer is listed inreferencedBy. A credential that is still unreferenced carries anorphanedCaveat.find_component_usagesfor a Custom Label counted unrelated identifiers as usage. The search treated any same-named variable as a use and reportedhasStaticEvidence: true. It now matches only label references (Label.X,$Label.X,$Label.c.X,{Label.X},@salesforce/label/c.X), and it also searches formulas, validation rules, Flows, FlexCards, OmniScripts and custom links.- The org-leak scanner passed silently when its blocklist was missing or broken.
scan:leaks, the release guard andsfi vault anonymizeeach had their own loader, and all three treated a missing or malformedforbidden-names.local.jsonas "no patterns" and reported OK. There is now one loader. A malformed file always fails. Strict runs refuse a missing blocklist unless--allow-no-blocklistis passed, every run prints how many patterns it loaded, and CI fails when the blocklist secret is empty (fork PRs run visibly generic-only). The release guard now checks the same patterns as the scanner (it used to read only thepatternskey) and reports a missing blocklist as a clean failure instead of a stack trace. The publish workflow keeps the blocklist untilnpm publishhas run its own leak check, then deletes it. sfi vault anonymizecertified files it never read. Binaries and symlinks in--outwere skipped without being counted, a pre-filled--outwas reported "0 residual matches — safe to share", and the command exited 0 even when the scan found leaks. It now refuses a non-empty--out, reports symlinks inside the vault as skipped, counts unreadable files as findings, and exits 2 with "NOT safe to share" when anything is found.sfi refresh --no-pullcontacted the org. It still ransf sobject describeonce per core standard object. A plain--no-pullnow runs no retrieve and no describe: it replays the describe snapshot the last pulling refresh cached (meta/describe-cache/) and says which objects had none.--with-describeopts back in. The summary says the org was not contacted only when no org-querying opt-in ran;--with-audit-trail,--with-tooling-apiand--with-data-shapestill contact the org and are named when used.sfi.health_checknow reports the vault as degraded and names the objects whose describe-only standard fields are missing, so a "field not found" there is not read as proof the field does not exist.- A mistyped or logged-out org alias reported only "Parsing --target-org". Refresh now checks the alias against your local sf logins before retrieving and fails fast with the fix (
sf org login web --alias …). sf errors keep the cause line printed under the header, andsfi initwarns when the alias is not one of your logins. - Setup steps contacted every org you are logged into.
sfi init, setup-modesfi mcpand the refresh preflight read the local login list (--skip-connection-status, short timeout) instead of checking the connection to every org. The trust statement no longer claimssfi refreshis the only thing that contacts the org; it namessfi refresh,sfi stale-sweep/sfi watchandsfi doctor. - Setup mode gave wrong first-run guidance. It put the first row of
sf org listinto the init command as if you had picked it, suggested pinning the very path it had just failed to find, told a mistyped--vaultto "run sfi init", and claimed the server restarts by itself. It now uses an<your-org-alias>placeholder (naming your sf default org as a hint only), a placeholder pin path, avault-path-not-foundreason for an explicit path that does not exist (its detail and connect-time instructions no longer say to runsfi initor that the vault is not built), names the project directory the refresh must run in, and says a restart is needed. - A refresh that failed before extracting anything printed empty Components/Edges tables above the error. Only the failure line is printed now.
- The Claude Code plugin's slash commands needed a
sfibinary the plugin never installs./sfi-init,/sfi-refresh,/sfi-statusand/sfi-onboardnow checkcommand -v sfiand fall back tonpx -y sf-intelligence@<version>./sfi-initasks which org to use instead of running a baresfi initthat cannot prompt without a terminal./sfi-field-auditno longer suggests--no-pullto raise the report cap (an offline rebuild never fetches reports). The slash-parity and version-consistency checks now fail on a missing fallback or a stale pin. - Onboarding docs contradicted the code and each other.
onboarding.mdsaid a refresh is not picked up by a running server and that the server blocks the refresh; on macOS/Linux the rebuild swaps in behind a live server (Windows still needs the client closed, now stated once).installation.md's Claude Code command lacked--vault, and its "no DX project" row described an error that cannot happen (init scaffolds one).mcp-hosts.mdpinned an old version,examples/demo-questions.mdrecommended a stale committed demo vault, and the README did not mention that the firstsfi demostart can exceed a host's startup timeout. docs/routing.mdanddocs/configuration.mdquoted stale tool counts (217 registered / 212 advertised / core 19 against 231 / 226 / 25). Fixed, andpnpm doc-syncnow fails when those phrases drift from the product manifest.- Website pages scrolled sideways on phones. At 390px every page overflowed by 9px (the header) and
/toolsby about 190px (long tool ids). Tighter phone gutters and wrapping for tool ids and inline code paths fix it without hiding the install button. - 136 harness-bound extractor/parser/renderer tests skipped silently on every machine but a frozen harness copy, CI included. The skip now says loudly that those tests assert nothing.
SFI_HARNESS_ROOT=<dir>runs them from any checkout (a wrong path fails instead of skipping),SFI_REQUIRE_HARNESS=1makes a missing harness a failure, and the walk-up no longer accepts an unrelated ancestortests/fixtures. The three copies of the locator are held identical by a test. sfi quickstartmarked steps done that it never checked. Install and auth were always ticked, the last step was ticked with a pseudo-command, andSFI_VAULTwas ignored. It now runssf --versionand reads your sf logins (checking the vault's own org), never ticks the MCP step it cannot see, prints the exactclaude mcp add … --vault "<path>"line, honours--vault/SFI_VAULT, and seeds starter questions from your own__cobjects (ahead of platform events and custom metadata types) with fields written asObject.Field. A slowsf --versionis no longer reported as "sf not installed".- Flow extraction dropped the values a Flow compares and writes. Decision conditions, record-trigger entry filters and workflow criteria now carry structured
conditionItems(field, resolved field id, operator, value, literal-vs-reference). Get / Update / Delete Records<filters>now mint field-level reads carrying the compared value. Assignment elements that set a field on a record variable the Flow later saves now mint field writes with the assigned value. A condition on a Get Records output or record variable (Get_Project.Stage__c) now resolves to the real field instead of a phantom id. When a Flow writes one field twice, every literal it sets is kept (literalValues), not only the first. - The "only when a record is updated to meet the condition requirements" entry setting was dropped. Flow nodes and their entry condition now carry
entryRequiresRecordChange. what_if_remove_picklist_valuereported "no impacts" for values active Flows depend on. It matched only quoted literals, but Flow and workflow criteria store values unquoted, and it never attributed a condition to its Flow. It now reads the structured conditions and Flow field edges, names each use (where: entry criteria, decision, Get Records filter, literal write), lists record types that merely list the value and Flows that do not run underinformational(they never movecompatibilityorverdict), says when a write of the value would fail on a restricted picklist, and also checks record types, criteria sharing rules, list view filters and Lightning page visibility rules.notCheckednames the families it does not read (reports, path assistants, dependent-picklist matrices, dynamic Apex).value_change_auditreads the same structured literals.- Flow writers were attributed across objects. The shared Flow source scan behind
why_field_changed,field_360,safe_to_delete_fieldandunused_fields_deepmatched a<field>name inside any Create/Update Records element without checking that element's object, so a Flow writingStatus__con a Task was reported as a writer of the Case field. The scan now resolves each element's object (<object>,$Record, typed variable), drops other-object matches, and marks unresolvable onesobjectScope: 'unresolved';find_component_usagesuses it instead of its private copy. why_field_changedwriters came back without the value they write. Each writer now carriesassignedValues(the literal it sets) orassignedFrom(its variable/formula source) andoperation; the gating condition shown is the entry criteria, withonlyWhenChangedToMeetwhen the Flow fires only on the save that changes the record. A new optionalvalueinput answers "what set it to X?".- Save order listed async and scheduled-only Flows as running in the save.
order_of_executionandwhat_happens_on_saveeach copied a rule that recognised scheduled-only Flows only by<pathType>, which a time-offset scheduled path does not carry, and read a vault withouthasImmediateConnectoras "immediate". Both now use one classifier (soe-flow-timing.ts) fed by a newscheduledPathCount; Flow steps carrytiming(async-only, orunknownon an older vault), their declaredtriggerOrder, andonlyWhenChangedToMeet. - Save order counted inactive automations without naming them.
what_happens_on_saveandorder_of_executionsaid "3 inactive automations are left out" but not which, so a host could not tell the user which Draft / Obsolete Flows or inactive rules look relevant but do not run.inactiveSummary.namesnow lists them (Type:apiName (reason), capped at 25, withnamesTruncated). - A Flow writing one field from a literal and from a variable lost one of them. The duplicate-edge merge kept only the first write's kind: when the variable write came first the literal vanished (so
what_if_remove_picklist_valuemissed it), and when the literal came first the writer read as literal-only (sowhy_field_changedwithvaluedropped it). Merged write edges now keep every literal (literalValues) and every variable source (referenceValues). what_if_remove_picklist_valuemissed Lightning pages that use the value. It read only pages already linked to the field by an edge, but neither a{!Record.Field}visibility rule nor a related-list filter creates one. It now reads every Lightning page, skips visibility rules on pages bound to another object, and counts related-listadminFiltersonly when the list is a child relationship of the field's object.what_if_remove_picklist_valuemissed values tested inside Flow formula resources. AnISPICKVAL({!$Record.Field__c}, 'X')in a<formulas>resource carries no edge to the field, so the Flow was left out while the disclosure said Flows were checked. Flow nodes now carryformulaValueRefs(each formula's resolved fields and literals) andformulaComparisons(direct field-to-literal comparisons) and the tool reads them; a vault built before this is named innotChecked, as are screen-component visibility rules and text templates.what_if_remove_picklist_valuecould saysafewhilenotCheckednamed families it never read. An empty scan now returnsreview.- One too-deeply-nested Flow or Apex property could abort the whole vault render. The Flow and Apex markdown renderers serialized node properties without the depth guard the generic component renderer already used; they now share it, so such a value is JSON-encoded in the frontmatter instead of failing the refresh.
- An unrecognized
SFI_TOOL_PROFILEvalue (minimal,lean, a typo) no longer silently selects the full ~760 KB tool roster; it warns on stderr and usescore. Onlyfullselects the full roster. - Tool calls no longer silently drop arguments a tool does not declare. A guessed sibling name is mapped onto the tool's real argument when unambiguous (
object/objectName→objectApiName,componentId↔nodeId/targetId/rootId, singularpermissionSetId→permissionSetIds, …); anything still unused is reported underargumentNoteson the response (or named in the error) instead of yielding a confident unscoped answer. - Every
invalid-queryargument error now names the tool's required and optional arguments, a one-line example call, and points atsfi.resolvefor canonical ids. - The router no longer recommends four retired hidden-alias tools that are not invocable under the core profile (
cdc_subscribers,field_cleanup_candidates,churn,find_apex_usages); each intent now names its surviving tool. layout_for_userrouting no longer emits hard-coded, org-specific profile ids (one of which exists in no org). Only the platform-standardProfile:Adminis emitted; any other " profile" phrase is passed as the tool'sprofileNameselector.sfi.route_questionnow binds the component it already resolved into every recommended call on the first turn, under each tool's own declared argument (fieldId,componentId,objectApiName,triggerId,rootId,classApiName, …, derived from the tool's registered input schema). Previouslyinvoke/candidates carried empty args and most first calls failedinvalid-query. Candidates whose required args could not be bound now say so inmissingArgs;invokeno longer contains a non-executablesfi.resolve {}step.- A label-named object binds its API name (
Invoice→Invoice__c), and a prose word scraped as an object (figure,same) is dropped and disclosed instead of passed asobjectApiName. Class.methodreferences resolve the Apex class and bind the method instead of raising a false "no component named … exists" premise check.- Save questions phrased "saved" / "inserted or updated" route with
event: 'upsert'(insert + update) instead of update only. - Shortlist hygiene: a stacked complement (e.g.
sfi.interpret) no longer outranks a high-confidence route's own primary tool; live-only tools sit below every vault tool when the live plane is off; hidden retired tools are never offered; entity evidence lists an exact winner first, then by score. sfi.resolve: trailing type nouns (label,custom label,class,checkbox,picklist,record(s)) are treated as type hints, so an exact API name followed by its type word resolvesexactinstead ofambiguous; a query equal to a component's multi-word label is a whole-name match. A trailing word is only stripped when the unstripped words do not literally name a component, so " Record field" keeps resolving to the field labelled " Record" rather than a sibling labelled ""; runner-up rows next to a literal name match reportsubstring, notexact.sfi.describe_analysis's default summary now includes a compactargssignature (every arg with its type,?for optional, and a short hint), so one describe call is enough for a correct first call.sfi.list_analysesaccepts aqueryfilter (every word must appear in the name or summary) and echoes it asappliedQuery; previously the argument was silently dropped and the whole roster returned.- Object-access questions ("who can see the X object") whose entity resolves to an object now route to
who_can_access_object/object_access_auditinstead of the field-onlyfield_access_audit, which required afieldIdthe question never had. - Specific what-if questions are no longer swallowed by the generic impact route: "remove 'X' from the Y picklist" routes to
what_if_remove_picklist_valueand "change X from currency to number" towhat_if_change_field_type. The quoted picklist value and the stated target type are bound intovalue/newType(derived from the tool's schema; left unbound when not exactly one), and "the Y picklist on Z" / "the Y checkbox" now resolve as a field. sfi.resolve: a type noun before "on " ("Status picklist on Case") is a type hint, so the field resolvesexactinstead ofambiguous.- "What changed since the last refresh" now also routes to
diff_snapshots(named added/removed/modified components), and the no-argwhat_changed_since_refreshranks abovechanged_since, which needs asincedate. - A "what does Class.method do?" question that matches no rule now still offers the tools that take a method (
explain_apex_method,apex_structure,call_graph, ...), bound to the resolved class and method, at low confidence, instead of an empty shortlist. - A guessed arg renamed onto a typed id (
fieldApiName: 'Contact.Birthdate'→fieldId) now gains its canonical prefix (CustomField:), and aninvalid-querythat follows a rename names the rename, so the error never blames an argument the caller did not pass. - A quoted literal in the question binds only a tool's REQUIRED
valueargument, never an optional filter or a write-side annotation value. sfi.route_questioninvokesteps whose required args could not be bound now carrymissingArgsinstead of posing as executable; an unroutedClass.methodquestion'sinvokeis the bound method tools rather than the generic fallback; and an object-access question no longer offers the field-onlyfield_access_audit(unscoped) back through the shortlist.- A vault built by an older sf-intelligence was served silently. Only
safe_to_delete_fieldcompared the vault's builder version with the running one, soget_impactandfind_component_usagescould reportsoundness.complete: trueon a vault whose builder predates whole edge families (for example OmniStudio callers of Apex, or this release's method-level LWC/Aura caller and Apex Custom Label edges). Every tool response now goes through one shared freshness assessment: on builder driftvaultState.freshnessnames both versions and the edge families added since,trust.completenessdrops fromcompletetopartial,soundnessgains astale-builderblind spot, and the warning leadstrust.limitations. A vault older than a week is flagged by age band (>7d,>30d,>90d). An emptytrust.freshness(asroute_questionreturned) now names the snapshot time. health_checkreporteddegradedon every vault, including the official demo. Coverage gaps (metadata families the org does not have, or the refresh did not confirm, report pulls capped by design, and unrecognised source directories) are now listed in a newcoverageGapsfield and no longer changestatus, which reflects wiring and integrity only. A retrieve that errored or never finished is a refresh failure, not a gap: it stays inissuesand keepsstatusatdegraded. Absence claims are still hedged by each tool's coverage caveat.health_checkandcoverage_reportdisagreed about families the vault's own edges reference but which hold no components.coverage_reportlisted such a family as partial whilehealth_check,coverage_report.summaryand every coverage caveat called it covered. The fact is now computed once when the server binds the vault and folded into the shared coverage summary, so every consumer reads the same verdict.safe_to_delete_field(and the other field-deletion gates) now also require EmailTemplate coverage, since merge fields reference fields; an unread template plane used to be left out ofmissingCoverage.get_impact,find_component_usagesandwhat_if_change_method_signatureclaimed completeness for types whose referrers are only partly modeled. A custom label used in formula fields, or an@AuraEnabledmethod called from an Aura bundle with no declared controller, came back ascomplete: truewith no blind spots. One referrer-coverage table per component type now says which referrer kinds are graph edges, text-search only, or not modeled.get_impactnames the unmodeled kinds as anunwalked-referrer-classblind spot,find_component_usagesreturns them inreferrerCoverage(withnotSearchedfor the kinds its text search does not read either), andwhat_if_change_method_signaturelists them intrust.limitationsand reportsreviewinstead ofsafewhen an@AuraEnabledmethod shows no callers. The field and object blind-spot list is now derived from the same table. Kinds that only newer builders emit as edges (method-level Aura callers, Apex Custom Label references) are judged by the vault's own builder version, so a vault built before them is not credited with edges it does not hold.- The
conceptReasoningblock showed 0 claims on most hub components while costing 4-6 KB. Claims on a standard object run 1.5-3.6 KB each, and the fit dropped claims (15 to 0) around a fixed block of prose. The fit now samples each claim's citation list (true count ingroundedInTotal), compacts the prose and shortens long claim texts before it drops a claim, so three to five claims survive where none did. A component where no rule fired gets a compact block that still carries every count and the not-checked warning, plus a pointer tosfi.interpret. sfi.interpretreturnedoversizeon objects and profiles. It serialized every claim three times with full citation lists (about 160-210 KB on a standard object), so the surface every concept-reasoning disclosure points to failed on the most common anchors. Claims are now paged (limit, default 10, andoffset, withpage.nextOffset), each claim's citations are sampled bygroundedInLimit(default 25, full count ingroundedInTotal), and the handler fits the page to the response budget itself. It samples the completeness lists and citations before it shrinks the page.safe_to_delete_field's stale-vault caveat named the wrong edge families. It always said the 0.3.0 families were missing, which is false for a vault built by 0.3.0 or later, and never named what such a vault does lack. It now lists exactly the families added after the vault's builder, from the same table every other response uses.sfi.interpretwith anoffsetpast the last claim said "No concept rule fired". The rendered answer and the evidence envelope now say the page is past the last claim and how many fired, and a partial page'srenderedtext names the window it shows.- Unreadable files turned into definitive answers. On a vault older than the flow async-path markers,
explain_flowtreated a flow source it could not read as "no AsyncAfterCommit path" and declared that an unhandled fault rolls back the triggering save. It now returnsrollsBackTransaction: nullwith a statement saying why. The same flow's non-Apex actions are disclosed as not checked instead of being left out.persona_unused_grantsnow counts reachable Apex files it could not read intrust.limitationsand marks completenesspartial, where it used to skip them silently. - Cross-vault comparisons read a malformed component row as "no properties" without a trace. Seven tools and
sfi snapshoteach carried a private copy of theproperties_jsonparser that swallowed the error. They now use the graph's parser, which logs a warning naming the row. - A field used only as a report filter was invisible to delete-safety. A Report names the fields it filters and sorts on in
<criteriaItems><column>and<sortColumn>, which the report sweep never read, sosafe_to_delete_fieldcalled reports "unchecked" for a report the vault held. Filter and sort columns now mint edges (cross-filter columns, which name fields on a related object, are skipped rather than guessed). - DataMapper Extract formulas now count as readers. A formula row such as
IF(alias:Field__c == false, …)reads the field through the same alias as the mapping rows; those reads were dropped. - An LWC
@salesforce/schemaimport is now a declared reference. It was graded heuristic like an in-body string match, so a compiler-checked import read as "may be a false positive". - Standard lookups now point at their target. The Metadata API ships
Contact.AccountId,Opportunity.AccountId,Case.ParentIdand similar with no<referenceTo>, so the data model had no edge into Account. A curated, platform-fixed table fills the target when the XML names none (markedreferenceToSource: standard-relationship-table); unlisted fields are never guessed. safe_to_delete_fieldtiers were reversed. A parsed Apex reference (which Salesforce refuses to delete past) was onlyriskywhile an Obsolete Flow was "will break at runtime". Parsed Apex and LWC schema imports are nowblocking; heuristic-only matches stayrisky, and so does a field named only inside a SOQL string literal (e.g. a constant handed toDatabase.query): the compiler does not check strings, so the delete succeeds and the query fails at runtime (such edges carrymechanism: soql-string-literal); every example carries the referrer'sstatus, and an inactive blocker (Obsolete Flow version, inactive rule) is disclosed as "does not run, but must be deleted first".- OmniStudio referrers had no category and landed in
unknown. They are nowomnistudio: a running DataMapper / Integration Procedure / OmniScript / FlexCard isblocking(breaks at runtime), one that does not run isreview. A DataMapper's own active flag is not used for this (orgs run DataMappers flagged inactive from active Integration Procedures): it runs when any caller is active. - An OmniStudio delete referrer names its callers. A DataMapper that reads the field is usually called by an Integration Procedure or OmniScript, which breaks with it; each
omnistudioexample now carriescalledBy(the components that dispatch it, active ones first) andcallers(how many there are and how many are active). - A class that both reads and writes a field was counted twice in
safe_to_delete_fieldand spent two example slots on itself. One referrer is one row. - Custom labels used by formulas and FlexCards had no referrers. A formula's (or validation rule's)
$Label.Xand a FlexCard's{Label.X}merge token now mintreferencesedges to the label, so "where is this label used" andget_impactno longer report zero with complete coverage. - A validation rule's error display field is now a dependency. A rule that shows its error on a field (
<errorDisplayField>) depends on it even when the formula never reads it; that edge was never minted, sosafe_to_delete_fieldmissed it. - A capped report pull no longer reads as "reports not checked". The default report retrieve is capped to the most-used reports;
safe_to_delete_fieldcalled the whole analytics categorynot-checkedalthough it had checked every report it retrieved. It is nowpartially-checked, withretrievedOfgiving how many reports and dashboards the vault holds (and so were checked) out of the org total. - A workflow field update fired by a time trigger was called "never fires". Only a rule's immediate actions were read, so an update named only inside
<workflowTimeTriggers>was listed as unreferenced andwhy_field_changed/safe_to_delete_fieldsaid it never runs. Time-trigger field updates now mint the same writer edges as immediate ones, markedtimeTriggered. - A condition row now carries its firer's status in
safe_to_delete_field, so a decision inside an Obsolete Flow is disclosed as not running. who_can_access_objectmade the host build "who can edit / delete" by hand. It returned one row per capability per principal (40-80 rows on a real object), interleaved across kinds, with no filter; a Modify All holder appeared up to six times. The defaultview: 'principals'now returns one row per principal with its effectivecapabilities(Modify All and Modify All Data imply Edit and Delete),recordSharingandscope, and the newaccessLevelandprincipalTypeinputs filter it ("which permission sets can delete X" is one call); aprincipalTypethat is never a granter kind (for example a permission set group, whose access arrives through its member sets) is rejected with the valid kinds instead of returning an empty list. WithaccessLevel,summary.sharingOnlyPrincipalscounts roles and groups that match only through record sharing and hold no object permission themselves.view: 'paths'keeps the per-capability rows. Profile and permission set rows now carry the licenceaudience(internal, external, guest, unknown), and principals with an external or guest licence that reach every record are called out.field_access_auditcounted a read-only profile as able to edit. Its headline counts and each grant'spermissioncame from field-level security alone, so a profile with FLS Edit but object Read (or no object row at all) was listed asedit. Each grant'spermissionis now the effective level for that container (FLS, object permission on the parent, and field type together), withflsPermissionfor the declared level and anotesaying why they differ (unconfirmedwhen the vault has no object row).summary.profilesandsummary.permissionSetsare disjoint effective counts; the declared FLS counts move tosummary.declaredFls.permissionTypefilters on the same effective level, sopermissionType: 'edit'no longer lists a read-only profile.permission_risk_reportignored who holds a grant. A permission set licensed to external community users with Modify All on an object ranked below internal admin profiles. Findings now carry the holderaudiencefrom the container's licence; View All or Modify All held through an external or guest licence iscriticaland ranks first within its severity. A permission set group takes the audience of its risky member sets.object_360said the external org-wide default is never extracted. It returned a hard-coded "not extracted" note while the object node carriedexternalSharingModelandwho_can_access_objectreported it. It now reports the extracted value; anullsays whether the vault predates the extraction or the XML declares none.generate_sharing_summaryspent its 50-object cap on types with no sharing model and dropped lowercase-namespaced objects. Custom metadata, platform event, external and big object types (shown as "OWD: Unknown") are now skipped with a boundary naming how many, objects with sharing rules come first, and names sort case-insensitively, so namespaced objects such asns__Application__care no longer cut silently. Naming one of the skipped types withobjectFilterstill answers it.effective_permissionsleft out page and tab access and reported unchecked record types as 0. It now returns the Visualforce pages and visible tabs the containers grant (with counts insummary), andsummary.recordTypeVisibilities/summary.visualforcePages/summary.tabsarenull, not 0, when no container carries that data, with a disclosure naming the containers built before it was extracted. The newperContainer: trueinput returns each container's own contribution (narrowed to the asked object) and how it was reached (directly or through which permission set group), so "does this group add delete?" no longer needs a call per group.layout_for_userpicked the Lightning record page by an alphabetical name guess. The vault already held the activation metadata (the object's org default, each app's default, and app + record type + profile assignments) but no extractor read it. The CustomObject and CustomApplication extractors now capture it asrecordPageOverrides, andlayout_for_userresolves the page in the platform's order, returningrecordPageActivationwith the org default, one row per app that overrides it (matchedOn), and the apps where the page depends on the record type. When no record type is passed and the profile's default record type picks an app's page, that row names it (assumedRecordType) and the app is listed independsOnRecordType. A vault refreshed before this falls back to the name pick, now markedfallbackinstead ofmatched.guest_exposure_reportnever ranked the Visualforce pages a guest user can load. It counted the guest profile's page grants and still reported the whole page plane as unchecked. Each page is now avisualforce-pagefinding rated by the controller and extension Apex it runs (pageControllers, read from the page's declared controller and extension references). The unchecked-surface row and limitation remain only for a guest profile built before page grants were extracted.- Save order stopped at the trigger dispatcher. A handler-pattern trigger (
Dispatcher.run(new XHandler())) showed only "references XHandler / calls Dispatcher" and no field writes.what_happens_on_saveandorder_of_executionnow follow the trigger into the Apex it calls (up to 3 hops) and list the field writes found there, each markedviathe class that performs them. Both tools share one module, so they cannot drift. - A custom-metadata switch that turns a trigger off was invisible. When the trigger's handler chain reads a bypass-style custom metadata type or custom setting, the trigger step now names it with this object's record and the flags it sets, and a top-level
triggerBypassWarningsline appears when a bypass flag is set. Whether the Apex honours the flag is disclosed as not evaluated. Custom-setting values are not in the vault, and the response says so. A record whose TRUE flags are not bypass-named (per-context flags such asBefore_Update__c) is reported asflags-set-not-evaluatedwith its own warning line, and a record whose values were never extracted readsvalues-not-in-vault, never "no bypass flag". order_of_executionandwhat_happens_on_savedropped triggers, after-save flows and duplicate rules behind a long run of validation rules. When the byte budget has to drop steps from an unpaged view, it now sheds the most crowded phase first (never below 3 steps) before it touches the tail, and names the shortfall inphasesOmitted.what_happens_on_saveused to hand the oversize payload to the global response guard, which cut the tail; on a real Contact it returned 30 of 60 steps with no duplicate rule, after-trigger, after-save flow or async step, and now returns 53 with only 7 validation rules held back. A pagedorder_of_executionview, and aphase-filteredwhat_happens_on_savecall, keep their earlier behaviour.- The test-coverage tools contradicted each other and missed how tests really run code.
apex_test_coverageread onlycallsApexout of each test,tests_for_changewalked calls and async dispatch, andtest_coverage_gapswalked every usage edge, so one class was untested in one tool and covered in another. None of them credited a test whose DML fires a trigger that calls the handler, sotests_for_changeselected zero tests for a trigger-handler change. The three tools (and the trigger join intest_coverage_for_method) now share one walk: calls, async dispatch, references and inheritance from Apex within 3 hops, with tests as sinks, plus a trigger hop for a test that writes or constructs a record of an object whose trigger reaches the class. Trigger-hop credit is markedvia: via-triggerand is heuristic. A test whose own source shows DML but none of the trigger's events (onlyinsertagainst an update-only trigger) is still credited but markedeventMismatch, because code it calls can fire the trigger. Org-wideapex_test_coveragereportssummary.classesCoveredOnlyViaTriggerand a boundary when any class is covered only that way. On a real vault, the untested count went from 59 to 10, and it now matchestest_coverage_gaps.review_changereads the walked edge set from the same module, so a test reached throughnew X()is now a selected test rather than an "unchecked referrer"; a test reached only over an edge the walk does not follow (e.g.dependsOnFromApi), or a referrer with no extracted test flag, still makes the rowunknown. find_dead_codecalled installed managed-package fieldsdefinitely_dead. A namespaced component (ns__Field__c) cannot be deleted from the org, and the package code that uses it is never in the vault. It is nowuncertainwith that reason, so an unscoped dead-code listing no longer leads with package fields.- The fake-assertion check flagged the standard expected-exception test.
System.assert(true, ...)inside thecatchof a try/catch whosetryexpects a throw acknowledges the exception the test is checking for; it is no longer counted as a tautology.assert(true)outside a catch is still flagged. - The trigger recursion-guard check fired on almost every trigger. A static flag or static set held on a helper class (
if (Flags.runOnce) { Flags.runOnce = false; ... },Flags.seen.contains(id)) now counts as a guard. A trigger whose whole body is one delegating call (a handler dispatcher or a managed-package framework) is no longer flagged, because any guard lives in the class it delegates to, which this per-file check cannot see. org_risk_reportled every vault with a false "critical: retrieve failed". The finding listed every partial coverage type as failed, but most were still pending, capped, or requested and returned nothing. A coverage gap is now a caveat on the report, never an org risk (mediumwhen a retrieve actually errored,lowotherwise). Its wording separates errored, pending/capped and unconfirmed-empty types, and thegate: trueblocker fires only on an errored retrieve.soql-injectioncalled every concatenated querycritical. The rule now traces where each concatenated value comes from. It stayscriticalonly when the value comes from a method parameter or a Visualforce page parameter. An untraced value (class member, method call) ishigh, a value read only from custom metadata or custom settings isinfo, and a query built only from literals (including ternaries andString.joinover literal lists) or fromId/number/date parameters is no longer flagged.without sharingjustified in the class doc comment was still flagged. A class doc comment of any length (annotations may sit between it and the declaration) or a trailing comment on the declaration line now counts as the justification.tech_debt_scorebanded a two-axis score as org-widecritical-debtand reported a delta against a different method. When less than half the applicable axis weight is scored,scoreBandis nowinsufficient-evidence(andorg_risk_reportranks itlow), and the response listsscoredAxesandscoredWeightFraction. Refresh now logs the axis set and score-model version with each score.scoreDeltais reported only against a prior score from the same model over the same axes; otherwisescoreDeltaUnavailablesays why.endpoint_catalogcounted Lightning controllers as inbound APIs and left out Apex callouts.inboundApisnow holds only REST/SOAP entry points.@AuraEnabledand invocable classes are listed underuiEntryPointsand are not counted intotalEndpoints.org_risk_reportleft out guest-user exposure and ranked Salesforce's standard profiles as critical. Guest exposure is now one ranked finding at the worst guest severity, citing the top nodes. A standard profile (<custom>false</custom>) that carries god-mode permissions by design is capped atmediumand labelled "Standard Profile", so custom grantors of the same permissions rank above it. This also applies inpermission_risk_report. The guest-exposure finding's evidence lists each node once.- Three tools gave three answers for a field used only as a report-type column.
unused_fields_deephid such a field as "used". It is now listed at confidencemediumat most, itsrecommendedActionstarts withREPORT-TYPE COLUMN ONLY, and a boundary gives the count. A Flow write still holds a field out of the list.safe_to_delete_fieldnow returnsreviewBecausewhen it gives areviewverdict with emptyreasoning, and names the coverage gap, the older builder or the live population that caused it.safe_to_delete_fieldandfield_360now read the same report-type scan asunused_fields_deep: both returnreportTypeColumns,safe_to_delete_fieldnever calls such a fieldsafe, andfield_360raises its risk fromlowtomedium. When the report-type scan failed or read only some report types, both tools say so, andsafe_to_delete_fieldgivesreviewinstead ofsafe. - A change to only a code file's
-meta.xmlsidecar (an API-version bump) was dropped from a diff review. It now maps to its class, trigger or page. - An api name with the wrong case was reported as not in the vault. It is now corrected to the vault's casing, but only on an exact case-insensitive match within the same type. A bare nested name completed to the one object that has it (
Field__ctoObj.Field__c) is counted separately asqualified. sfi review-change --diffreviewed a rename as a change to the new file only, so the removed class and its dependents never appeared. It now reviews the old component as deleted and the new one as added, and both--diffand--manifestname container files and unmodelled metadata as not reviewed instead of mapping them to ids that do not exist.order_of_executiondropped record-triggered flows that had norecordTriggerType. It had its own copy of the save-event matchers, and that copy had drifted fromwhat_happens_on_save's: it skipped such a flow on every event, whilewhat_happens_on_savetreats it as the platform default,CreateAndUpdate. Both tools now use one shared module,soe-event-match.ts.sfi.generate_onboarding_docsilently ignored an object scope. Its schema was not strict, so{ "objectApiName": "Case" }was dropped and the org-wide tour came back as if it answered the object question. The tool now refuses unknown arguments and namessfi.object_360withformat: "handbook"; its description says it is org-wide.safe_to_delete_fieldread thesharingcategory as "checked, none" for a field that sharing rules test. Sharing-rule criteria and restriction / scoping rule filters now reference the fields they test, so such a field is a blockingsharingreferrer. A filter that walks a lookup (Advisor__r.Region__c = $User.Id) now references the field it ends on, on the related object, as well as the lookup. When the vault cannot resolve such a path, a field with the name it ends on readssharing: not-checkedand neversafe. On a vault built before this release the row readsnot-checked. Re-runsfi refreshto get the new references.- A time-triggered workflow field update was treated as a same-save write.
automation_collisionsreported a high-severity same-save collision with a before-save Flow, andwhat_happens_on_save/order_of_executionlisted the update as a save-time action. The update runs later in its own transaction. It is now left out of collisions and shown asschedulesTimeTriggeredWrite. health_checkreporteddegraded("retrieve failed, re-run refresh") on every vault with no report pull, includingsfi demo,--no-reportsand--no-pull. Report and Dashboard rows start as pending by design. They now count as a failed retrieve only when a pull was attempted.field_access_auditclaimed a denial it had not checked. Its "N containers declare FLS Edit but cannot edit" count included grants whose object access was never checked (on a real vault, 38 instead of 15). It now counts only verified downgrades.layout_for_usersaid "no record page is activated" for an object whose own definition the vault does not hold. The org default record page is now reported as NOT CHECKED, and the page picked by name is labelled as a guess.field_360andsafe_to_delete_fieldmissed report-type columns reached through a relationship path. When such a column has the same name as the field, the field is no longer rated low risk or certified safe, and its analytics row no longer readsnone-found.apex_structuredropped the omitted-sharing finding for a Visualforce@RemoteActioncontroller.@RemoteActionis now an entry point, and the catalog finding is kept unless the parsed check reports the same rule.sfi mcp --vault <project folder>booted setup mode, saying no vault was built. It now accepts the folder that holdsorg-kb, like every other command. The setup-mode redirect also states the actual reason (for example a mistyped path), not "no knowledge base yet"./sfi-refreshtold the agent to stop on every non-scratch org.--skip-connection-statusnever reportsConnected, so the pre-flight now checks only that the alias is in the local login list. The skill agrees.sfi watchandrefresh --componentslost standard fields after a demand retrieve. The re-extract after the retrieve now runs the standard-field describe live.effective_permissionsno longer says tab visibility is outside the permission union it returns, in its response or its tool description./sfi-onboardno longer asks for a "connected" org after listing orgs with--skip-connection-status, which never reports one.order_of_executiondropped record-triggered flows that have norecordTriggerType. Its stale copy of the event matcher had missed the fix thatwhat_happens_on_savealready had.- The recursion-guard detector missed a toggled static Boolean when the
iftest used a different letter case from the declaration. Apex identifiers are case-insensitive. sfi.get_impactno longer tells the host to check that an id exists first. Its description and long-form reference said an unknown id returns the same empty slice as "nothing depends on it"; the tool already refuses an unknown id withcomponent-not-found. Both now say so, and say that a phantom id (referenced but never retrieved) still answers but is absent fromimpact.nodes, with lost edges counted indroppedEndpointEdges.sfi.safe_to_delete_fieldandsfi.field_access_auditsay which part offieldIdis case-insensitive. TheObject.Fieldpart is; theCustomField:prefix is not.- Server instructions rule 7 says live data can also be enabled by the operator, not only by a
sfi.live_consentgrant. - Workflow and approval-process field updates now carry the value they write (literal, lookup, formula, blank, next/previous) on their
writesToedge; before, the edge said onlyLiteral. - A component that writes one field in several places (an approval process's submit / approve / reject / recall updates, a Flow's create and update, a rule's immediate and time-triggered updates) kept only its first value in the graph; every value is now folded into the stored edge (cold import and incremental refresh), keeping which values a time trigger writes (
partlyTimeTriggered,timeTriggeredValues,immediateValues). Edges that state no value are left unmerged. - Field updates run by an approval step's own approve / reject actions emitted no edge, so those writers were missing and the update could read as "nothing fires it". They are now writers (
hookType: stepApproval/stepRejection). what_if_remove_picklist_valuenow also finds workflow / approval updates that set the value (vault rebuilt by this version), and shares its value-set check withwhy_field_changed.endpoint_catalogreads a computed Apex callout endpoint instead of stopping at "dynamic". String constants (same class orOtherClass.NAME) are followed, and each runtime part is attributed to its custom metadata type and field, custom label or custom setting, with the values the vault holds for it (apexCallouts[].resolution). A literal or constant prefix that names a credential or host followed by a runtime part is reported aspartially-resolvedwith that credential or host. When nothing shows where the name ends ('callout:My_API' + path,'https://api.vendor.com' + path), the name is still reported, flaggednameMayContinue, and such a host stays insummary.unauthorizedCalloutHostswith aboundaries[]note. A distinct record value held by several records lists all of them (alsoFrom). An endpoint built only from constants resolves tonamed-credential/literal-host. A'callout:' + <record field>endpoint lists the credentials its record values name asvault-recordcandidates.'https://api.' + xno longer reports the hostapi..pnpm publish --dry-run(andnpm publish --dry-run) inpackages/clino longer aborts in the prepublish hook with "found 0 .tgz": the pack-allowlist check's ownnpm packnow ignores an inheritednpm_config_dry_run, so a release can be rehearsed end to end. The allowlist check itself is unchanged.
Verification scope
Windows: partially verified. The hard-gated tier (core, tooling-api, renderers, parsers, patterns, vault, extractors) passed. Advisory tiers were NOT green: WIN-1=failure, WIN-2=failure — those suites did not report a pass on Windows for this build and were not allowed to block it. See CI run https://github.com/PranavNagrecha/Salesforce-Intelligence/actions/runs/38083381223.
CI run: https://github.com/PranavNagrecha/Salesforce-Intelligence/actions/runs/38083381223