mainsequence 4.4.27__tar.gz → 4.4.30__tar.gz

{mainsequence-4.4.27 → mainsequence-4.4.30}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: mainsequence
-Version: 4.4.27
+Version: 4.4.30
 Summary: Main Sequence SDK 
 Author-email: Main Sequence GmbH <dev@main-sequence.io>
 License: MainSequence GmbH SDK License Agreement

{mainsequence-4.4.27 → mainsequence-4.4.30}/agent_scaffold/AGENTS.md

@@ -53,7 +53,8 @@ Core responsibilities:
   - for data publishing and data pipelines, use `DataNode`s and `MetaTable`s
   - for serving application or widget-facing surfaces, use `FastAPI`
   - for visualization, confirm the delivery target with the user:
-    - if they want something quick for testing or iteration, use Streamlit
+    - if they want a Streamlit app, treat app design and implementation as project-owned code and
+      use Main Sequence skills only for platform deployment and release verification
     - if they want reusable components and a more structured product surface, use Command Center
   - for scheduled execution, releases, and backend operations, use jobs, images, resources, and
     other platform objects through the proper platform skills
@@ -63,8 +64,8 @@ Core responsibilities:
 - translate user business logic into reusable code under `src/` so it can be reused by APIs,
   dashboards, jobs, and other project components instead of duplicating logic in integration
   layers
-- maintain the repository through the maintenance skills, including project-state reconciliation,
-  journaling, blocker tracking, and bug auditing
+- maintain the repository through explicit `.agents/` project-state files and the bug auditor skill
+  for blocker and SDK/platform issue assessment
 
 Typical outcomes include:
 
@@ -72,11 +73,11 @@ Typical outcomes include:
 - build a `MetaTable` to record operational or application data
 - build a `FastAPI` API that reads project data and returns widget-ready or
   application-ready responses
-- confirm whether a visualization should be a quick Streamlit surface or a reusable Command Center
-  surface before building it
+- confirm whether a visualization should be a project-owned Streamlit app or a reusable Command
+  Center surface before building or deploying it
 - build reusable business logic in `src/` and keep thin integration layers in APIs, jobs, and
   dashboards
-- keep the repository auditable through maintenance, journaling, and bug reporting
+- keep the repository auditable through project-state records, blocker tracking, and bug reporting
 
 Working rules for this role:
 
@@ -204,8 +205,12 @@ Typical routing:
   `.agents/skills/mainsequence/platform_operations/orchestration_and_releases/SKILL.md`
 - RBAC, sharing, constants, secrets, and access verification:
   `.agents/skills/mainsequence/platform_operations/access_control_and_sharing/SKILL.md`
-- dashboards:
-  `.agents/skills/mainsequence/dashboards/streamlit/SKILL.md`
+- Streamlit dashboard deployment and release verification:
+  `.agents/skills/mainsequence/platform_operations/orchestration_and_releases/SKILL.md`
+
+Streamlit dashboard design and implementation are app-owned project work, not a separate Main
+Sequence scaffold skill. Route only deployment of an already-authored Streamlit dashboard to
+orchestration and releases.
 
 ## Mandatory Startup Sequence
 
@@ -246,8 +251,8 @@ Default pattern:
 
 Before the final response:
 
-- consult the maintenance skill whenever project understanding, verified state, or historical
-  record changed during the turn
+- update the relevant `.agents/` project-state files whenever project understanding, verified
+  state, open tasks, blockers, or historical record changed during the turn
 
 Always use `.agents/skills/mainsequence/project_builder/SKILL.md` as the source of truth for project
 scaffolding, folder structure, and standard repository layout.
@@ -340,6 +345,6 @@ If something may be a Main Sequence SDK, documentation, or platform issue:
 ## Project-State Files Under `.agents/`
 
 
-Do not improvise their meaning in domain skills. Use the maintenance skill to reconcile them after
-material work.
+Do not improvise their meaning in domain skills. Use the project bootstrap skill rules to reconcile
+them after material work.
 <!-- mainsequence-agent-scaffold:end -->

{mainsequence-4.4.27 → mainsequence-4.4.30}/agent_scaffold/skills/application_surfaces/api_surfaces/SKILL.md

