mainsequence 4.4.5__tar.gz → 4.4.10__tar.gz

{mainsequence-4.4.5/mainsequence.egg-info → mainsequence-4.4.10}/PKG-INFO

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

{mainsequence-4.4.5 → mainsequence-4.4.10}/agent_scaffold/AGENTS.md

@@ -17,14 +17,26 @@ uses them to update only the Main Sequence section below.
 <!-- mainsequence-agent-scaffold:start schema=1 source=agent_scaffold -->
 ## Main Sequence Instructions
 
-Before any non-trivial Main Sequence work, update the project SDK first and then refresh the
-installed Main Sequence scaffold files so the local CLI surface, `AGENTS.md`, and
-`.agents/skills/mainsequence/` match the installed SDK version:
+Before any non-trivial Main Sequence work, update the project SDK first, then compare the
+installed SDK version with the managed skills pin:
 
 - `mainsequence project update-sdk --path .`
+
+After the SDK update, inspect `.agents/skills/mainsequence/PINNED_FROM.txt`.
+Its `pinned_version=...` value records the SDK version that supplied the copied
+Main Sequence skills. Compare that value with the installed SDK version reported
+by `mainsequence --version`.
+
+Refresh the managed scaffold only when `PINNED_FROM.txt` is missing or its
+`pinned_version` differs from the installed SDK version:
+
 - `mainsequence project update AGENTS.md --path .`
 - `mainsequence project update_agent_skills --path .`
 
+If `pinned_version` already matches the installed SDK version, do not refresh
+`AGENTS.md` or `.agents/skills/mainsequence/` as a startup ritual; continue with
+the task.
+
 Canonical Main Sequence documentation root:
 `https://mainsequence-sdk.github.io/mainsequence-sdk/`
 
@@ -179,7 +191,13 @@ Typical routing:
 - Command Center workspace JSON creation/update and mounted widget mutation:
   `.agents/skills/mainsequence/command_center/workspace_builder/SKILL.md`
 - AppComponents, custom forms, and widget input or output contracts:
-  `.agents/skills/mainsequence/command_center/app_components/SKILL.md`
+  `.agents/skills/mainsequence/command_center/widgets/app_components/SKILL.md`
+- Command Center table/pro-table widgets, tabular frames, table visual metadata, formulas,
+  selections, and live merge mappings:
+  `.agents/skills/mainsequence/command_center/widgets/tables/SKILL.md`
+- Command Center tabular transform widgets, projection, filtering, aggregate, pivot, unpivot,
+  computed columns, and seed/live update bindings:
+  `.agents/skills/mainsequence/command_center/widgets/tabular_transform/SKILL.md`
 - predeployment AppComponent/API contract testing through `apiTargetMode: "mock-json"`:
   `.agents/skills/mainsequence/command_center/api_mock_prototyping/SKILL.md`
 - jobs, schedules, images, project resources, releases, and Artifacts:
@@ -207,10 +225,15 @@ For any non-trivial Main Sequence task:
     `mainsequence project open-signed-terminal <PROJECT_ID>`
 11. Before proceeding with non-trivial Main Sequence work, update the project SDK:
     `mainsequence project update-sdk --path .`
-12. After updating the SDK, refresh the installed Main Sequence scaffold files:
+12. After updating the SDK, compare `mainsequence --version` with
+    `.agents/skills/mainsequence/PINNED_FROM.txt` field `pinned_version=...`.
+13. If `PINNED_FROM.txt` is missing or `pinned_version` differs from the installed
+    SDK version, refresh the managed scaffold files:
     `mainsequence project update AGENTS.md --path .`
     `mainsequence project update_agent_skills --path .`
-13. Verify platform state with the CLI or platform tooling instead of guessing.
+14. If `pinned_version` already matches the installed SDK version, do not refresh
+    `AGENTS.md` or `.agents/skills/mainsequence/` as a startup ritual.
+15. Verify platform state with the CLI or platform tooling instead of guessing.
 
 ## Orchestrator Rule
 

{mainsequence-4.4.5 → mainsequence-4.4.10}/agent_scaffold/skills/application_surfaces/api_surfaces/SKILL.md

@@ -51,7 +51,11 @@ This skill must not claim ownership of:
 - Command Center workspaces:
   `.agents/skills/mainsequence/command_center/workspace_builder/SKILL.md`
 - AppComponents and custom forms:
-  `.agents/skills/mainsequence/command_center/app_components/SKILL.md`
+  `.agents/skills/mainsequence/command_center/widgets/app_components/SKILL.md`
+- Command Center table/pro-table response contracts:
+  `.agents/skills/mainsequence/command_center/widgets/tables/SKILL.md`
+- Command Center tabular transform consumers:
+  `.agents/skills/mainsequence/command_center/widgets/tabular_transform/SKILL.md`
 - Adapter from API provider-side Command Center connection endpoints:
   `.agents/skills/mainsequence/command_center/adapter_from_api/SKILL.md`
 - predeployment mock API contract validation:
@@ -69,14 +73,18 @@ This skill must not claim ownership of:
 4. `docs/knowledge/fastapi/index.md`
 5. `docs/knowledge/command_center/widget_data_contracts.md`
 6. `docs/knowledge/command_center/forms.md`
-7. `.agents/skills/mainsequence/command_center/app_components/SKILL.md`
+7. `.agents/skills/mainsequence/command_center/widgets/app_components/SKILL.md`
 
 Also load:
 
 8. `.agents/skills/mainsequence/command_center/workspace_builder/SKILL.md` when the API is tied to mounted widgets, workspace payloads, or workspace mutation
-9. `.agents/skills/mainsequence/command_center/adapter_from_api/SKILL.md` when the API must be consumed through a Command Center Adapter from API connection
-10. `.agents/skills/mainsequence/command_center/api_mock_prototyping/SKILL.md` when the contract should be validated in AppComponent mock mode before backend deployment
-11. `.agents/skills/mainsequence/platform_operations/orchestration_and_releases/SKILL.md` when the API must become usable from Command Center or an AppComponent
+9. `.agents/skills/mainsequence/command_center/widgets/tables/SKILL.md` when the API returns
+   `core.tabular_frame@v1`, `meta.tableVisuals`, or table/pro-table widget-facing data
+10. `.agents/skills/mainsequence/command_center/widgets/tabular_transform/SKILL.md` when the API
+    response will be reshaped by `core__tabular-transform`
+11. `.agents/skills/mainsequence/command_center/adapter_from_api/SKILL.md` when the API must be consumed through a Command Center Adapter from API connection
+12. `.agents/skills/mainsequence/command_center/api_mock_prototyping/SKILL.md` when the contract should be validated in AppComponent mock mode before backend deployment
+13. `.agents/skills/mainsequence/platform_operations/orchestration_and_releases/SKILL.md` when the API must become usable from Command Center or an AppComponent
 
 Do not wait for the user to say "Command Center" explicitly if the API is being built as a platform UI surface. That is the default assumption in Main Sequence projects.
 
@@ -138,7 +146,7 @@ In a Main Sequence project, assume API work is for Command Center unless the use
 That means:
 
 - prefer widget-facing contracts by default
-- load `.agents/skills/mainsequence/command_center/app_components/SKILL.md`
+- load `.agents/skills/mainsequence/command_center/widgets/app_components/SKILL.md`
 - also load `.agents/skills/mainsequence/command_center/workspace_builder/SKILL.md` when the API is coupled to mounted workspace widgets or workspace payloads
 - load `.agents/skills/mainsequence/command_center/adapter_from_api/SKILL.md` when the API will be consumed by connection-first workspace dataflow
 - try to use the existing Command Center SDK response model before inventing a new response shape

{mainsequence-4.4.5 → mainsequence-4.4.10}/agent_scaffold/skills/command_center/adapter_from_api/SKILL.md

@@ -33,6 +33,105 @@ frontend/editor tooling or a future explicit transform, but the current backend
 hot-path validate, extract JSONPath rows, coerce schemas, or reshape provider responses because a
 mapping exists.
 
