mainsequence 7.0.2__tar.gz → 8.0.0__tar.gz

{mainsequence-7.0.2/mainsequence.egg-info → mainsequence-8.0.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: mainsequence
-Version: 7.0.2
+Version: 8.0.0
 Summary: Main Sequence SDK 
 Author-email: Main Sequence GmbH <dev@main-sequence.io>
 License-Expression: LicenseRef-MainSequence-Proprietary
@@ -61,7 +61,7 @@ The Main Sequence platform allows you to:
 
 The key idea is that you can focus on development and deployment, while the platform handles the DevOps layer.
 
-## Project Status
+## Repository Status
 
 - Status: actively maintained
 - Last commit: `2026-03-27` - [`6aa5dea`](https://github.com/mainsequence-sdk/mainsequence-sdk/commit/6aa5deab73586226c7b267abf2e3f02f4f7e7669) - `docs logo fix v.3.17.6`
@@ -69,16 +69,16 @@ The key idea is that you can focus on development and deployment, while the plat
 - Documentation: [Documentation Site](https://mainsequence-sdk.github.io/mainsequence-sdk/)
 - Security policy: [SECURITY.md](SECURITY.md)
 - Release history: [CHANGELOG.md](CHANGELOG.md)
-- Major-version migration: [6.x to 7.0 hard cut](docs/migrations/v7-time-index-table-updater-hard-cut.md)
+- Major-version migrations: [Migration guides](docs/migrations/v8-code-repository-ontology.md)
 
 ## What this repository contains
 
-This repository contains the SDK and the documentation used to build and operate Main Sequence projects.
+This repository contains the SDK and documentation used to build and operate Main Sequence CodeRepositories.
 
 Main package areas:
 
 - `mainsequence.meta_tables`: `MetaTable`s, `TimeIndexTableUpdater`s, update workflows, and persistence
-- `mainsequence.client`: API client models for projects, jobs, time-index tables, sharing, and platform resources
+- `mainsequence.client`: API client models for CodeRepositories, jobs, time-index tables, sharing, and platform resources
 - `mainsequence.cli`: the `mainsequence` command-line interface
 
 Repository areas:
@@ -97,7 +97,7 @@ The documentation is organized into three reading modes:
 Recommended entry points:
 
 - Beginner tutorial:
-  - [MainSequence SDK tutorial Project](https://github.com/mainsequence-projects/mainsequence-sdk-tutorial)
+  - [MainSequence SDK tutorial CodeRepository](https://github.com/mainsequence-projects/mainsequence-sdk-tutorial)
 - Knowledge:
   - [Time-Index Table Updaters](docs/knowledge/time_index_table_updates.md)
   - [MetaTables](docs/knowledge/meta_tables/index.md)
@@ -105,6 +105,7 @@ Recommended entry points:
   - [Scheduling Jobs](docs/knowledge/infrastructure/scheduling_jobs.md)
   - [Streamlit Dashboards](docs/knowledge/dashboards/streamlit/index.md)
 - Migrations:
+  - [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:
   - [CLI Overview](docs/cli/index.md)
@@ -129,24 +130,24 @@ session with `mainsequence login --mcp`, then call the printed
 callback URI; tokens return directly to the CLI and are never exposed through
 MCP.
 
-Check that you can see your projects:
+Check that you can see your CodeRepositories:
 
 ```bash
-mainsequence project list
+mainsequence code-repository list
 ```
 
-Create a new project:
+Create a new CodeRepository:
 
 ```bash
-mainsequence project create my-first-project
+mainsequence code-repository create my-first-repository
 ```
 
 Set it up locally:
 
 ```bash
-mainsequence project set-up-locally <PROJECT_ID>
-cd my-first-project
-mainsequence project build_local_venv --path .
+mainsequence code-repository set-up-locally <CODE_REPOSITORY_UID>
+cd my-first-repository
+mainsequence code-repository build-local-venv --path .
 ```
 
 From there, the normal learning path is:
@@ -157,7 +158,7 @@ From there, the normal learning path is:
 4. add an API or another application surface
 5. schedule jobs
 6. build dashboards or downstream consumers
-7. package the project as an agent-facing surface when the repository is ready
+7. package the CodeRepository as an agent-facing surface when it is ready
 
 ## Installation for development
 
@@ -213,13 +214,13 @@ black .
 
 If you are evaluating the platform:
 
-- start with the separate canonical tutorial Project linked above
+- start with the separate canonical tutorial CodeRepository linked above
 
 If you are building a feature and already know the area:
 
 - go straight to the relevant guide in `docs/knowledge/`
 
-If you are operating projects day to day:
+If you are operating CodeRepositories day to day:
 
 - use `docs/cli/` and the `mainsequence --help` command tree
 
@@ -233,7 +234,7 @@ If you need the exact SDK surface:
 - Python: `>=3.13`
 - CLI entry point: `mainsequence`
 
-Project metadata is defined in [pyproject.toml](pyproject.toml).
+Package metadata is defined in [pyproject.toml](pyproject.toml).
 
 ## License
 

{mainsequence-7.0.2 → mainsequence-8.0.0}/README.md

@@ -19,7 +19,7 @@ The Main Sequence platform allows you to:
 
 The key idea is that you can focus on development and deployment, while the platform handles the DevOps layer.
 
-## Project Status
+## Repository Status
 
 - Status: actively maintained
 - Last commit: `2026-03-27` - [`6aa5dea`](https://github.com/mainsequence-sdk/mainsequence-sdk/commit/6aa5deab73586226c7b267abf2e3f02f4f7e7669) - `docs logo fix v.3.17.6`
@@ -27,16 +27,16 @@ The key idea is that you can focus on development and deployment, while the plat
 - Documentation: [Documentation Site](https://mainsequence-sdk.github.io/mainsequence-sdk/)
 - Security policy: [SECURITY.md](SECURITY.md)
 - Release history: [CHANGELOG.md](CHANGELOG.md)
-- Major-version migration: [6.x to 7.0 hard cut](docs/migrations/v7-time-index-table-updater-hard-cut.md)
+- Major-version migrations: [Migration guides](docs/migrations/v8-code-repository-ontology.md)
 
 ## What this repository contains
 
-This repository contains the SDK and the documentation used to build and operate Main Sequence projects.
+This repository contains the SDK and documentation used to build and operate Main Sequence CodeRepositories.
 
 Main package areas:
 
 - `mainsequence.meta_tables`: `MetaTable`s, `TimeIndexTableUpdater`s, update workflows, and persistence
-- `mainsequence.client`: API client models for projects, jobs, time-index tables, sharing, and platform resources
+- `mainsequence.client`: API client models for CodeRepositories, jobs, time-index tables, sharing, and platform resources
 - `mainsequence.cli`: the `mainsequence` command-line interface
 
 Repository areas:
@@ -55,7 +55,7 @@ The documentation is organized into three reading modes:
 Recommended entry points:
 
 - Beginner tutorial:
-  - [MainSequence SDK tutorial Project](https://github.com/mainsequence-projects/mainsequence-sdk-tutorial)
+  - [MainSequence SDK tutorial CodeRepository](https://github.com/mainsequence-projects/mainsequence-sdk-tutorial)
 - Knowledge:
   - [Time-Index Table Updaters](docs/knowledge/time_index_table_updates.md)
   - [MetaTables](docs/knowledge/meta_tables/index.md)
@@ -63,6 +63,7 @@ Recommended entry points:
   - [Scheduling Jobs](docs/knowledge/infrastructure/scheduling_jobs.md)
   - [Streamlit Dashboards](docs/knowledge/dashboards/streamlit/index.md)
 - Migrations:
+  - [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:
   - [CLI Overview](docs/cli/index.md)
@@ -87,24 +88,24 @@ session with `mainsequence login --mcp`, then call the printed
 callback URI; tokens return directly to the CLI and are never exposed through
 MCP.
 
-Check that you can see your projects:
+Check that you can see your CodeRepositories:
 
 ```bash
-mainsequence project list
+mainsequence code-repository list
 ```
 
-Create a new project:
+Create a new CodeRepository:
 
 ```bash
-mainsequence project create my-first-project
+mainsequence code-repository create my-first-repository
 ```
 
 Set it up locally:
 
 ```bash
-mainsequence project set-up-locally <PROJECT_ID>
-cd my-first-project
-mainsequence project build_local_venv --path .
+mainsequence code-repository set-up-locally <CODE_REPOSITORY_UID>
+cd my-first-repository
+mainsequence code-repository build-local-venv --path .
 ```
 
 From there, the normal learning path is:
@@ -115,7 +116,7 @@ From there, the normal learning path is:
 4. add an API or another application surface
 5. schedule jobs
 6. build dashboards or downstream consumers
-7. package the project as an agent-facing surface when the repository is ready
+7. package the CodeRepository as an agent-facing surface when it is ready
 
 ## Installation for development
 
@@ -171,13 +172,13 @@ black .
 
 If you are evaluating the platform:
 
-- start with the separate canonical tutorial Project linked above
+- start with the separate canonical tutorial CodeRepository linked above
 
 If you are building a feature and already know the area:
 
 - go straight to the relevant guide in `docs/knowledge/`
 
-If you are operating projects day to day:
+If you are operating CodeRepositories day to day:
 
 - use `docs/cli/` and the `mainsequence --help` command tree
 
@@ -191,7 +192,7 @@ If you need the exact SDK surface:
 - Python: `>=3.13`
 - CLI entry point: `mainsequence`
 
-Project metadata is defined in [pyproject.toml](pyproject.toml).
+Package metadata is defined in [pyproject.toml](pyproject.toml).
 
 ## License
 

{mainsequence-7.0.2 → mainsequence-8.0.0}/agent_scaffold/AGENTS.md

@@ -1,33 +1,33 @@
 # AGENTS.md
 
-You are a dual-mandate agent. Follow the project-specific instructions in this file and the
+You are a dual-mandate agent. Follow the repository-specific instructions in this file and the
 relevant skills, while also keeping in mind that application surfaces, data, and implementation
 operate within the Main Sequence platform and must follow Main Sequence platform instructions.
 
-## Project-Specific Instructions
+## Repository-Specific Instructions
 
-[ HERE SHOULD BE THE PROJECT-SPECIFIC ACTIONS, RULES, CONTEXT, AND LOCAL NOTES. DO NOT REMOVE
-THIS LINE UNLESS YOU REPLACE IT WITH REAL PROJECT-SPECIFIC CONTENT. ]
+[ HERE SHOULD BE THE REPOSITORY-SPECIFIC ACTIONS, RULES, CONTEXT, AND LOCAL NOTES. DO NOT REMOVE
+THIS LINE UNLESS YOU REPLACE IT WITH REAL REPOSITORY-SPECIFIC CONTENT. ]
 
 Do not remove the `<!-- mainsequence-agent-scaffold:start schema=1 source=agent_scaffold -->`
-or `<!-- mainsequence-agent-scaffold:end -->` markers. `mainsequence project update AGENTS.md`
+or `<!-- mainsequence-agent-scaffold:end -->` markers. `mainsequence code-repository update AGENTS.md`
 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, then compare the
+Before any non-trivial Main Sequence work, update the CodeRepository SDK first, then compare the
 installed SDK version with the managed skills pin:
 
-- `mainsequence project update-sdk --path .`
+- `mainsequence code-repository update-sdk --path .`
 
 After the SDK update, inspect `.agents/skills/mainsequence/PINNED_FROM.txt`.
 The schema-2 record describes both sources installed by
-`mainsequence project update_agent_skills`:
+`mainsequence code-repository update-agent-skills`:
 
 - `sdk_version=...` and `sdk_skills_path=...` identify the SDK-owned execution
-  skills copied from the target project's installed SDK;
+  skills copied from the target code repository's installed SDK;
 - `platform_manifest_version=...`, `platform_manifest_sha256=...`,
   `platform_ontology_sha256=...`, and the
   `platform_resource.<name>.*` fields identify the platform-owned ontology and
@@ -40,8 +40,8 @@ Compare the SDK value with the installed version reported by
 Refresh the managed scaffold only when `PINNED_FROM.txt` is missing or its
 `pinned_version` differs from the installed SDK version:
 
-- `mainsequence project update_agent_skills --path .`
-- `mainsequence project update AGENTS.md --path .`
+- `mainsequence code-repository update-agent-skills --path .`
+- `mainsequence code-repository update AGENTS.md --path .`
 
 If `sdk_version` already matches the installed SDK version and no explicit
 platform-skill refresh is needed, do not refresh `AGENTS.md` or
@@ -66,7 +66,7 @@ Core responsibilities:
   - 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 project-owned code and
+    - 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 scheduled execution, releases, and backend operations, use jobs, images, resources, and
     other platform objects through the proper platform skills
@@ -74,7 +74,7 @@ Core responsibilities:
 - route each part of the work to the correct repository skill instead of improvising across domains
 - use the `mainsequence` CLI as the default control surface for backend and platform interaction
 - 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
+  dashboards, jobs, and other repository components instead of duplicating logic in integration
   layers
 - use the bug auditor skill for blocker and SDK/platform issue assessment
 
@@ -85,7 +85,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 project-owned Streamlit app or a reusable Command
+- confirm whether a visualization should be a repository-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
@@ -185,18 +185,18 @@ Use the latest relevant documentation or specialized skill for the task at hand.
 
 Typical routing:
 
-- project architecture, ontology, and Project Blueprint:
+- product architecture, ontology, and Project Blueprint:
   `.agents/skills/mainsequence/project_design/SKILL.md`
-- project setup, local checkout, CLI environment, scaffolding, and standard
+- CodeRepository setup, local checkout, CLI environment, scaffolding, and standard
   repository layout:
-  `.agents/skills/mainsequence/sdk_project_execution/SKILL.md`
-- local environment repair, project authentication refresh, SDK updates,
-  managed skill refresh, and canonical project sync:
-  `.agents/skills/mainsequence/maintenance/project-maintenance/SKILL.md`
-- turning an existing project into a project-backed coding agent, defining
-  project-owned skills, and authoring `.agents/agent_card.json`:
-  `.agents/skills/mainsequence/project_to_agent/SKILL.md`
-- project status audits, blocker analysis, failure classification, and upstream SDK assessment:
+  `.agents/skills/mainsequence/sdk_code_repository_execution/SKILL.md`
+- local environment repair, CodeRepository authentication refresh, SDK updates,
+  managed skill refresh, and canonical CodeRepository sync:
+  `.agents/skills/mainsequence/maintenance/code_repository_maintenance/SKILL.md`
+- turning an existing CodeRepository into a code-repository-backed coding agent, defining
+  repository-owned skills, and authoring `.agents/agent_card.json`:
+  `.agents/skills/mainsequence/code_repository_to_agent/SKILL.md`
+- CodeRepository status audits, blocker analysis, failure classification, and upstream SDK assessment:
   `.agents/skills/mainsequence/maintenance/bug_auditor/SKILL.md`
 - TimeIndexTableUpdaters, updates, identifiers, schema, metadata:
   `.agents/skills/mainsequence/data_publishing/time_index_table_updates/SKILL.md`
@@ -206,14 +206,14 @@ Typical routing:
   `.agents/skills/mainsequence/data_access/exploration/SKILL.md`
 - FastAPI APIs serving the Command Center frontend and their release lifecycle:
   `.agents/skills/mainsequence/application_surfaces/api_surfaces/SKILL.md`
-- jobs, schedules, images, project resources, releases, and Artifacts:
+- jobs, schedules, images, code repository resources, releases, and Artifacts:
   `.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 project work, not a separate Main
+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.
 
@@ -223,15 +223,15 @@ For any non-trivial Main Sequence task:
 
 1. Read the latest relevant Main Sequence documentation.
 2. Compare the implementation against the latest documented behavior.
-3. Confirm you are in the correct project checkout, or use `--path` explicitly.
+3. Confirm you are in the correct CodeRepository checkout, or use `--path` explicitly.
 4. Confirm platform context with:
-   `mainsequence project current --debug`
+   `mainsequence code-repository current --debug`
 5. Before validations or live checks, run:
-   `mainsequence project refresh_token --path .`
+   `mainsequence code-repository refresh-token --path .`
 6. If git push or pull is required, use:
-    `mainsequence project open-signed-terminal <PROJECT_ID>`
-7. Before proceeding with non-trivial Main Sequence work, update the project SDK:
-    `mainsequence project update-sdk --path .`
+    `mainsequence code-repository open-signed-terminal <CODE_REPOSITORY_UID>`
+7. Before proceeding with non-trivial Main Sequence work, update the CodeRepository SDK:
+    `mainsequence code-repository update-sdk --path .`
 8. After updating the SDK, compare `mainsequence --version` with
     `.agents/skills/mainsequence/PINNED_FROM.txt` field `sdk_version=...`
     (`pinned_version=...` is its compatibility alias), and verify that the
@@ -239,8 +239,8 @@ For any non-trivial Main Sequence task:
 9. If `PINNED_FROM.txt` is missing, `sdk_version` differs from the installed
     SDK version, or a platform-skill refresh is explicitly required, refresh
     the managed scaffold files:
-    `mainsequence project update_agent_skills --path .`
-    `mainsequence project update AGENTS.md --path .`
+    `mainsequence code-repository update-agent-skills --path .`
+    `mainsequence code-repository update AGENTS.md --path .`
 10. If `sdk_version` already matches the installed SDK version and no platform
     refresh is required, do not refresh `AGENTS.md` or
     `.agents/skills/mainsequence/` as a startup ritual.
@@ -253,21 +253,21 @@ Use the skills as an orchestrated sequence, not as isolated documents.
 Default pattern:
 
 1. `.agents/skills/mainsequence/project_design/SKILL.md`
-2. `.agents/skills/mainsequence/sdk_project_execution/SKILL.md`
+2. `.agents/skills/mainsequence/sdk_code_repository_execution/SKILL.md`
 3. the relevant domain skill
 
-When the intended project surface is a project-backed coding agent, apply
-`.agents/skills/mainsequence/project_to_agent/SKILL.md` after the relevant
-project behavior exists and has been verified. The repository source card is
+When the intended repository surface is a code-repository-backed coding agent, apply
+`.agents/skills/mainsequence/code_repository_to_agent/SKILL.md` after the relevant
+repository behavior exists and has been verified. The repository source card is
 not the runtime A2A Agent Card; the deployed runtime supplies its concrete
 interfaces and security declarations.
 
 Use `.agents/skills/mainsequence/project_design/SKILL.md` as the platform
 source of truth for intent and ontology. Use
-`.agents/skills/mainsequence/sdk_project_execution/SKILL.md` for installed-SDK,
+`.agents/skills/mainsequence/sdk_code_repository_execution/SKILL.md` for installed-SDK,
 CLI, filesystem, and local repository execution mechanics. Use
-`.agents/skills/mainsequence/maintenance/project-maintenance/SKILL.md` for
-repeatable environment, authentication, SDK, scaffold-refresh, and project-sync
+`.agents/skills/mainsequence/maintenance/code_repository_maintenance/SKILL.md` for
+repeatable environment, authentication, SDK, scaffold-refresh, and CodeRepository-sync
 routines.
 
 ## Core Working Rules
@@ -292,23 +292,23 @@ When platform state matters, verify it with the CLI and/or platform UI.
 
 At minimum, verify relevant:
 
-- current project selection
+- current code repository selection
 - data availability
 - jobs
 - job runs and logs
-- project images
+- code repository images
 - dashboard or agent resources/releases
 - data assets
-- related platform objects used by the project
+- related platform objects used by the CodeRepository
 
 Typical verification commands:
 
-- `mainsequence project current --debug`
-- `mainsequence project jobs list`
-- `mainsequence project jobs runs list <JOB_UID>`
-- `mainsequence project jobs runs logs <JOB_RUN_UID> --max-wait-seconds 900`
-- `mainsequence project images list`
-- `mainsequence project project_resource list`
+- `mainsequence code-repository current --debug`
+- `mainsequence code-repository jobs list`
+- `mainsequence code-repository jobs runs list <JOB_UID>`
+- `mainsequence code-repository jobs runs logs <JOB_RUN_UID> --max-wait-seconds 900`
+- `mainsequence code-repository images list`
+- `mainsequence code-repository resources list`
 
 If live verification is not possible:
 
@@ -318,7 +318,7 @@ If live verification is not possible:
 
 ## Dependency Management Rules
 
-Manage project Python dependencies with `uv`.
+Manage CodeRepository Python dependencies with `uv`.
 
 Rules:
 
@@ -326,16 +326,16 @@ Rules:
 - add development-only libraries with `uv add --dev <package>`
 - do not edit dependency declarations or lockfiles manually when `uv` should manage them
 - do not treat `requirements.txt` as the source of truth for dependency changes
-- when dependency changes matter to the project runtime, keep the `uv`-managed project files and
+- when dependency changes matter to the CodeRepository runtime, keep the `uv`-managed package files and
   exported requirements in sync
 
 ## Documentation Rules
 
-- all formal project documentation must live under `docs/`
+- all formal CodeRepository documentation must live under `docs/`
 - documentation must remain MkDocs-compatible
 - keep `docs/SUMMARY.md` aligned with the docs structure
 - the root `README.md` must remain the entry point and documentation map
-- every major project area must have its own page under `docs/`
+- every major CodeRepository area must have its own page under `docs/`
 - operational and verification procedures must be documented under `docs/`
 - any new feature, workflow, component, or integration must be reflected in documentation
 

{mainsequence-7.0.2 → mainsequence-8.0.0}/agent_scaffold/skills/a2a_sdk_execution/SKILL.md

@@ -49,7 +49,7 @@ mainsequence agent search "<discoveryPrompt>" \
 ```
 
 Use the canonical Organization Environment UID associated with the target
-ProjectBranch. It scopes discovery only; it does not create, assign, or override an
+CodeRepositoryBranch. It scopes discovery only; it does not create, assign, or override an
 Agent's environment.
 
 4. Treat the CLI output as authoritative.
@@ -341,7 +341,7 @@ handle for a different task or conversation.
 ### Runtime-Owned Child Or Executor Agent
 
 - May use bounded A2A within the active task scope without separate user confirmation.
-- Should keep the request tightly scoped to the current project or active task.
+- Should keep the request tightly scoped to the current CodeRepository or active task.
 
 ## A2A Response Behavior
 

{mainsequence-7.0.2 → mainsequence-8.0.0}/agent_scaffold/skills/application_surfaces/api_surfaces/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: mainsequence-command-center-fastapi
-description: Build, contract-test, release, and verify a FastAPI project resource that serves the Command Center frontend. Use when a Main Sequence API must implement a wire contract defined by the mainsequence-sdk/command-center-sdk GitHub repository and then move through local testing, project sync, image and resource resolution, FastAPI ResourceRelease creation, and deployed frontend validation.
+description: Build, contract-test, release, and verify a FastAPI code repository resource that serves the Command Center frontend. Use when a Main Sequence API must implement a wire contract defined by the mainsequence-sdk/command-center-sdk GitHub repository and then move through local testing, code-repository sync, image and resource resolution, FastAPI ResourceRelease creation, and deployed frontend validation.
 ---
 
 # Command Center FastAPI Release Lifecycle
@@ -94,7 +94,7 @@ Record:
 
 FastAPI releases receive the authenticated human from the Main Sequence
 platform through injected request state. No SDK authentication setup is
-required in project code:
+required in repository code:
 
 ```python
 from fastapi import FastAPI, Request
@@ -132,7 +132,7 @@ Keep Command Center contract-bearing route code focused on transport and
 application behavior:
 
 1. validate request bodies and parameters
-2. invoke project-owned services and Main Sequence data access
+2. invoke repository-owned services and Main Sequence data access
 3. serialize the declared Command Center contract
 4. validate the serialized body against the schema from the selected repository
    commit before it crosses the HTTP boundary
@@ -176,24 +176,24 @@ Adapter From API schema and fixtures at the selected repository commit.
 
 ### 5. Release the tested commit
 
-Before release, verify local project resolution:
+Before release, verify local CodeRepository resolution:
 
 ```bash
-mainsequence project current --debug --json
+mainsequence code-repository current --debug --json
 ```
 
 Then move the tested code through the canonical lifecycle:
 
 ```bash
-mainsequence project sync -m "Release Command Center API"
-mainsequence project images create
-mainsequence project project_resource list --filter resource_type=fastapi
-mainsequence project project_resource create_fastapi
+mainsequence code-repository sync -m "Release Command Center API"
+mainsequence code-repository images create
+mainsequence code-repository resources list --filter resource_type=fastapi
+mainsequence code-repository resources create_fastapi
 ```
 
 Verify that:
 
-- project sync used the intended Git branch
+- code-repository sync used the intended Git branch
 - the selected image contains the exact tested commit
 - resource discovery found the expected FastAPI path at that commit
 - the selected resource UID and image UID refer to the same commit
@@ -226,7 +226,7 @@ Report:
 - implemented contract IDs and schema `$id` values
 - conformance and route-test results
 - local frontend integration path used
-- Git commit, project image UID, project resource UID, and release identity
+- Git commit, code repository image UID, code repository resource UID, and release identity
 - deployed contract validation and Command Center frontend result
 - whether automatic deployment is enabled and why
 

{mainsequence-7.0.2 → mainsequence-8.0.0}/agent_scaffold/skills/data_access/exploration/SKILL.md

@@ -43,7 +43,7 @@ This skill discovers and identifies data. It does not publish, redesign, or defi
 
 ## Route Adjacent Work
 
-- project bootstrap, scaffolding, and routing:
+- CodeRepository bootstrap, scaffolding, and routing:
   `.agents/skills/mainsequence/project_design/SKILL.md`
 - `TimeIndexTableUpdater` creation or modification:
   `.agents/skills/mainsequence/data_publishing/time_index_table_updates/SKILL.md`
@@ -56,7 +56,7 @@ This skill discovers and identifies data. It does not publish, redesign, or defi
 - 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.
+Streamlit dashboard implementation is app-owned repository code, not a Main Sequence scaffold skill.
 
 ## Read First
 
@@ -70,7 +70,7 @@ Streamlit dashboard implementation is app-owned project code, not a Main Sequenc
 Before exploring, collect or infer:
 
 - the business question being asked
-- whether the user is exploring organization-wide data or project-scoped data
+- whether the user is exploring organization-wide data or CodeRepositoryBranch-scoped data
 - whether the target is a published table or a row-oriented table
 - whether the user already knows an identifier, keyword, or object UID
 - whether metadata discovery alone answers the question
@@ -155,9 +155,9 @@ field to filter by:
 - `mainsequence time-index-table detail <TIME_INDEX_META_TABLE_UID>`
 
 Collection listing is scoped to one Organization Environment. Inside a
-registered project checkout, the CLI derives that scope from the process-frozen
-Git-resolved ProjectBranch. Do not pass an Environment UID or branch UID. On an
-unregistered branch, table operations fail when they require ProjectBranch
+registered CodeRepository checkout, the CLI derives that scope from the process-frozen
+Git-resolved CodeRepositoryBranch. Do not pass an Environment UID or branch UID. On an
+unregistered branch, table operations fail when they require CodeRepositoryBranch
 context while unrelated local development remains available.
 
 Column lookup is also a different path. Use it only for schema-name discovery,

{mainsequence-7.0.2 → mainsequence-8.0.0}/agent_scaffold/skills/data_publishing/meta_table_migrations/SKILL.md

@@ -32,7 +32,7 @@ platform-managed application tables outside the migration workflow.
 - Which provider-scoped MetaTable models belong in `metatable_models`?
 - Does a dynamic provider need `metadata_for_models(...)` instead of full
   package metadata?
-- Does the project need an `after_register_metatables` catalog hook, and does
+- Does the CodeRepository need an `after_register_metatables` catalog hook, and does
   that hook use `context.metatable_models` and `context.registered_metatables`
   instead of importing a broader registry?
 
@@ -119,7 +119,7 @@ platform-managed, Alembic-managed reservations and are validated before HTTP.
   and SDK provider APIs.
 - Do not call platform-managed model `.register()` in normal application code.
   Registration is reserved for the migration workflow.
-- Resolve Project/Git context once per CLI operation and reuse it for the
+- Resolve CodeRepository/Git context once per CLI operation and reuse it for the
   registry reservation, provider reservations, and migration credential.
 - Reject a returned registry unless it is a platform-managed,
   Alembic-managed root in `reserved` or `active` state. Do not silently reuse a
@@ -134,7 +134,7 @@ platform-managed, Alembic-managed reservations and are validated before HTTP.
 - If `current` fails before Alembic runs, inspect the provider import path and
   Alembic version MetaTable binding. Confirm the registry reservation is
   `platform_managed` + `alembic_managed`, has no parent registry UID, and
-  carries the same Project/Git context as the migration operation.
+  carries the same CodeRepository/Git context as the migration operation.
 - If `revision` autogenerate tries to create everything again, the local
   migration connection cannot see the provider's current physical tables.
 - If `upgrade` fails during prepare, inspect provider model identifiers,