@@ -39,7 +39,7 @@ This skill must not claim ownership of:
 - workspace document creation or mutation
 - AppComponent custom form design
 - job creation, scheduling, image pinning, or releases
-- Streamlit dashboard implementation
+- Streamlit dashboard design or implementation
 - non-FastAPI API framework choices for Main Sequence project APIs
 
 ## Route Adjacent Work
@@ -62,8 +62,8 @@ This skill must not claim ownership of:
   `.agents/skills/mainsequence/command_center/api_mock_prototyping/SKILL.md`
 - Jobs, images, resources, and releases:
   `.agents/skills/mainsequence/platform_operations/orchestration_and_releases/SKILL.md`
-- Streamlit dashboards:
-  `.agents/skills/mainsequence/dashboards/streamlit/SKILL.md`
+
+Streamlit dashboard implementation is app-owned project code, not a Main Sequence platform skill. Route Streamlit deployment only through orchestration and releases.
 
 ## Read First
 

{mainsequence-4.4.27 → mainsequence-4.4.30}/agent_scaffold/skills/command_center/connections/SKILL.md

@@ -45,7 +45,7 @@ This skill must not claim ownership of:
 - AppComponent custom forms or action contracts
 - generic FastAPI endpoint design
 - backend resource and release creation
-- Streamlit dashboards
+- Streamlit dashboard design or implementation
 
 ## Route Adjacent Work
 

{mainsequence-4.4.27 → mainsequence-4.4.30}/agent_scaffold/skills/command_center/widgets/app_components/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: command-center-app-components
-description: Use this skill when the task is about AppComponent widgets in a Main Sequence project. This skill owns AppComponent generated request forms, response-side editable-form and notification UI contracts, dynamic request/response binding contracts, and the boundary between AppComponent responses and widget-facing output contracts, including requiring generic tabular consumers to receive core.tabular_frame@v1 instead of ad hoc AppComponent JSON. Before changing AppComponent payloads or contracts, verify the target widget in the Command Center registry through the CLI. Source order is strict: registry detail first, SDK client models second, local Main Sequence repository docs/models third only if the first two still leave something unresolved. Main Sequence is platform-first: if an AppComponent depends on a project API, that API must already exist as a FastAPI project resource and have a corresponding FastAPI ResourceRelease before the AppComponent is considered usable from Command Center. Resource and release creation belong to the orchestration-and-releases skill. It does not own workspace layout, generic FastAPI design, or Streamlit dashboards.
+description: Use this skill when the task is about AppComponent widgets in a Main Sequence project. This skill owns AppComponent generated request forms, response-side editable-form and notification UI contracts, dynamic request/response binding contracts, and the boundary between AppComponent responses and widget-facing output contracts, including requiring generic tabular consumers to receive core.tabular_frame@v1 instead of ad hoc AppComponent JSON. Before changing AppComponent payloads or contracts, verify the target widget in the Command Center registry through the CLI. Source order is strict: registry detail first, SDK client models second, local Main Sequence repository docs/models third only if the first two still leave something unresolved. Main Sequence is platform-first: if an AppComponent depends on a project API, that API must already exist as a FastAPI project resource and have a corresponding FastAPI ResourceRelease before the AppComponent is considered usable from Command Center. Resource and release creation belong to the orchestration-and-releases skill. It does not own workspace layout, generic FastAPI design, or Streamlit dashboard design or implementation.
 ---
 
 # Command Center AppComponents
@@ -40,7 +40,7 @@ This skill must not claim ownership of:
 - generic FastAPI route architecture
 - tabular or operational data producer design
 - MetaTable schema design
-- Streamlit dashboard implementation
+- Streamlit dashboard design or implementation
 - scheduling, image pinning, resources, or releases
 
 ## Route Adjacent Work
@@ -61,8 +61,8 @@ This skill must not claim ownership of:
   `.agents/skills/mainsequence/data_publishing/meta_tables/SKILL.md`
 - Jobs, images, resources, and releases:
   `.agents/skills/mainsequence/platform_operations/orchestration_and_releases/SKILL.md`
-- Streamlit dashboards:
-  `.agents/skills/mainsequence/dashboards/streamlit/SKILL.md`
+
+Streamlit dashboard implementation is app-owned project code, not an AppComponent or Main Sequence platform skill. Route Streamlit dashboard deployment or release verification to orchestration and releases.
 
 ## Read First
 