+## Connection CLI And Transport Modes
+
+Use the Main Sequence CLI to create or update the Adapter from API connection instance that points
+Command Center at the provider API.
+
+Backend/deployed API mode:
+
+```bash
+mainsequence cc connection create-adapter-from-api \
+  --name "Provider API" \
+  --api-base-url https://api.example.com \
+  --workspace-uid <workspace-uid> \
+  --default
+```
+
+Direct local/tunnel development mode:
+
+```bash
+cloudflared tunnel --url http://127.0.0.1:8021
+
+mainsequence cc connection create-adapter-from-api \
+  --name "Provider API local" \
+  --debug-api-base-url https://example.trycloudflare.com \
+  --workspace-uid <workspace-uid> \
+  --default
+```
+
+Patch an existing Adapter from API connection:
+
+```bash
+mainsequence cc connection patch-adapter-from-api <connection-uid> \
+  --api-base-url https://api.example.com
+
+mainsequence cc connection patch-adapter-from-api <connection-uid> \
+  --debug-api-base-url https://example.trycloudflare.com
+```
+
+Inspect connection state:
+
+```bash
+mainsequence cc connection list --filter type_id=command_center.adapter_from_api
+mainsequence cc connection detail <connection-uid>
+```
+
+CLI characteristics:
+
+- `--api-base-url` creates backend mode public config with `apiBaseUrl`.
+- `--debug-api-base-url` creates direct mode public config with `transportMode=direct`,
+  `debugApiBaseUrl`, `compiledContractSource=direct`, and derived contract/OpenAPI URLs.
+- `--public-config-json` and `--public-config-file` accept a full publicConfig object when URL
+  options are not enough.
+- `--config-json` and `--config-file` set public non-secret `configValues`.
+- `--secure-config-json` and `--secure-config-file` send secret values as `secureConfig`; returned
+  connection details expose only `secureFields`, not the raw secret values.
+- `patch-adapter-from-api` must target an existing `command_center.adapter_from_api` connection; do
+  not use it for other connection types.
+- Do not include `applicationBindings` in Adapter from API public config. The
+  `AdapterFromApiConnectionPublicConfig` model rejects it.
+
+Direct mode is critical during development. It lets a workspace test the connection against a local
+API before any resource release or API deployment. Run the local API, expose it with a Cloudflare
+tunnel, create or patch the connection with `--debug-api-base-url`, and validate the workspace
+connection/query flow directly. This avoids constant API deployments while iterating on the
+contract, operation metadata, response shape, and widget behavior. Switch to `--api-base-url` only
+when the deployed API is ready to be the stable backend target.
+
+## SDK Helper Modules
+
+Provider code should use the Command Center SDK helpers instead of hand-building the well-known
+contract when the project can depend on `mainsequence-sdk`:
+
+```python
+from mainsequence.client.command_center.contracts.adapter_from_api import (
+    AdapterFromApiConfigVariable,
+    AdapterFromApiParameter,
+    AdapterFromApiSecretInjection,
+    AdapterFromApiSecretVariable,
+)
+from mainsequence.client.command_center.contracts.response_mapping import (
+    make_tabular_response_mapping,
+)
+from mainsequence.client.command_center.contracts.tabular import make_tabular_frame
+from mainsequence.client.command_center.providers.adapter_from_api import (
+    make_health_operation,
+    make_provider_contract,
+    make_query_operation,
+)
+```
+
+Use:
+
+- `contracts.adapter_from_api` for strict provider contract, operation, config variable, and secret
+  variable models
+- `providers.adapter_from_api` for `make_health_operation`, `make_query_operation`, and
+  `make_provider_contract`
+- `contracts.response_mapping` for optional `responseMappings` metadata
+- `contracts.tabular` for canonical `core.tabular_frame@v1` response helpers such as
+  `make_tabular_frame`
+
 ## Scope
 
 This skill owns:
@@ -50,7 +149,7 @@ This skill does not own:
 
 - general FastAPI project structure
 - unrelated API routes for non-Command Center clients
-- Command Center connection instance creation
+- general Command Center connection management beyond the Adapter from API CLI workflow above
 - workspace layout or widget mounting
 - backend adapter runtime internals
 - resource release or deployment orchestration
@@ -65,8 +164,10 @@ Route those concerns to the adjacent skills below.
   `.agents/skills/mainsequence/command_center/connections/SKILL.md`
 - Workspace widgets and binding:
   `.agents/skills/mainsequence/command_center/workspace_builder/SKILL.md`
+- Table/pro-table output contracts and `meta.tableVisuals` metadata:
+  `.agents/skills/mainsequence/command_center/widgets/tables/SKILL.md`
 - AppComponent form-driven actions:
-  `.agents/skills/mainsequence/command_center/app_components/SKILL.md`
+  `.agents/skills/mainsequence/command_center/widgets/app_components/SKILL.md`
 - API mock/prototype validation before deployment:
   `.agents/skills/mainsequence/command_center/api_mock_prototyping/SKILL.md`
 - FastAPI resources, images, jobs, and releases:
@@ -264,6 +365,7 @@ For FastAPI providers in Main Sequence repos, full canonical frame endpoints mus
 
 ```python
 from mainsequence.client.command_center.data_models import TabularFrameResponse
+from mainsequence.client.command_center.contracts.tabular import make_tabular_frame
 ```
 
 Declare `response_model=TabularFrameResponse` instead of recreating the canonical frame shape
@@ -354,7 +456,9 @@ Before implementing or revising an API for Adapter from API consumption, decide:
 
 For a FastAPI provider:
 
-- define strict Pydantic models for the Command Center contract
+- use the SDK provider helpers in `mainsequence.client.command_center.providers.adapter_from_api`
+  and strict models in `mainsequence.client.command_center.contracts.adapter_from_api` when the
+  dependency is available
 - set explicit `operation_id` values on routes
 - expose `GET /.well-known/command-center/connection-contract`
 - expose a zero-argument health route

{mainsequence-4.4.5 → mainsequence-4.4.10}/agent_scaffold/skills/command_center/api_mock_prototyping/SKILL.md

@@ -44,9 +44,11 @@ This skill must not claim ownership of:
 ## Route Adjacent Work
 
 - AppComponents and custom forms:
-  `.agents/skills/mainsequence/command_center/app_components/SKILL.md`
+  `.agents/skills/mainsequence/command_center/widgets/app_components/SKILL.md`
 - Command Center workspaces and widget mutation:
   `.agents/skills/mainsequence/command_center/workspace_builder/SKILL.md`
+- Tabular transform widgets for downstream reshaping in mock validation:
+  `.agents/skills/mainsequence/command_center/widgets/tabular_transform/SKILL.md`
 - APIs and FastAPI:
   `.agents/skills/mainsequence/application_surfaces/api_surfaces/SKILL.md`
 - Jobs, images, resources, and releases:
@@ -61,7 +63,7 @@ This skill must not claim ownership of:
 2. The SDK client models:
    - `mainsequence/client/command_center/app_component.py`
    - `mainsequence/client/command_center/workspace.py`
-3. `.agents/skills/mainsequence/command_center/app_components/SKILL.md`
+3. `.agents/skills/mainsequence/command_center/widgets/app_components/SKILL.md`
 4. `.agents/skills/mainsequence/command_center/workspace_builder/SKILL.md`
 
 Only after the mock contract is stable:

{mainsequence-4.4.5 → mainsequence-4.4.10}/agent_scaffold/skills/command_center/connections/SKILL.md

@@ -24,6 +24,11 @@ connection instance and query model are known.
 ## This Skill Can Do
 
 - discover connection types and instances through `mainsequence.client.command_center.connections`
+- use `mainsequence.client.command_center.widgets.connection_query` for connection-query source
+  widget payload drafts
+- use `mainsequence.client.command_center.contracts.*` and
+  `mainsequence.client.command_center.providers.*` when validating Adapter from API provider
+  contracts
 - decide whether an existing connection instance can support the requested workspace data
 - inspect `ConnectionType.queryModels` and `usageGuidance`
 - verify that a query model can publish the required output contract
@@ -48,10 +53,14 @@ This skill must not claim ownership of:
   `.agents/skills/mainsequence/command_center/workspace_design/SKILL.md`
 - Workspace JSON creation and widget mutation:
   `.agents/skills/mainsequence/command_center/workspace_builder/SKILL.md`
+- Table/pro-table consumer contracts, table visual metadata, selection, and live update behavior:
+  `.agents/skills/mainsequence/command_center/widgets/tables/SKILL.md`
+- Tabular transform consumer contracts and source/live update bindings:
+  `.agents/skills/mainsequence/command_center/widgets/tabular_transform/SKILL.md`
 - Adapter from API connection workflow:
   `.agents/skills/mainsequence/command_center/adapter_from_api/SKILL.md`
 - AppComponent forms and action API contracts:
-  `.agents/skills/mainsequence/command_center/app_components/SKILL.md`
+  `.agents/skills/mainsequence/command_center/widgets/app_components/SKILL.md`
 - API implementation:
   `.agents/skills/mainsequence/application_surfaces/api_surfaces/SKILL.md`
 - Jobs, images, resources, and releases:
@@ -63,6 +72,22 @@ This skill must not claim ownership of:
    - `mainsequence/client/command_center/connections.py`
    - `mainsequence/client/command_center/data_models.py` when validating `core.tabular_frame@v1`
      output shape
+   - `mainsequence/client/command_center/contracts/adapter_from_api.py` when validating provider
+     discovery contracts
+   - `mainsequence/client/command_center/contracts/response_mapping.py` when validating
+     response-mapping metadata
+   - `mainsequence/client/command_center/contracts/tabular.py` when building or checking canonical
+     tabular frames
+   - `mainsequence/client/command_center/contracts/table_visuals.py` when table-specific visual
+     defaults travel with `meta.tableVisuals`
+   - `mainsequence/client/command_center/providers/adapter_from_api.py` when a provider should use
+     SDK contract builders
+   - `mainsequence/client/command_center/widgets/connection_query.py` when creating
+     connection-query source widget payloads
+   - `mainsequence/client/command_center/widgets/tabular_transform.py` when a connection-backed
+     flow needs a `core__tabular-transform` widget
+   - `mainsequence/client/command_center/widgets/bindings.py` when binding seed data or live updates
+     into the transform
 2. Widget registry detail for the source and consumer widgets:
    - `mainsequence cc registered_widget_type list --json`
    - `mainsequence cc registered_widget_type detail <WIDGET_ID> --json`

{mainsequence-4.4.5/agent_scaffold/skills/command_center → mainsequence-4.4.10/agent_scaffold/skills/command_center/widgets}/app_components/SKILL.md

@@ -47,6 +47,8 @@ This skill must not claim ownership of:
 
 - Command Center workspaces:
   `.agents/skills/mainsequence/command_center/workspace_builder/SKILL.md`
+- Command Center table/pro-table output contracts and table visual metadata:
+  `.agents/skills/mainsequence/command_center/widgets/tables/SKILL.md`
 - predeployment mock API contract validation:
   `.agents/skills/mainsequence/command_center/api_mock_prototyping/SKILL.md`
 - APIs and FastAPI:
@@ -71,17 +73,19 @@ This skill must not claim ownership of:
 2. `docs/knowledge/command_center/forms.md`
 3. `docs/knowledge/command_center/widget_data_contracts.md`
 4. `mainsequence/client/command_center/app_component.py`
-5. `.agents/skills/mainsequence/command_center/adapter_from_api/SKILL.md` when API-shaped data must become a connection-backed tabular dataset
-6. `.agents/skills/mainsequence/command_center/connections/SKILL.md` when AppComponent output will be consumed by generic tabular widgets or must align with connection-first dataflow
+5. `.agents/skills/mainsequence/command_center/widgets/tables/SKILL.md` when AppComponent output will feed
+   a table/pro-table widget or needs `core.tabular_frame@v1` plus table visual metadata
+6. `.agents/skills/mainsequence/command_center/adapter_from_api/SKILL.md` when API-shaped data must become a connection-backed tabular dataset
+7. `.agents/skills/mainsequence/command_center/connections/SKILL.md` when AppComponent output will be consumed by generic tabular widgets or must align with connection-first dataflow
 
 If the AppComponent is backed by project APIs, also read:
 
-7. `.agents/skills/mainsequence/application_surfaces/api_surfaces/SKILL.md`
-8. `.agents/skills/mainsequence/platform_operations/orchestration_and_releases/SKILL.md`
+8. `.agents/skills/mainsequence/application_surfaces/api_surfaces/SKILL.md`
+9. `.agents/skills/mainsequence/platform_operations/orchestration_and_releases/SKILL.md`
 
 If the task is about validating the API contract before deployment, also read:
 
-9. `.agents/skills/mainsequence/command_center/api_mock_prototyping/SKILL.md`
+10. `.agents/skills/mainsequence/command_center/api_mock_prototyping/SKILL.md`
 
 ## Inputs This Skill Needs