mainsequence 8.0.5__tar.gz → 8.0.7__tar.gz

{mainsequence-8.0.5/mainsequence.egg-info → mainsequence-8.0.7}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: mainsequence
-Version: 8.0.5
+Version: 8.0.7
 Summary: Main Sequence SDK 
 Author-email: Main Sequence GmbH <dev@main-sequence.io>
 License-Expression: LicenseRef-MainSequence-Proprietary
@@ -56,7 +56,7 @@ The Main Sequence Python SDK is the client and development toolkit for the Main
 The Main Sequence platform allows you to:
 
 1. rapidly build and deploy data products with normalized `MetaTable` contracts and `TimeIndexTableUpdater` producer workflows
-2. rapidly deploy RBAC-enabled dashboards on the platform
+2. deploy FastAPI services and supported application surfaces on the platform
 3. rapidly deploy agents using the Google Agent SDK
 
 The key idea is that you can focus on development and deployment, while the platform handles the DevOps layer.
@@ -103,8 +103,8 @@ Recommended entry points:
   - [MetaTables](docs/knowledge/meta_tables/index.md)
   - [Constants and Secrets](docs/knowledge/infrastructure/constants_and_secrets.md)
   - [Scheduling Jobs](docs/knowledge/infrastructure/scheduling_jobs.md)
-  - [Streamlit Dashboards](docs/knowledge/dashboards/streamlit/index.md)
 - Migrations:
+  - [Streamlit dashboard support removal](docs/migrations/streamlit-dashboard-removal.md)
   - [7.x to 8.0: CodeRepository ontology hard cut](docs/migrations/v8-code-repository-ontology.md)
   - [6.x to 7.0: Time-Index Table Updater hard cut](docs/migrations/v7-time-index-table-updater-hard-cut.md)
 - CLI:
@@ -157,7 +157,7 @@ From there, the normal learning path is:
 3. understand sharing and RBAC for published tables
 4. add an API or another application surface
 5. schedule jobs
-6. build dashboards or downstream consumers
+6. build supported application surfaces or downstream consumers
 7. package the CodeRepository as an agent-facing surface when it is ready
 
 ## Installation for development

{mainsequence-8.0.5 → mainsequence-8.0.7}/README.md

@@ -14,7 +14,7 @@ The Main Sequence Python SDK is the client and development toolkit for the Main
 The Main Sequence platform allows you to:
 
 1. rapidly build and deploy data products with normalized `MetaTable` contracts and `TimeIndexTableUpdater` producer workflows
-2. rapidly deploy RBAC-enabled dashboards on the platform
+2. deploy FastAPI services and supported application surfaces on the platform
 3. rapidly deploy agents using the Google Agent SDK
 
 The key idea is that you can focus on development and deployment, while the platform handles the DevOps layer.
@@ -61,8 +61,8 @@ Recommended entry points:
   - [MetaTables](docs/knowledge/meta_tables/index.md)
   - [Constants and Secrets](docs/knowledge/infrastructure/constants_and_secrets.md)
   - [Scheduling Jobs](docs/knowledge/infrastructure/scheduling_jobs.md)
-  - [Streamlit Dashboards](docs/knowledge/dashboards/streamlit/index.md)
 - Migrations:
+  - [Streamlit dashboard support removal](docs/migrations/streamlit-dashboard-removal.md)
   - [7.x to 8.0: CodeRepository ontology hard cut](docs/migrations/v8-code-repository-ontology.md)
   - [6.x to 7.0: Time-Index Table Updater hard cut](docs/migrations/v7-time-index-table-updater-hard-cut.md)
 - CLI:
@@ -115,7 +115,7 @@ From there, the normal learning path is:
 3. understand sharing and RBAC for published tables
 4. add an API or another application surface
 5. schedule jobs
-6. build dashboards or downstream consumers
+6. build supported application surfaces or downstream consumers
 7. package the CodeRepository as an agent-facing surface when it is ready
 
 ## Installation for development

{mainsequence-8.0.5 → mainsequence-8.0.7}/agent_scaffold/AGENTS.md

@@ -65,9 +65,8 @@ Core responsibilities:
   - for data publishing and data pipelines, use `TimeIndexTableUpdater`s and `MetaTable`s
   - for APIs serving the Command Center frontend, use the contract-authoritative
     FastAPI release workflow
