RMD Documents with params set do not create the `params` object when run interactively

System details:

Positron and OS details:

Positron Version: 2024.08.0 (system setup) build 31
Code - OSS Version: 1.91.0
Commit: 7ee0596b81d578059e63c9af7c535c6b6040b947
Date: 2024-08-10T13:58:22.910Z
Electron: 29.4.0
Chromium: 122.0.6261.156
Node.js: 20.9.0
V8: 12.2.281.27-electron.0
OS: Windows_NT x64 10.0.19045

Interpreter details:

R 4.3.3

Describe the issue:

In RStudio, using ctrl+enter or running a code chunk inside of an RMD file would populate the params R object with the default params set in the YAML..
In Positron, the params object is not created when running code or code chunks interactively from the RMD file. This issue prevents manually running / testing parametric reports; the whole report must be rendered with defined params each time.

Steps to reproduce the issue:

1. Create RMD file and define params in the YAML
2. Create an R code chunk that references the params object, and manually run the code chunk
3. Error: ! object 'params' not found

Expected or desired behavior:

The desired behavior is for Positron to populate the params object for RMD files as RStudio, so RMD files can be tested / iterated on when they are parameterized.

Were there any error messages in the UI, Output panel, or Developer Tools console?

Error:
! object 'params' not found

Reproduce the issue with an RMD file containing YAML params and an interactive R code chunk that references params, using the reported Positron and R versions if available. Trace the interactive RMD execution path and compare it with the stated RStudio behavior; done means the params object is populated from the YAML defaults and the chunk no longer reports object 'params' not found.