docs: refresh publishing and app delivery guidance - #491

What this changes

• Updates scheduling instructions to use the current Run and Save schedule labels and documents enabling the schedule before configuring it.
• Replaces the scheduling screenshots with current high-resolution WebP captures.
• Updates the PDF export instruction to use the current Export as ... label.
• Updates the project export route to use Export as ... and Project as .zip.
• Points Streamlit file uploads to the Files panel in the right sidebar and removes stale screenshots that show the former layout or obsolete controls.
• Updates Streamlit app status labels to Awake, Waking up, and Going to sleep.
• Replaces outdated Streamlit limitation text with the observed AI panel, file upload support, and Record screen menu entry.

Pages checked

• Creating apps
• Scheduling
• Export a PDF
• Export a project
• Streamlit apps

Linear ticket is not filed yet. See the local run artifact for the prepared ticket text and add Closes <ID> after filing it.

Why

The documentation audit executed the linked pages against the real product and found reproducible differences.

Finding 1: cosmetic

Click the calendar icon Schedule notebook, which is at the top of the notebook, right next to the Run notebook button

• Documented: The scheduling control is next to a Run notebook button.
• Actual: The current toolbar uses Run.
• Reproduced: Yes. The scheduling control and current Run label were observed in the live notebook toolbar.
• Correction: Changed the instruction to refer to the current Run label.

Finding 2: misleading

Configure the frequency at which you would like the notebook to run and then click Save.

• Documented: Frequency and Save are ready after opening the scheduling dialog.
• Actual: The Schedule notebook switch must be enabled before the frequency controls and Save schedule become available.
• Reproduced: Yes. The dialog was opened with scheduling disabled, then enabled and saved successfully.
• Correction: Added the enable step and changed the action to Save schedule.

Finding 3: cosmetic

Additionally, you can also configure notifications for successful and failed runs, either by email or into Slack.

• Documented: The notification controls are illustrated by the page screenshot.
• Actual: The current scheduling dialog includes the notification controls plus repeated-failure controls and current recipient fields.
• Reproduced: Yes. The current dialog was opened and its notification controls were inspected.
• Correction: Replaced the old screenshot with a current WebP capture.

Finding 4: cosmetic

Every run automatically creates a run snapshot — an immutable record of the notebook's state after execution.

• Documented: The page screenshot illustrates the version-history entry created by a scheduled run.
• Actual: The current version-history panel shows a scheduled-run entry with the notebook context and duration.
• Reproduced: Yes. A scheduled run completed and its current version-history entry was observed.
• Correction: Replaced the old screenshot with a current WebP capture.

Finding 5: major

Scheduled notebooks can use integrations that rely on federated (OAuth) authentication, such as Snowflake and BigQuery OAuth. Scheduled runs authenticate using the OAuth tokens of the user who set up the schedule.

• Documented: Snowflake and BigQuery OAuth integrations can be used by scheduled notebooks.
• Actual: Production BigQuery OAuth scheduled execution succeeded. Snowflake OAuth scheduled execution was not independently exercised because no account with the required provider access was available.
• Reproduced: BigQuery was reproduced successfully. Snowflake remains unverified under the user-authorized exception.
• Correction: No source correction was made to the Snowflake portion while the required account access was unavailable.

Finding 6: cosmetic

Hover over Export as.

• Documented: The project actions menu uses the label Export as.
• Actual: The current menu uses Export as ....
• Reproduced: Yes. The current menu label was observed while exporting a PDF.
• Correction: Changed the instruction to Export as ....

Finding 7: major

To export a project, click the ellipses (...) to the right of the Share & publish button and then click on Download.

• Documented: The export route uses a Share & publish area followed by Download.
• Actual: The current project toolbar exposes an ellipsis menu, then Export as ..., then Project as .zip.
• Reproduced: Yes. The current project menu and export submenu were observed.
• Correction: Updated the route and current menu labels.

Finding 8: cosmetic

Simply drag and drop your .py file into your project's Files section.

• Documented: The project exposes a Files section for adding a Python file.
• Actual: Files are shown in the Files panel in the right sidebar.
• Reproduced: Yes. A safe Python file was added through the current Files panel and opened successfully.
• Correction: Updated the instruction to name the current Files panel and removed stale illustrations of the former layout.

Finding 9: major

The indicator in the upper left corner of the app preview shows three possible states:

• Documented: The app preview uses Live, Sleeping, and Deploying app states.
• Actual: The observed states were Awake, Waking up, and Going to sleep.
• Reproduced: Yes. All three current status labels were observed during app startup and idle transitions.
• Correction: Updated the status list to the current labels and descriptions.

Finding 10: major

If you prefer to control when updates go live, you can disable automatic updates in the Streamlit settings (hamburger icon, Settings) by turning off the Run on save option.

• Documented: The shared app exposes a Settings control with a Run on save option.
• Actual: The current shared app menu has no Settings or Run on save control, while editor changes were reflected immediately.
• Reproduced: Yes. The menu and immediate update behavior were observed.
• Correction: Removed the obsolete instruction and its contradictory screenshot.

Finding 11: major

The Record a screencast feature is not available

• Documented: The app does not provide a recording feature.
• Actual: The app menu includes Record screen.
• Reproduced: Yes. The current menu entry was observed.
• Correction: Updated the limitation to identify the current Record screen option.

Finding 12: major

AI support for editing Streamlit files is coming soon!

• Documented: AI editing support is not yet available for Streamlit files.
• Actual: The Streamlit file editor includes an AI control and prompt panel.
• Reproduced: Yes. The control and panel were observed without submitting a prompt.
• Correction: Replaced the future-looking limitation with the observed editor behavior.

Finding 13: major

The first time a viewer opens an app that uses an OAuth integration they have not authenticated yet, the helper renders an Authenticate button that opens the same OAuth flow used by notebooks and published apps.

• Documented: An unauthenticated viewer receives an authentication prompt and can then run the OAuth-backed query with their identity.
• Actual: The BigQuery helper returned a permission-denied 403 before an authentication prompt was observed. The Snowflake Azure AD flow opened Microsoft sign-in, but the available account was rejected because it is not an external user in the deepnote.com tenant.
• Reproduced: The failure was observed. Full viewer authentication remains unverified under the user-authorized exception.
• Correction: No source correction was made until an OAuth-enabled viewer account is available.

How this was verified

Every documented step was performed through the real Chrome UI in the approved Deepnote workspace. Only steps that depended on unresolved OAuth account access remain unverified, and those details are reported below.

Opened automatically by the doc-verify skill from the approved GitHub account. Not reviewed by a human.

Unverified by human

This draft uses the user-authorized incomplete-verification exception. The following exact details remain unverified:

• Scheduling: Scheduled execution with the Snowflake OAuth example was not independently exercised because no account with the required provider access is available. No credentials were entered or handled.
• Streamlit apps: Per-viewer OAuth authentication was not fully verified: the BigQuery helper returned a permission-denied 403, and the Snowflake Azure AD flow rejected the available Microsoft account because it is not an external user in the deepnote.com tenant. No credentials were entered or handled.

Summary by CodeRabbit

• Documentation
  • Updated PDF and project export instructions to reflect current menu labels and navigation.
  • Clarified scheduling steps, including calendar access, save actions, and updated visuals.
  • Revised Streamlit setup guidance with current file-panel, deployment, app-state, and supported-feature information.
  • Removed obsolete Streamlit images and outdated instructions.