{mainsequence-4.4.27 → mainsequence-4.4.30}/agent_scaffold/skills/command_center/workspace_builder/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: command-center-workspace-builder
-description: Use this skill when the task is about creating, updating, validating, or reviewing Main Sequence Command Center workspaces after the workspace design is known. This skill owns workspace documents, widget instance payload resolution, safe mutation, shared versus user state, widget-scoped mutation, connection-backed source widget mounting, and grounding those decisions against the richer widget-type registry contract plus the SDK command_center client models. Use workspace_design first when the task is still about deciding which widgets, layout, narrative, or visualization strategy should express the user intent; use command-center-connections first when source data or query contracts are unresolved. Source order is strict: registry detail first, SDK client models second, local Main Sequence repository docs/models third only when the first two still leave instance payload questions unresolved. Main Sequence is platform-first: if a mounted widget or AppComponent depends on a project API, that API must already exist as a FastAPI project resource and have a corresponding FastAPI ResourceRelease before the workspace flow is considered usable. Resource and release creation belong to the orchestration-and-releases skill. It does not own AppComponent form contracts, API implementation, workspace design, or Streamlit dashboards.
+description: Use this skill when the task is about creating, updating, validating, or reviewing Main Sequence Command Center workspaces after the workspace design is known. This skill owns workspace documents, widget instance payload resolution, safe mutation, shared versus user state, widget-scoped mutation, connection-backed source widget mounting, and grounding those decisions against the richer widget-type registry contract plus the SDK command_center client models. Use workspace_design first when the task is still about deciding which widgets, layout, narrative, or visualization strategy should express the user intent; use command-center-connections first when source data or query contracts are unresolved. Source order is strict: registry detail first, SDK client models second, local Main Sequence repository docs/models third only when the first two still leave instance payload questions unresolved. Main Sequence is platform-first: if a mounted widget or AppComponent depends on a project API, that API must already exist as a FastAPI project resource and have a corresponding FastAPI ResourceRelease before the workspace flow is considered usable. Resource and release creation belong to the orchestration-and-releases skill. It does not own AppComponent form contracts, API implementation, workspace design, or Streamlit dashboard design or implementation.
 ---
 
 # Command Center Workspace Builder
@@ -42,7 +42,7 @@ This skill must not claim ownership of:
 - AppComponent custom input forms
 - widget-facing API response contracts
 - generic FastAPI or backend API implementation
-- Streamlit dashboard implementation
+- Streamlit dashboard design or implementation
 - tabular or operational data producer design
 - MetaTable schema design
 
@@ -66,11 +66,11 @@ This skill must not claim ownership of:
   `.agents/skills/mainsequence/application_surfaces/api_surfaces/SKILL.md`
 - Jobs, images, resources, and releases:
   `.agents/skills/mainsequence/platform_operations/orchestration_and_releases/SKILL.md`
-- Streamlit dashboards:
-  `.agents/skills/mainsequence/dashboards/streamlit/SKILL.md`
 - MetaTables:
   `.agents/skills/mainsequence/data_publishing/meta_tables/SKILL.md`
 
+Streamlit dashboard implementation is app-owned project code, not a Main Sequence workspace skill. Route Streamlit dashboard deployment or release verification to orchestration and releases.
+
 ## Read First
 
 0. If widget selection, layout narrative, or visualization strategy is not already decided, use:

{mainsequence-4.4.27 → mainsequence-4.4.30}/agent_scaffold/skills/command_center/workspace_design/SKILL.md

@@ -48,8 +48,8 @@ This skill must not claim ownership of:
   `.agents/skills/mainsequence/data_publishing/meta_tables/SKILL.md`
 - Jobs, images, resources, and releases:
   `.agents/skills/mainsequence/platform_operations/orchestration_and_releases/SKILL.md`
-- Streamlit dashboards:
-  `.agents/skills/mainsequence/dashboards/streamlit/SKILL.md`
+
+Streamlit dashboard design and implementation are app-owned project work, not a Main Sequence Command Center or platform scaffold skill. Route only Streamlit dashboard deployment or release verification to orchestration and releases.
 
 ## Read First
 