-  - for visualization, confirm the delivery target with the user:
-    - if they want a Streamlit app, treat app design and implementation as repository-owned code and
-      use Main Sequence skills only for platform deployment and release verification
+  - for visualization, confirm the supported delivery target with the user, such as a Command
+    Center frontend backed by FastAPI or a static site
   - for scheduled execution, releases, and backend operations, use jobs, images, resources, and
     other platform objects through the proper platform skills
 - break work into independent executions according to the skill each part requires
@@ -85,8 +84,7 @@ Typical outcomes include:
 - build and release a `FastAPI` API whose Command Center contract-bearing
   responses conform to a recorded revision of the canonical Command Center SDK
   GitHub contracts
-- confirm whether a visualization should be a repository-owned Streamlit app or a reusable Command
-  Center surface before building or deploying it
+- confirm which supported application surface should deliver a visualization before building it
 - build reusable business logic in `src/` and keep thin integration layers in APIs, jobs, and
   dashboards
 - assess blockers and suspected SDK or platform issues from concrete repository and runtime evidence
@@ -107,7 +105,6 @@ Working rules for this role:
 User-resolution rule for agents:
 
 - use `User.get_logged_user()` only when code is running with request-bound identity context:
-  - Streamlit
   - code that explicitly binds `_CURRENT_AUTH_HEADERS`
 - treat its result as `RequestUserIdentity`: the human caller's canonical `uid` and optional
   `username`, never a numeric id or a full account profile
@@ -140,7 +137,7 @@ Delegation rules:
 
 ## Main Sequence Source-Of-Truth Rule
 
-For any task involving Main Sequence code, CLI usage, TimeIndexTableUpdaters, orchestration, jobs, dashboards,
+For any task involving Main Sequence code, CLI usage, TimeIndexTableUpdaters, orchestration, jobs, application surfaces,
 agents, releases, artifacts, RBAC, or platform
 validation, always consult the latest relevant Main Sequence documentation before acting.
 
@@ -158,7 +155,7 @@ Before implementation, debugging, or validation, make the success condition expl
 
 At minimum, define:
 
-- what artifact, behavior, dataset, job, dashboard, release, or document should exist at the end
+- what artifact, behavior, dataset, job, application surface, release, or document should exist at the end
 - what checks will prove it worked
 - what platform objects must be verified
 - what is in scope and what is intentionally not being claimed
@@ -172,7 +169,7 @@ Examples:
 - job or schedule success:
   the job exists with the intended configuration, the run executes successfully, and logs confirm
   expected behavior
-- dashboard or release success:
+- application-surface or release success:
   the resource is present, the release exists for the intended image or commit, and the deployed
   behavior is verified
 - documentation success:
@@ -210,13 +207,6 @@ 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`
-- Streamlit dashboard deployment and release verification:
-  `.agents/skills/mainsequence/platform_operations/orchestration_and_releases/SKILL.md`
-
-Streamlit dashboard design and implementation are app-owned repository work, not a separate Main
-Sequence scaffold skill. Route only deployment of an already-authored Streamlit dashboard to
-orchestration and releases.
-
 ## Mandatory Startup Sequence
 
 For any non-trivial Main Sequence task:
@@ -297,7 +287,7 @@ At minimum, verify relevant:
 - jobs
 - job runs and logs
 - code repository images
-- dashboard or agent resources/releases
+- application or agent resources/releases
 - data assets
 - related platform objects used by the CodeRepository
 

{mainsequence-8.0.5 → mainsequence-8.0.7}/agent_scaffold/skills/data_access/exploration/SKILL.md

@@ -51,13 +51,9 @@ This skill discovers and identifies data. It does not publish, redesign, or defi
   `.agents/skills/mainsequence/data_publishing/meta_tables/SKILL.md`
 - FastAPI providers serving the Command Center frontend:
   `.agents/skills/mainsequence/application_surfaces/api_surfaces/SKILL.md`
-- Streamlit dashboard deployment:
-  `.agents/skills/mainsequence/platform_operations/orchestration_and_releases/SKILL.md`
 - blocker and failure analysis:
   `.agents/skills/mainsequence/maintenance/bug_auditor/SKILL.md`
 
-Streamlit dashboard implementation is app-owned repository code, not a Main Sequence scaffold skill.
-
 ## Read First
 
 1. `AGENTS.md`

{mainsequence-8.0.5 → mainsequence-8.0.7}/agent_scaffold/skills/maintenance/bug_auditor/SKILL.md

@@ -59,14 +59,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`
-- Streamlit dashboard deployment or release issues:
-  `.agents/skills/mainsequence/platform_operations/orchestration_and_releases/SKILL.md`
 - environment repair, authentication refresh, SDK updates, managed skill
   refresh, and CodeRepository sync after the failure is classified:
   `.agents/skills/mainsequence/maintenance/code_repository_maintenance/SKILL.md`
 
