dyro 0.1.0__tar.gz

dyro-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 DandreYang
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

dyro-0.1.0/PKG-INFO

@@ -0,0 +1,116 @@
+Metadata-Version: 2.4
+Name: dyro
+Version: 0.1.0
+Summary: DyroEngineeringFlow: local-first automation and delivery control for multi-repository teams
+Author: DandreYang
+License-Expression: MIT
+Project-URL: Homepage, https://github.com/DandreYang/DyroEngineeringFlow
+Project-URL: Repository, https://github.com/DandreYang/DyroEngineeringFlow
+Project-URL: Issues, https://github.com/DandreYang/DyroEngineeringFlow/issues
+Project-URL: Changelog, https://github.com/DandreYang/DyroEngineeringFlow/blob/main/CHANGELOG.md
+Keywords: agent,automation,delivery,git-worktree,multi-repository
+Classifier: Development Status :: 2 - Pre-Alpha
+Classifier: Environment :: Console
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Dynamic: license-file
+
+# DyroEngineeringFlow
+
+[English](README.md) | [简体中文](README.zh-CN.md) | [日本語](README.ja.md) | [한국어](README.ko.md) | [Español](README.es.md)
+
+**DyroEngineeringFlow · `dyro` CLI** is a local-first engineering automation and delivery control platform for multi-repository teams. It brings development lines, Git worktrees, agent launchers, task gates, independent review, and merge audit into versioned workspace configuration.
+
+**Keep engineering moving from task to delivery.**
+
+DyroEngineeringFlow is not coupled to Codex, Claude, or any business domain. Each team supplies a `dyro.toml` Profile for repositories, layouts, agent adapters, and delivery policy; business rules, model cost, and release practices stay in that Profile.
+
+## What it enforces
+
+- A task belongs to exactly one development line—never a mixed feature or hotfix workspace.
+- Each task runs in its own `git worktree` on a `task/<id>` branch.
+- Gates are executed by the orchestrator; an agent's self-report is not evidence of success.
+- A task needs independent review before it becomes `done`; merge and push require explicit confirmation by default.
+- Executable configuration is represented as argv arrays. The core never runs TOML-provided shell strings.
+
+## Quick start
+
+This is currently a local development release and requires Python 3.11 or later:
+
+```bash
+cd /path/to/DyroEngineeringFlow
+python3 -m pip install -e .
+
+mkdir my-workspace && cd my-workspace
+dyro init . --wizard --name my-workspace
+```
+
+The wizard records repository paths, their positions in a development line, and optional Git remotes. If a Profile contains remotes, missing repository anchors can be created safely:
+
+```bash
+dyro --dry-run bootstrap
+dyro bootstrap --yes
+dyro doctor
+```
+
+For a new teammate, the normal entry point is one command. It checks the workspace, then selects a development line and local agent:
+
+```bash
+dyro start
+```
+
+## Delivery workflow
+
+Use explicit commands when scripting or leading a release:
+
+```bash
+dyro doctor
+dyro line create release-2026-10 --base origin/main --yes
+dyro open release-2026-10 --agent codex
+dyro task create API-101 --title "Implement API contract" --line release-2026-10 --repository api
+dyro task next
+dyro task next --run --yes
+dyro task review API-101
+dyro task merge API-101 --yes
+```
+
+A production hotfix must state its verified production base; it never inherits a default branch implicitly:
+
+```bash
+dyro hotfix create incident-123 --base v2026.09.7 --repos api,web --yes
+```
+
+Every write-capable operation has a planning mode:
+
+```bash
+dyro --dry-run line create release-2026-10 --base origin/main
+dyro --dry-run task run API-101
+```
+
+## Command map
+
+| Command | Purpose |
+| --- | --- |
+| `init --wizard` / `bootstrap` / `start` | Onboard a teammate, restore missing repository anchors, and choose a line and agent. |
+| `doctor` / `status` | Validate and display control-plane state. |
+| `line create/list` | Create, register, and inspect feature development lines. |
+| `hotfix create` | Create a hotfix line from an explicit production base. |
+| `agent list` / `open` | Inspect adapters or open an agent in the correct development line. |
+| `task create/list/board/status/next` | Manage task manifests, the state machine, and the next actionable task. |
+| `task run/answer/gates/review` | Run tasks, resolve questions, execute gates, and request independent review. |
+| `task merge` | Merge a reviewed task branch into its owning development line. |
+| `task loop/daemon/stats/decisions` | Run controlled batches, scheduling, ledger reporting, and decision gates. |
+
+See the [architecture and Profile contract](docs/architecture.md) and the [Huiyichu migration guide](docs/migration-huiyichu.md) for implementation detail.
+
+## Languages and documentation
+
+This README is maintained in English, Simplified Chinese, Japanese, Korean, and Spanish. Commands, configuration keys, directory names, and safety rules are deliberately identical across translations. The current CLI messages and extended technical guides are primarily Chinese; multilingual README support does not claim that the runtime has language switching yet.
+
+## Current boundaries
+
+DyroEngineeringFlow provides a complete local workflow loop. It does not create remote repositories, ship SaaS credentials, or enable automatic push. Automatic merge requires permission in both the task manifest and local policy. It is available under the [MIT License](LICENSE). PyPI Trusted Publishing is prepared, but `dyro` is not published to PyPI yet; the PyPI pending publisher, GitHub `pypi` Environment, and first GitHub Release must still be configured. Package-name, trademark, cross-platform adapter, and real external-project pilot validation remain required before public release.