{mainsequence-4.4.27 → mainsequence-4.4.30}/agent_scaffold/skills/data_access/exploration/SKILL.md

@@ -51,13 +51,15 @@ This skill discovers and identifies data. It does not publish, redesign, or defi
   `.agents/skills/mainsequence/data_publishing/meta_tables/SKILL.md`
 - FastAPI or application-facing implementation:
   `.agents/skills/mainsequence/application_surfaces/api_surfaces/SKILL.md`
-- Streamlit dashboards:
-  `.agents/skills/mainsequence/dashboards/streamlit/SKILL.md`
+- Streamlit dashboard deployment:
+  `.agents/skills/mainsequence/platform_operations/orchestration_and_releases/SKILL.md`
 - Command Center surfaces:
   `.agents/skills/mainsequence/command_center/workspace_builder/SKILL.md`
 - blocker and failure analysis:
   `.agents/skills/mainsequence/maintenance/bug_auditor/SKILL.md`
 
+Streamlit dashboard implementation is app-owned project code, not a Main Sequence scaffold skill.
+
 ## Read First
 
 1. `AGENTS.md`

{mainsequence-4.4.27 → mainsequence-4.4.30}/agent_scaffold/skills/maintenance/bug_auditor/SKILL.md

@@ -50,8 +50,6 @@ This skill audits. It does not implement by default.
 
 - bootstrap, routing, and repo structure:
   `.agents/skills/mainsequence/project_builder/SKILL.md`
-- `.agents/` state reconciliation after the audit:
-  `.agents/skills/mainsequence/maintenance/local_journal/SKILL.md`
 - DataNode implementation issues:
   `.agents/skills/mainsequence/data_publishing/data_nodes/SKILL.md`
 - MetaTable implementation issues:
@@ -62,8 +60,10 @@ This skill audits. It does not implement by default.
   `.agents/skills/mainsequence/platform_operations/orchestration_and_releases/SKILL.md`
 - RBAC and access issues:
   `.agents/skills/mainsequence/platform_operations/access_control_and_sharing/SKILL.md`
-- dashboard domain issues:
-  `.agents/skills/mainsequence/dashboards/streamlit/SKILL.md`
+- Streamlit dashboard deployment or release issues:
+  `.agents/skills/mainsequence/platform_operations/orchestration_and_releases/SKILL.md`
+
+Streamlit dashboard design and implementation failures are target-project application code issues unless the evidence points to Main Sequence deployment, resource discovery, image selection, release creation, or platform runtime behavior.
 
 ## Read First
 

{mainsequence-4.4.27 → mainsequence-4.4.30}/agent_scaffold/skills/platform_operations/access_control_and_sharing/SKILL.md

@@ -45,7 +45,7 @@ This skill must not claim ownership of:
 - DataNode producer implementation
 - MetaTable schema design
 - FastAPI route design
-- Streamlit dashboard implementation
+- Streamlit dashboard design or implementation
 - workspace document structure
 
 ## Route Adjacent Work
@@ -58,11 +58,13 @@ This skill must not claim ownership of:
   `.agents/skills/mainsequence/data_publishing/meta_tables/SKILL.md`
 - APIs and FastAPI:
   `.agents/skills/mainsequence/application_surfaces/api_surfaces/SKILL.md`
-- Streamlit dashboards:
-  `.agents/skills/mainsequence/dashboards/streamlit/SKILL.md`
+- Streamlit dashboard deployment:
+  `.agents/skills/mainsequence/platform_operations/orchestration_and_releases/SKILL.md`
 - Command Center workspaces:
   `.agents/skills/mainsequence/command_center/workspace_builder/SKILL.md`
 
+Streamlit dashboard implementation is app-owned project code. This skill only reasons about access to deployed resources such as `ResourceRelease`.
+
 ## Read First
 
 1. `docs/tutorial/role_based_access_control.md`