-Streamlit dashboard design and implementation failures are target-repository application code issues unless the evidence points to Main Sequence deployment, resource discovery, image selection, release creation, or platform runtime behavior.
-
 ## Read First
 
 1. `AGENTS.md`

{mainsequence-8.0.5 → mainsequence-8.0.7}/agent_scaffold/skills/platform_operations/access_control_and_sharing/SKILL.md

@@ -45,7 +45,7 @@ This skill must not claim ownership of:
 - TimeIndexTableUpdater producer implementation
 - MetaTable schema design
 - FastAPI route design
-- Streamlit dashboard design or implementation
+- application UI design or implementation
 - workspace document structure
 
 ## Route Adjacent Work
@@ -58,10 +58,7 @@ This skill must not claim ownership of:
   `.agents/skills/mainsequence/data_publishing/meta_tables/SKILL.md`
 - Command Center-serving FastAPI providers:
   `.agents/skills/mainsequence/application_surfaces/api_surfaces/SKILL.md`
-- Streamlit dashboard deployment:
-  `.agents/skills/mainsequence/platform_operations/orchestration_and_releases/SKILL.md`
-
-Streamlit dashboard implementation is app-owned repository code. This skill only reasons about access to deployed resources such as `ResourceRelease`.
+This skill only reasons about access to deployed resources such as `ResourceRelease`.
 
 ## Read First
 

{mainsequence-8.0.5 → mainsequence-8.0.7}/agent_scaffold/skills/platform_operations/orchestration_and_releases/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: mainsequence-orchestration-and-releases
-description: Use this skill for Main Sequence jobs, schedules, backend-managed code-repository workflow files, code repository images, run inspection, resources, releases, Streamlit deployment, and operational Artifacts. It does not own TimeIndexTableUpdater behavior, MetaTable schemas, API contracts, Streamlit design, or RBAC policy.
+description: Use this skill for Main Sequence jobs, schedules, backend-managed code-repository workflow files, code repository images, run inspection, resources, releases, and operational Artifacts. It does not own TimeIndexTableUpdater behavior, MetaTable schemas, API contracts, application UI design, or RBAC policy.
 ---
 
 # Main Sequence Orchestration And Releases
@@ -16,7 +16,6 @@ This skill is for:
 - images
 - code repository resources
 - releases
-- Streamlit dashboard deployment as `streamlit_dashboard` releases
 - operational logs and run inspection
 - Artifacts as job inputs or outputs
 
@@ -33,7 +32,6 @@ This skill is for:
 - reason about code repository resources and resource releases
 - decide whether a `ResourceRelease` should opt into `automatic_deployment`
 - inspect automatic deployment run state for release rotations
-- create or review Streamlit dashboard deployment through code repository resources and `streamlit_dashboard` releases
 - review Artifact-based workflows in operational pipelines
 
 ## This Skill Must Not Claim
@@ -44,8 +42,7 @@ This skill must not claim ownership of:
 - MetaTable schema and row semantics
 - Command Center FastAPI wire contracts
 - RBAC or sharing policy
-- Streamlit dashboard implementation details
-- Streamlit layout, styling, sidebar/session behavior, page structure, or UI helper design
+- application UI implementation details
 
 ## Route Adjacent Work
 
@@ -64,13 +61,8 @@ This skill must not claim ownership of:
 2. `docs/knowledge/infrastructure/scheduling_jobs.md`
 3. `docs/knowledge/infrastructure/artifacts.md`
 4. `docs/knowledge/infrastructure/owner_observability.md` when inspecting logs or resource usage
-5. `docs/tutorial/dashboards/streamlit/streamlit_integration_2.md` when deploying or verifying a Streamlit dashboard
-6. `docs/knowledge/dashboards/streamlit/index.md` when deployment metadata or SDK/dashboard boundary questions matter
-
 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 repository code. This skill only owns deployment and verification of an already-authored dashboard.
-
 ## Inputs This Skill Needs
 
 Before changing orchestration or release behavior, collect or infer:
@@ -78,7 +70,6 @@ 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
@@ -90,13 +81,11 @@ Before changing orchestration or release behavior, collect or infer:
 - whether the workflow is:
   - direct CLI/client job creation
   - backend-managed code-repository workflow declarations
-  - Streamlit dashboard release creation
 - whether a `ResourceRelease` should be manually pinned or opted into repository-sync automatic deployment
 - whether Artifact inputs or outputs are part of the run
 - who owns the exact initial image: the caller for manual pinning or the
   backend for automatic deployment
 - whether future qualifying immutable repository events may promote a standalone Job
-- 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.
 
@@ -110,8 +99,7 @@ For every non-trivial orchestration task, decide:
    automatic deployment make the backend derive it from the synchronized commit?
 4. Does the workflow depend on Artifacts?
 5. Is the task actually a release/resource problem instead of only a job problem?
-6. For Streamlit dashboard deployment, do the selected app resource, README resource, and code repository image all refer to the intended pushed commit?
-7. For a `ResourceRelease`, should repository sync be allowed to rotate the release automatically through `automatic_deployment`?
+6. For a `ResourceRelease`, should repository sync be allowed to rotate the release automatically through `automatic_deployment`?
 
 ## Build Rules
 
@@ -235,32 +223,14 @@ Do not force a file workflow into a table workflow too early.
 
 ### 6. Resources and releases are part of deployment, not just code
 
-For deployed dashboards, APIs, or agents:
+For deployed APIs, agents, or other supported resources:
 
 - the local file is not enough
 - the code repository resource must exist
 - the release must exist
 - the release must point at the intended image or resource version
 
-### 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 code repository image must be built from the intended pushed commit
-- `mainsequence code-repository resources list` must discover the dashboard app and README resources
-- create the release with `mainsequence code-repository resources 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 Automatic ResourceRelease deployment
+### 6.1 Automatic ResourceRelease deployment
 
 `automatic_deployment` is the automated deployment opt-in flag on a `ResourceRelease`. It means repository synchronization can rotate an existing release to the latest synced CodeRepository commit for the same resource path.
 
@@ -268,7 +238,7 @@ When `automatic_deployment=True`, repository-sync events may create a unified `D
 
 - reads the CodeRepository's current synced commit
 - resolves the current code repository resource at the release's existing resource path
-- resolves the current adjacent `README.md` when the release kind requires one, such as Streamlit dashboards
+- resolves supporting resources required by the release kind
 - creates or resolves the code repository image for that commit
 - redeploys the existing release to the current resource, README, and code repository image
 - records state, phase, outcome, revision context, artifact context, steps, logs, result, and errors on the deployment run
@@ -280,7 +250,7 @@ Enable `automatic_deployment` only when:
 - the release should track the CodeRepository's synced version
 - the resource path is stable across commits
 - the current synced branch/version is an acceptable deployment source for that release
-- dashboard README requirements are satisfied for the current commit
+- required supporting resources are available for the current commit
 - the team accepts CI/CD-style rotation for this release
 
 Keep `automatic_deployment` disabled when:
@@ -293,13 +263,11 @@ Keep `automatic_deployment` disabled when:
 
 Create opted-in releases with the CLI flags that exist:
 
-- `mainsequence code-repository resources create_dashboard --automatic-deployment`
 - `mainsequence code-repository resources create_fastapi --automatic-deployment`
 - use `--no-automatic-deployment` when the decision is explicitly to keep the release pinned/manual
 
 The SDK surface also accepts:
 
-- `CodeRepositoryResource.create_dashboard(..., automatic_deployment=True)`
 - `CodeRepositoryResource.create_fastapi(..., automatic_deployment=True)`
 - `ResourceRelease.create(..., automatic_deployment=True)`
 - `ResourceRelease.deploy_current_version()` for an SDK-triggered manual deployment run; it returns `DeploymentRun`
@@ -336,8 +304,7 @@ When reviewing an orchestration task, look for:
 - workflows depending on laptop-specific file paths instead of Artifacts
 - `automatic_deployment` enabled without an explicit decision about repository-sync CI/CD rotation
 - assumptions that automatic deployment will deploy local unpushed changes
-- automatic release rotation where the resource path or dashboard README is not stable
-- Streamlit dashboard deployment work drifting into app design or UI implementation ownership
+- automatic release rotation where the resource path or required supporting resources are not stable
 - tasks that are really resource/release problems rather than simple job problems
 
 ## Validation Checklist
