Under the hood
Artifact creation now passes a request ID through, and auto-opening after first write has an extra gate
What
When the Artifacts tool creates a new artifact from a type, the call that builds the artifact page now also passes along a request ID and an additional parameter that weren't included before. Separately, the path that automatically opens an artifact after its first write is now gated by an additional check before it will open.
Why
Threading a request ID through artifact creation likely helps associate the creation with the request that triggered it. The added gate on auto-opening means the artifact won't necessarily pop open automatically in every case it used to.
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
What the extra parameter and the new auto-open gate condition specifically check is not stated in the finding.