{mainsequence-4.4.27 → mainsequence-4.4.30}/agent_scaffold/skills/platform_operations/orchestration_and_releases/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: mainsequence-orchestration-and-releases
-description: Use this skill when the task is about operational execution in a Main Sequence project. This skill owns jobs, schedules, batch scheduling files, project images, run inspection, project resources, releases, and Artifacts as operational inputs. It does not own DataNode producer design, MetaTable schema design, API route contracts, or RBAC policy.
+description: Use this skill when the task is about operational execution in a Main Sequence project. This skill owns jobs, schedules, batch scheduling files, project images, run inspection, project resources, releases, Streamlit dashboard deployment, and Artifacts as operational inputs. It does not own DataNode producer design, MetaTable schema design, API route contracts, Streamlit dashboard design, or RBAC policy.
 ---
 
 # Main Sequence Orchestration And Releases
@@ -16,6 +16,7 @@ This skill is for:
 - images
 - project resources
 - releases
+- Streamlit dashboard deployment as `streamlit_dashboard` releases
 - operational logs and run inspection
 - Artifacts as job inputs or outputs
 
@@ -30,6 +31,7 @@ This skill is for:
 - freeze jobs to a project image
 - inspect job runs and logs
 - reason about project resources and resource releases
+- create or review Streamlit dashboard deployment through project resources and `streamlit_dashboard` releases
 - review Artifact-based workflows in operational pipelines
 
 ## This Skill Must Not Claim
@@ -41,6 +43,7 @@ This skill must not claim ownership of:
 - FastAPI route contracts
 - RBAC or sharing policy
 - Streamlit dashboard implementation details
+- Streamlit layout, styling, sidebar/session behavior, page structure, or UI helper design
 
 ## Route Adjacent Work
 
@@ -54,20 +57,22 @@ This skill must not claim ownership of:
   `.agents/skills/mainsequence/command_center/api_mock_prototyping/SKILL.md`
 - RBAC and sharing:
   `.agents/skills/mainsequence/platform_operations/access_control_and_sharing/SKILL.md`
-- Streamlit dashboards:
-  `.agents/skills/mainsequence/dashboards/streamlit/SKILL.md`
 
 ## Read First
 
 1. `docs/tutorial/scheduling_jobs.md`
 2. `docs/knowledge/infrastructure/scheduling_jobs.md`
 3. `docs/knowledge/infrastructure/artifacts.md`
+4. `docs/tutorial/dashboards/streamlit/streamlit_integration_2.md` when deploying or verifying a Streamlit dashboard
+5. `docs/knowledge/dashboards/streamlit/index.md` when deployment metadata or SDK/dashboard boundary questions matter
 
-If the task touches deployed dashboards or APIs, also read the relevant domain skill/docs before changing the operational workflow.
+If the task touches deployed FastAPI APIs, also read the relevant API skill/docs before changing the operational workflow.
+
+If the task asks to design, build, style, or restructure a Streamlit app, do not treat that as Main Sequence platform skill work. Streamlit implementation is app-owned project code. This skill only owns deployment and verification of an already-authored dashboard.
 
 If the task is about publishing a Command Center-facing API mainly to test AppComponent UX, bindings, or request/response contracts, read:
 
-4. `.agents/skills/mainsequence/command_center/api_mock_prototyping/SKILL.md`
+6. `.agents/skills/mainsequence/command_center/api_mock_prototyping/SKILL.md`
 
 Do that before building an image or creating a FastAPI `ResourceRelease`.
 
@@ -78,6 +83,7 @@ Before changing orchestration or release behavior, collect or infer:
 - the execution target:
   - `execution_path`
   - app entrypoint
+  - Streamlit `app.py` resource path when deploying a dashboard
 - whether the job is:
   - manual
   - interval
@@ -89,8 +95,10 @@ Before changing orchestration or release behavior, collect or infer:
 - whether the workflow is:
   - direct CLI/client job creation
   - repository-managed batch scheduling
+  - Streamlit dashboard release creation
 - whether Artifact inputs or outputs are part of the run
 - whether the job should be reproducible against a pinned image
+- for Streamlit dashboard deployment, the `README.md` resource next to `app.py`
 
 If the execution target or image strategy is unclear, stop before scheduling anything.
 
@@ -104,6 +112,7 @@ For every non-trivial orchestration task, decide:
 4. Is strict batch sync appropriate or dangerous?
 5. Does the workflow depend on Artifacts?
 6. Is the task actually a release/resource problem instead of only a job problem?
+7. For Streamlit dashboard deployment, do the selected app resource, README resource, and project image all refer to the intended pushed commit?
 
 ## Build Rules
 