@@ -355,7 +322,6 @@ Do not claim success until you have checked:
 - the job exists after direct creation or repository workflow application
 - 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
 - `automatic_deployment` is intentionally enabled or disabled on each release
 - automatic deployment runs were inspected when repository-sync rotation matters
 - automatic deployment results match the intended commit, resource, README, image, and terminal status

{mainsequence-8.0.5 → mainsequence-8.0.7}/agent_scaffold/skills/sdk_code_repository_execution/SKILL.md

@@ -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 design or implementation
+- unsupported application deployment targets
 - pricing-runtime semantics
 
 Do not let this skill become a domain manual.
@@ -62,13 +62,11 @@ Do not let this skill become a domain manual.
 - local environment repair, CodeRepository authentication refresh, SDK updates,
   managed skill refresh, and canonical CodeRepository sync:
   `.agents/skills/mainsequence/maintenance/code_repository_maintenance/SKILL.md`
-- jobs, schedules, artifacts, images, resources, releases, and Streamlit dashboard deployment:
+- jobs, schedules, artifacts, images, resources, and releases:
   `.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 dashboard design and implementation are app-owned repository 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`
@@ -149,8 +147,6 @@ Also maintain these standard repository areas when relevant:
 - `tests/`
 - `docs/`
 - `api/`
-- `dashboards/`
-- `dashboards/components/`
 
 If the CodeRepository has recurring scheduled jobs or repository-managed releases,
 keep backend-managed declarations as direct `.yaml` or `.yml` children of

{mainsequence-8.0.5 → mainsequence-8.0.7}/mainsequence/cli/api.py

@@ -2861,10 +2861,13 @@ def create_code_repository_resource_release(
     Create a resource release via SDK client model.
 
     Single source of truth:
-      - delegates to `CodeRepositoryResource.create_dashboard()` or
-        `CodeRepositoryResource.create_fastapi()`
+      - delegates to `CodeRepositoryResource.create_fastapi()`
       - which in turn use `ResourceRelease.create()`
     """
+    normalized_release_kind = str(release_kind).strip()
+    if normalized_release_kind != "fastapi":
+        raise ApiError("release_kind must be 'fastapi'.")
+
     tokens = get_tokens()
     access = (tokens.get("access") or "").strip()
     refresh = (tokens.get("refresh") or "").strip()
@@ -2924,16 +2927,9 @@ def create_code_repository_resource_release(
             "timeout": timeout,
         }
 
-        create_method_name = {
-            "streamlit_dashboard": "create_dashboard",
-            "fastapi": "create_fastapi",
-        }.get(str(release_kind).strip())
-        if not create_method_name:
-            raise ApiError("release_kind must be one of: 'streamlit_dashboard', 'fastapi'.")
-
-        create_method = getattr(resource, create_method_name, None)
+        create_method = getattr(resource, "create_fastapi", None)
         if not callable(create_method):
-            raise ApiError(f"CodeRepositoryResource does not implement {create_method_name}().")
+            raise ApiError("CodeRepositoryResource does not implement create_fastapi().")
         created = create_method(**create_kwargs)
 
         if isinstance(created, dict):
@@ -4532,7 +4528,6 @@ def create_code_repository_job(
     name: str,
     code_repository_branch_uid: str,
     execution_path: str | None = None,
-    app_name: str | None = None,
     task_schedule: dict[str, Any] | str | None = None,
     cpu_request: str | int | float | None = None,
     memory_request: str | int | float | None = None,
@@ -4601,7 +4596,6 @@ def create_code_repository_job(
             name=name,
             code_repository_branch_uid=resolved_branch_uid,
             execution_path=execution_path,
-            app_name=app_name,
             task_schedule=task_schedule,
             cpu_request=cpu_request,
             memory_request=memory_request,
@@ -4742,11 +4736,8 @@ def run_code_repository_job(
         payload = job.run_job(timeout=timeout, command_args=command_args)
         effective_tokens: list[str] = []
         execution_path = str(getattr(job, "execution_path", "") or "").strip()
-        app_name = str(getattr(job, "app_name", "") or "").strip()
         if execution_path:
             effective_tokens.append(execution_path)
-        elif app_name:
-            effective_tokens.append(f"app:{app_name}")
         if command_args:
             effective_tokens.extend(str(arg) for arg in command_args)
         effective_run = shlex.join(effective_tokens) if effective_tokens else None