dyro-0.1.0/README.md

@@ -0,0 +1,95 @@
+# DyroEngineeringFlow
+
+[English](README.md) | [简体中文](README.zh-CN.md) | [日本語](README.ja.md) | [한국어](README.ko.md) | [Español](README.es.md)
+
+**DyroEngineeringFlow · `dyro` CLI** is a local-first engineering automation and delivery control platform for multi-repository teams. It brings development lines, Git worktrees, agent launchers, task gates, independent review, and merge audit into versioned workspace configuration.
+
+**Keep engineering moving from task to delivery.**
+
+DyroEngineeringFlow is not coupled to Codex, Claude, or any business domain. Each team supplies a `dyro.toml` Profile for repositories, layouts, agent adapters, and delivery policy; business rules, model cost, and release practices stay in that Profile.
+
+## What it enforces
+
+- A task belongs to exactly one development line—never a mixed feature or hotfix workspace.
+- Each task runs in its own `git worktree` on a `task/<id>` branch.
+- Gates are executed by the orchestrator; an agent's self-report is not evidence of success.
+- A task needs independent review before it becomes `done`; merge and push require explicit confirmation by default.
+- Executable configuration is represented as argv arrays. The core never runs TOML-provided shell strings.
+
+## Quick start
+
+This is currently a local development release and requires Python 3.11 or later:
+
+```bash
+cd /path/to/DyroEngineeringFlow
+python3 -m pip install -e .
+
+mkdir my-workspace && cd my-workspace
+dyro init . --wizard --name my-workspace
+```
+
+The wizard records repository paths, their positions in a development line, and optional Git remotes. If a Profile contains remotes, missing repository anchors can be created safely:
+
+```bash
+dyro --dry-run bootstrap
+dyro bootstrap --yes
+dyro doctor
+```
+
+For a new teammate, the normal entry point is one command. It checks the workspace, then selects a development line and local agent:
+
+```bash
+dyro start
+```
+
+## Delivery workflow
+
+Use explicit commands when scripting or leading a release:
+
+```bash
+dyro doctor
+dyro line create release-2026-10 --base origin/main --yes
+dyro open release-2026-10 --agent codex
+dyro task create API-101 --title "Implement API contract" --line release-2026-10 --repository api
+dyro task next
+dyro task next --run --yes
+dyro task review API-101
+dyro task merge API-101 --yes
+```
+
+A production hotfix must state its verified production base; it never inherits a default branch implicitly:
+
+```bash
+dyro hotfix create incident-123 --base v2026.09.7 --repos api,web --yes
+```
+
+Every write-capable operation has a planning mode:
+
+```bash
+dyro --dry-run line create release-2026-10 --base origin/main
+dyro --dry-run task run API-101
+```
+
+## Command map
+
+| Command | Purpose |
+| --- | --- |
+| `init --wizard` / `bootstrap` / `start` | Onboard a teammate, restore missing repository anchors, and choose a line and agent. |
+| `doctor` / `status` | Validate and display control-plane state. |
+| `line create/list` | Create, register, and inspect feature development lines. |
+| `hotfix create` | Create a hotfix line from an explicit production base. |
+| `agent list` / `open` | Inspect adapters or open an agent in the correct development line. |
+| `task create/list/board/status/next` | Manage task manifests, the state machine, and the next actionable task. |
+| `task run/answer/gates/review` | Run tasks, resolve questions, execute gates, and request independent review. |
+| `task merge` | Merge a reviewed task branch into its owning development line. |
+| `task loop/daemon/stats/decisions` | Run controlled batches, scheduling, ledger reporting, and decision gates. |
+
+See the [architecture and Profile contract](docs/architecture.md) and the [Huiyichu migration guide](docs/migration-huiyichu.md) for implementation detail.
+
+## Languages and documentation
+
+This README is maintained in English, Simplified Chinese, Japanese, Korean, and Spanish. Commands, configuration keys, directory names, and safety rules are deliberately identical across translations. The current CLI messages and extended technical guides are primarily Chinese; multilingual README support does not claim that the runtime has language switching yet.
+
+## Current boundaries
+
+DyroEngineeringFlow provides a complete local workflow loop. It does not create remote repositories, ship SaaS credentials, or enable automatic push. Automatic merge requires permission in both the task manifest and local policy. It is available under the [MIT License](LICENSE). PyPI Trusted Publishing is prepared, but `dyro` is not published to PyPI yet; the PyPI pending publisher, GitHub `pypi` Environment, and first GitHub Release must still be configured. Package-name, trademark, cross-platform adapter, and real external-project pilot validation remain required before public release.