@@ -175,7 +184,25 @@ For deployed dashboards, APIs, or agents:
 - the release must exist
 - the release must point at the intended image or resource version
 
-### 6.1 Do not publish an API just to test AppComponent contracts
+### 6.1 Streamlit dashboard deployment is a release workflow
+
+Main Sequence owns the deployment boundary for Streamlit dashboards, not the dashboard UI design.
+
+For Streamlit dashboard deployment:
+
+- the dashboard `app.py` must already exist in the repository
+- the dashboard `README.md` must exist next to `app.py`
+- both files must be committed and pushed
+- the project image must be built from the intended pushed commit
+- `mainsequence project project_resource list` must discover the dashboard app and README resources
+- create the release with `mainsequence project project_resource create_dashboard`
+- the dashboard release kind is `streamlit_dashboard`
+
+Do not prescribe Streamlit page layout, styling, sidebar/session patterns, or helper/component architecture. Those are application-owned implementation details.
+
+Validate the deployment path, not the Streamlit design.
+
+### 6.2 Do not publish an API just to test AppComponent contracts
 
 If the goal is to validate Command Center AppComponent UX, request rendering, response rendering, published outputs, or downstream bindings, do not jump straight to:
 
@@ -203,6 +230,7 @@ When reviewing an orchestration task, look for:
 - unsafe use of `--strict`
 - workflows depending on laptop-specific file paths instead of Artifacts
 - image or release work being used as a substitute for predeployment AppComponent/API contract validation
+- Streamlit dashboard deployment work drifting into app design or UI implementation ownership
 - tasks that are really resource/release problems rather than simple job problems
 
 ## Validation Checklist
@@ -219,6 +247,7 @@ Do not claim success until you have checked:
 - the job exists after creation or sync
 - runs and logs were inspected when execution success matters
 - resources and releases were verified when deployment success matters
+- Streamlit dashboard releases use the intended app resource, README resource, image, and `streamlit_dashboard` release kind
 - Command Center-facing API publishing is not being used just to test AppComponent UX that should have been validated first in `mock-json` mode
 
 If the workflow uses `scheduled_jobs.yaml`, also check:

{mainsequence-4.4.27 → mainsequence-4.4.30}/agent_scaffold/skills/project_builder/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: mainsequence-project
-description: Use this skill to bootstrap work in a Main Sequence repository. This skill owns project context verification, docs-first behavior, success-definition discipline, and routing between specialized domain skills and the maintenance skill. It does not own domain implementation semantics or direct reconciliation of the project-state files under `.agents/`.
+description: Use this skill to bootstrap work in a Main Sequence repository. This skill owns project context verification, docs-first behavior, success-definition discipline, routing between specialized domain skills, and project-state file discipline. It does not own domain implementation semantics.
 ---
 
 # Main Sequence Project Bootstrap
@@ -24,7 +24,7 @@ This skill is for:
 - define a concrete success condition before implementation starts
 - verify current project and platform context
 - decide which specialized skill owns the actual domain work
-- decide when to hand off to `.agents/skills/mainsequence/maintenance/local_journal/SKILL.md`
+- decide when project-state files under `.agents/` need to be read or updated
 - enforce standard Main Sequence repository structure expectations
 - separate verified facts from assumptions
 - record documentation mismatches and route follow-up work
@@ -42,7 +42,7 @@ This skill must not claim ownership of:
 - jobs, schedules, images, resources, or releases
 - RBAC or sharing semantics
 - domain assets, translation tables, or construction logic
-- Streamlit dashboard implementation
+- Streamlit dashboard design or implementation
 - pricing-runtime semantics
 
 Do not let this skill become a domain manual.
@@ -61,27 +61,24 @@ Do not let this skill become a domain manual.
   `.agents/skills/mainsequence/command_center/workspace_builder/SKILL.md`
 - AppComponents, custom forms, and widget-facing API contracts:
   `.agents/skills/mainsequence/command_center/widgets/app_components/SKILL.md`
-- project-state reconciliation and local history under `.agents/`:
-  `.agents/skills/mainsequence/maintenance/local_journal/SKILL.md`
 - project status audits, blocker analysis, and upstream SDK assessment:
   `.agents/skills/mainsequence/maintenance/bug_auditor/SKILL.md`
-- jobs, schedules, artifacts, images, resources, and releases:
+- jobs, schedules, artifacts, images, resources, releases, and Streamlit dashboard deployment:
   `.agents/skills/mainsequence/platform_operations/orchestration_and_releases/SKILL.md`
 - RBAC and sharing:
   `.agents/skills/mainsequence/platform_operations/access_control_and_sharing/SKILL.md`
-- Streamlit dashboards:
-  `.agents/skills/mainsequence/dashboards/streamlit/SKILL.md`
+
+Streamlit dashboard design and implementation are app-owned project work, not a separate Main Sequence scaffold skill. Route only platform deployment of an already-authored Streamlit dashboard to orchestration and releases.
 
 ## Read First
 
 1. `AGENTS.md`
-2. `.agents/skills/mainsequence/maintenance/local_journal/SKILL.md`
-3. the latest relevant Main Sequence docs for the task
-4. `.agents/brief.md`
-5. `.agents/status.md`
-6. `.agents/tasks.md`
-7. `.agents/record.md`
-8. `.agents/journal.md` when resuming, debugging, or investigating a repeated issue
+2. the latest relevant Main Sequence docs for the task
+3. `.agents/brief.md`
+4. `.agents/status.md`
+5. `.agents/tasks.md`
+6. `.agents/record.md`
+7. `.agents/journal.md` when resuming, debugging, or investigating a repeated issue
 
 Canonical documentation root:
 `https://mainsequence-sdk.github.io/mainsequence-sdk/`
@@ -95,7 +92,7 @@ Before starting non-trivial work, collect or infer:
 - the repository path and current project context
 - whether live platform verification is required
 - which specialized skill should own the domain behavior
-- whether the maintenance skill will need to run after the domain step
+- whether project-state files under `.agents/` will need updates after the domain step
 
 If the user goal or project context is unclear, stop before routing domain work.
 
@@ -106,7 +103,7 @@ For every non-trivial task, decide:
 1. What does success look like in observable terms?
 2. Which specialized skill owns the domain behavior?
 3. Does platform state need live verification?
-4. Will the maintenance skill need to run after this step?
+4. Will project-state files under `.agents/` need to be updated after this step?
 5. Are the docs and local implementation aligned, or is there a discrepancy to record?
 
 ## Build Rules
@@ -170,13 +167,9 @@ Once the task boundary is clear, move into the correct specialized skill.
 
 Do not teach domain semantics here.
 
-### 6. Hand off to maintenance after material work
-
-After material domain work, route to:
-
-- `.agents/skills/mainsequence/maintenance/local_journal/SKILL.md`
+### 6. Update project-state files after material work
 
-Use that handoff when the turn changed:
+After material domain work, update the relevant project-state files under `.agents/` when the turn changed:
 
 - verified state
 - blockers
@@ -198,7 +191,7 @@ Before first-running or validating a new or changed DataNode, use an explicit na
 When reviewing bootstrap behavior, look for:
 
 - domain work happening without a clear owner skill
-- material domain work finishing without a maintenance handoff
+- material domain work finishing without required project-state updates
 - implementation starting without a concrete success condition
 - platform claims made without verification
 - docs mismatches that were noticed but not recorded
@@ -212,7 +205,7 @@ Do not claim bootstrap success until you have checked:
 - the relevant docs were checked
 - the success condition is explicit
 - the correct specialized skill was chosen
-- the maintenance handoff was made when project state materially changed
+- required project-state updates were made when project state materially changed
 - any platform-state claims were verified with CLI or platform tooling
 
 ## This Skill Must Stop And Escalate When

{mainsequence-4.4.27 → mainsequence-4.4.30}/mainsequence/client/agent_runtime_models.py

@@ -10,7 +10,7 @@ from enum import Enum
 from typing import Any, ClassVar
 
 import requests
-from pydantic import ConfigDict, Field
+from pydantic import ConfigDict, Field, model_validator
 
 from .base import BaseObjectOrm, BasePydanticModel, ShareableObjectMixin
 from .exceptions import ApiError, raise_for_response
@@ -118,6 +118,10 @@ class AgentRuntimeImageDrift(BasePydanticModel):
         None,
         description="Additional backend detail when drift information is unavailable or degraded.",
     )