dyro-0.1.0/pyproject.toml

@@ -0,0 +1,39 @@
+[build-system]
+requires = ["setuptools>=77.0.3"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "dyro"
+version = "0.1.0"
+description = "DyroEngineeringFlow: local-first automation and delivery control for multi-repository teams"
+readme = "README.md"
+requires-python = ">=3.11"
+authors = [{ name = "DandreYang" }]
+license = "MIT"
+license-files = ["LICENSE"]
+keywords = ["agent", "automation", "delivery", "git-worktree", "multi-repository"]
+classifiers = [
+  "Development Status :: 2 - Pre-Alpha",
+    "Environment :: Console",
+  "Programming Language :: Python :: 3",
+  "Programming Language :: Python :: 3.11",
+  "Programming Language :: Python :: 3.12",
+]
+
+[project.urls]
+Homepage = "https://github.com/DandreYang/DyroEngineeringFlow"
+Repository = "https://github.com/DandreYang/DyroEngineeringFlow"
+Issues = "https://github.com/DandreYang/DyroEngineeringFlow/issues"
+Changelog = "https://github.com/DandreYang/DyroEngineeringFlow/blob/main/CHANGELOG.md"
+
+[project.scripts]
+dyro = "dyro.cli:main"
+
+[tool.setuptools]
+package-dir = { "" = "src" }
+
+[tool.setuptools.packages.find]
+where = ["src"]
+
+[tool.unittest]
+start-directory = "tests"

dyro-0.1.0/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+

dyro-0.1.0/src/dyro/__init__.py

@@ -0,0 +1,3 @@
+"""DyroEngineeringFlow: the dyro CLI for multi-repository delivery automation."""
+
+__version__ = "0.1.0"

dyro-0.1.0/src/dyro/__main__.py

@@ -0,0 +1,5 @@
+from .cli import main
+
+
+if __name__ == "__main__":
+    main()