+    catalog_state: dict[str, Any] | None = Field(
+        None,
+        description="Platform catalog freshness state returned by the backend, when available.",
+    )
 
 
 class AgentRuntimePaths(BasePydanticModel):
@@ -165,9 +169,13 @@ class AgentSessionRuntimeAccess(BasePydanticModel):
         default_factory=AgentRuntimePaths,
         description="Runtime-relative paths returned by the control plane.",
     )
+    service_runtime_uid: str | None = Field(
+        None,
+        description="Public UID of the linked service runtime, when the backend has one.",
+    )
     knative_service_runtime_uid: str | None = Field(
         None,
-        description="Public UID of the linked Knative service runtime, when the backend has one.",
+        description="Deprecated alias for service_runtime_uid kept for older SDK callers.",
     )
     image_drift: AgentRuntimeImageDrift | None = Field(
         None,
@@ -180,6 +188,20 @@ class AgentSessionRuntimeAccess(BasePydanticModel):
             return None
         return self.image_drift.model_dump()
 
+    @model_validator(mode="after")
+    def _mirror_service_runtime_uid(self) -> AgentSessionRuntimeAccess:
+        if (
+            self.service_runtime_uid is None
+            and self.knative_service_runtime_uid is not None
+        ):
+            self.service_runtime_uid = self.knative_service_runtime_uid
+        elif (
+            self.knative_service_runtime_uid is None
+            and self.service_runtime_uid is not None
+        ):
+            self.knative_service_runtime_uid = self.service_runtime_uid
+        return self
+
 
 def _join_runtime_url(rpc_url: str, runtime_path: str) -> str:
     if not isinstance(rpc_url, str) or not rpc_url.strip():
@@ -423,9 +445,27 @@ class CodingAgentService(BaseObjectOrm, BasePydanticModel):
     related_job_uid: str | None = Field(
         None, description="Public UID of the backing job, if attached."
     )
-    knative_service_runtime_uid: str | None = Field(
-        None, description="Public UID of the backing Knative service runtime, if attached."
+    service_runtime_uid: str | None = Field(
+        None, description="Public UID of the backing service runtime, if attached."
     )
+    knative_service_runtime_uid: str | None = Field(
+        None,
+        description="Deprecated alias for service_runtime_uid kept for older SDK callers.",
+    )
+
+    @model_validator(mode="after")
+    def _mirror_service_runtime_uid(self) -> CodingAgentService:
+        if (
+            self.service_runtime_uid is None
+            and self.knative_service_runtime_uid is not None
+        ):
+            self.service_runtime_uid = self.knative_service_runtime_uid
+        elif (
+            self.knative_service_runtime_uid is None
+            and self.service_runtime_uid is not None
+        ):
+            self.knative_service_runtime_uid = self.service_runtime_uid
+        return self
 
     @classmethod
     def _post_collection_action(

{mainsequence-4.4.27 → mainsequence-4.4.30}/mainsequence.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: mainsequence
-Version: 4.4.27
+Version: 4.4.30
 Summary: Main Sequence SDK 
 Author-email: Main Sequence GmbH <dev@main-sequence.io>
 License: MainSequence GmbH SDK License Agreement

{mainsequence-4.4.27 → mainsequence-4.4.30}/mainsequence.egg-info/SOURCES.txt

@@ -13,7 +13,6 @@ agent_scaffold/skills/command_center/widgets/tabular_transform/SKILL.md
 agent_scaffold/skills/command_center/workspace_analysis/SKILL.md
 agent_scaffold/skills/command_center/workspace_builder/SKILL.md
 agent_scaffold/skills/command_center/workspace_design/SKILL.md
-agent_scaffold/skills/dashboards/streamlit/SKILL.md
 agent_scaffold/skills/data_access/exploration/SKILL.md
 agent_scaffold/skills/data_publishing/data_nodes/SKILL.md
 agent_scaffold/skills/data_publishing/meta_table_migrations/SKILL.md

{mainsequence-4.4.27 → mainsequence-4.4.30}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "mainsequence"
-version = "4.4.27"
+version = "4.4.30"
 description = "Main Sequence SDK "
 readme = "README.md"
 requires-python = ">=3.11"