vstack 2.2.0__tar.gz → 3.1.1__tar.gz

{vstack-2.2.0 → vstack-3.1.1}/PKG-INFO

@@ -1,11 +1,12 @@
 Metadata-Version: 2.4
 Name: vstack
-Version: 2.2.0
+Version: 3.1.1
 Summary: VS Code-native AI engineering workflow system for microservices, libraries, and backend systems.
 License-Expression: MIT
 License-File: LICENSE
-Keywords: github-copilot,vscode,ai-workflows,developer-tools,devx,engineering-workflow,copilot-agent-mode,backend,microservices,api,workflow-automation,release-engineering
+Keywords: github-copilot,vscode,ai-workflows,developer-tools,devx,engineering-workflow,copilot-agent-mode,backend,microservices,api,workflow-automation,release-engineering,agentic-workflow,agentic-ai,ai-agent,llm,llm-agents,prompt-engineering,code-generation,scaffolding,cli,agents
 Requires-Python: >=3.11,<3.15
+Classifier: Development Status :: 4 - Beta
 Classifier: License :: OSI Approved :: MIT License
 Classifier: Programming Language :: Python :: 3
 Classifier: Programming Language :: Python :: 3.11
@@ -15,7 +16,10 @@ Classifier: Programming Language :: Python :: 3.14
 Classifier: Environment :: Console
 Classifier: Intended Audience :: Developers
 Classifier: Topic :: Software Development :: Build Tools
+Classifier: Topic :: Software Development :: Code Generators
 Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Classifier: Topic :: Utilities
+Requires-Dist: pyyaml (>=6.0)
 Project-URL: Changelog, https://github.com/eschaar/vstack/blob/main/CHANGELOG.md
 Project-URL: Documentation, https://github.com/eschaar/vstack/blob/main/README.md
 Project-URL: Discussions, https://github.com/eschaar/vstack/discussions
@@ -33,7 +37,7 @@ Description-Content-Type: text/markdown
 [![Python version](https://img.shields.io/badge/python-3.11--3.14-0B8A6F)](https://github.com/eschaar/vstack/blob/main/pyproject.toml)
 [![Verify status](https://img.shields.io/github/actions/workflow/status/eschaar/vstack/verify.yml?label=verify&color=1D6FA5)](https://github.com/eschaar/vstack/actions/workflows/verify.yml)
 [![Security checks](https://img.shields.io/github/actions/workflow/status/eschaar/vstack/security.yml?label=security&color=B15E00)](https://github.com/eschaar/vstack/actions/workflows/security.yml)
-[![Runtime: stdlib only](https://img.shields.io/badge/runtime-stdlib%20only-5B6C8F)](https://github.com/eschaar/vstack/blob/main/pyproject.toml)
+[![Runtime: PyYAML](https://img.shields.io/badge/runtime-PyYAML-5B6C8F)](https://github.com/eschaar/vstack/blob/main/pyproject.toml)
 [![License: MIT](https://img.shields.io/github/license/eschaar/vstack?color=5F7A1F)](https://github.com/eschaar/vstack/blob/main/LICENSE)
 [![GitHub Discussions](https://img.shields.io/badge/discussions-ask%20%26%20share-blueviolet?logo=github)](https://github.com/eschaar/vstack/discussions)
 
@@ -54,7 +58,7 @@ It provides a fixed role model for end-to-end software delivery: `product`, `arc
 - Fixed role model: `product`, `architect`, `designer`, `engineer`, `tester`, `release`
 - Template-driven install model from `src/vstack/_templates/`
 - Backend-first verification, security, and release discipline
-- Standard-library-only runtime dependencies
+- One runtime dependency: PyYAML
 
 ## Building blocks
 
@@ -80,16 +84,23 @@ VS Code command palette (`Chat: Run Prompt File`) or the Copilot Chat attach but
 | `migration-safety`  | Review DB migration safety, rollback, and zero-downtime   |
 | `release-readiness` | Evaluate release readiness from reports and open blockers |
 
-## Quick start
+## Quickstart — fresh install
 
 Install with `pipx`, then install vstack artifacts into your repository:
 
 ```bash
+# Install the CLI once, globally
 pipx install vstack
-vstack install --target /path/to/your/project
-vstack validate
+
+# Move to your repository root and run install — no --target needed
+cd /path/to/your/project
+vstack install        # seeds .vstack/config.yaml and generates .github/ in the current directory
+vstack validate       # confirm no errors
 ```
 
+When you omit `--target`, vstack uses the current working directory. The equivalent
+explicit form is `vstack install --target /path/to/your/project`.
+
 Run a first task in Copilot Agent Mode:
 
 ```text
@@ -101,6 +112,57 @@ Expected result:
 - `vstack validate` reports no unresolved template tokens
 - Agent command returns a concrete verification summary for your repository
 
+## Quick upgrade
+
+### Patch or minor version (e.g. v3.1 → v3.2, same major)
+
+Docs paths never change within a major version. Only `.github/` artifacts are updated.
+
+```bash
+pipx upgrade vstack
+
+cd /path/to/your/project
+vstack init           # idempotent — safe to run in CI
+```
+
+### Major version (e.g. v2 → v3)
+
+Docs paths may change on a major version bump. Run `vstack migrate` before `vstack init`.
+
+```bash
+pipx upgrade vstack
+
+cd /path/to/your/project
+vstack migrate        # moves docs files to their new paths (auto-detects installed version)
+vstack init           # regenerates .github/ artifacts
+
+# Only if you see "Legacy manifest schema detected" in the output above:
+vstack manifest upgrade
+vstack init
+```
+
+Preview the docs moves without touching any files:
+
+```bash
+vstack migrate --dry-run
+```
+
+For upgrades spanning multiple major versions (e.g. v1 → v3), `vstack migrate` chains
+all intermediate steps automatically. Use `--from` and `--to` to specify the range
+explicitly if auto-detection from the manifest fails:
+
+```bash
+vstack migrate --from 1 --to 3
+vstack init
+```
+
+### Force reinstall (overwrite local edits)
+
+```bash
+vstack install --force                       # overwrite all managed artifacts
+vstack install --force-name agent/engineer   # overwrite one specific artifact
+```
+
 ## Why this helps
 
 - Consistent role boundaries for planning, implementation, validation, and release
@@ -112,10 +174,17 @@ Expected result:
 ```bash
 vstack --version
 vstack validate
+
+# Run from your repository root (--target defaults to the current directory)
+vstack install
+vstack init
+vstack migrate
+vstack manifest verify
+vstack manifest status
+vstack manifest upgrade
+
+# Or specify a path explicitly
 vstack install --target /path/to/your/project
-vstack manifest verify --target /path/to/your/project
-vstack manifest status --target /path/to/your/project
-vstack manifest upgrade --target /path/to/your/project
 ```
 
 ## Common usage patterns
@@ -123,6 +192,11 @@ vstack manifest upgrade --target /path/to/your/project
 Repository-scoped install (recommended for teams):
 
 ```bash
+# Move to your repository root and install there
+cd /path/to/your/project
+vstack install
+
+# Or specify a path explicitly from any directory
 vstack install --target /path/to/your/project
 ```
 
@@ -132,12 +206,25 @@ Profile-wide install (optional defaults for all projects):
 vstack install --global
 ```
 
-By default, `vstack install` preserves existing unmanaged files and local edits to tracked files by comparing the current file contents with the SHA-256 checksum recorded in `vstack.json`. Use `--adopt-name <name>` to start tracking one existing unmanaged file without overwriting it. `vstack uninstall` also preserves locally modified tracked files unless you explicitly pass `--force` or `--force-name <name>`. Use `vstack manifest status --target ...` (or `vstack status --target ...`) to see what still matches the manifest. If a legacy manifest schema is detected, run `vstack manifest upgrade --target ...` first.
+`vstack install` is the first-run command: it seeds `.vstack/config.yaml` in your project (never overwrites), then generates `.github/` artifacts from templates. `vstack init` re-runs generation idempotently — safe to use in CI after upgrading vstack.
+
+By default, `vstack install` preserves existing unmanaged files and local edits to tracked files by comparing the current file contents with the SHA-256 checksum recorded in `.vstack/vstack.json`. Use `--adopt-name <name>` to start tracking one existing unmanaged file without overwriting it. `vstack uninstall` also preserves locally modified tracked files unless you explicitly pass `--force` or `--force-name <name>`. Use `vstack manifest status --target ...` (or `vstack status --target ...`) to see what still matches the manifest. If a legacy manifest schema is detected, run `vstack manifest upgrade --target ...` first.
+
+To skip artifact types or individual artifacts you do not need, edit `.vstack/config.yaml`:
+
+```yaml
+exclude:
+  skills:
+    - terraform
+    - helm
+  instructions: all   # skip the entire type
+```
 
 If you already have agents, skills, or other files in `.github/`, run a dry-run first to see what would be preserved before committing:
 
 ```bash
-vstack install --dry-run --target /path/to/your/project
+# Run from your repository root
+vstack install --dry-run
 ```
 
 The summary lists preserved files as `type/name` selectors (e.g. `agent/engineer`). Resolve each conflict with `--force-name type/name` to overwrite, `--adopt-name type/name` to take ownership without overwriting, or `--force` to overwrite everything.
@@ -145,7 +232,7 @@ The summary lists preserved files as `type/name` selectors (e.g. `agent/engineer
 ## Fast troubleshooting
 
 - Command not found after install: ensure your `pipx` binary path is in `PATH`
-- Validation error: rerun `vstack install --target ...` and then `vstack validate`
+- Validation error: rerun `vstack install` from your repository root and then `vstack validate`
 - Agent results look generic: explicitly invoke a role (for example `@tester`) before a skill
 
 ## Full documentation

{vstack-2.2.0 → vstack-3.1.1}/README-pypi.md

@@ -6,7 +6,7 @@
 [![Python version](https://img.shields.io/badge/python-3.11--3.14-0B8A6F)](https://github.com/eschaar/vstack/blob/main/pyproject.toml)
 [![Verify status](https://img.shields.io/github/actions/workflow/status/eschaar/vstack/verify.yml?label=verify&color=1D6FA5)](https://github.com/eschaar/vstack/actions/workflows/verify.yml)
 [![Security checks](https://img.shields.io/github/actions/workflow/status/eschaar/vstack/security.yml?label=security&color=B15E00)](https://github.com/eschaar/vstack/actions/workflows/security.yml)
-[![Runtime: stdlib only](https://img.shields.io/badge/runtime-stdlib%20only-5B6C8F)](https://github.com/eschaar/vstack/blob/main/pyproject.toml)
+[![Runtime: PyYAML](https://img.shields.io/badge/runtime-PyYAML-5B6C8F)](https://github.com/eschaar/vstack/blob/main/pyproject.toml)
 [![License: MIT](https://img.shields.io/github/license/eschaar/vstack?color=5F7A1F)](https://github.com/eschaar/vstack/blob/main/LICENSE)
 [![GitHub Discussions](https://img.shields.io/badge/discussions-ask%20%26%20share-blueviolet?logo=github)](https://github.com/eschaar/vstack/discussions)
 
@@ -27,7 +27,7 @@ It provides a fixed role model for end-to-end software delivery: `product`, `arc
 - Fixed role model: `product`, `architect`, `designer`, `engineer`, `tester`, `release`
 - Template-driven install model from `src/vstack/_templates/`
 - Backend-first verification, security, and release discipline
-- Standard-library-only runtime dependencies
+- One runtime dependency: PyYAML
 
 ## Building blocks
 
@@ -53,16 +53,23 @@ VS Code command palette (`Chat: Run Prompt File`) or the Copilot Chat attach but
 | `migration-safety`  | Review DB migration safety, rollback, and zero-downtime   |
 | `release-readiness` | Evaluate release readiness from reports and open blockers |
 
-## Quick start
+## Quickstart — fresh install
 
 Install with `pipx`, then install vstack artifacts into your repository:
 
 ```bash
+# Install the CLI once, globally
 pipx install vstack
-vstack install --target /path/to/your/project
-vstack validate
+
+# Move to your repository root and run install — no --target needed
+cd /path/to/your/project
+vstack install        # seeds .vstack/config.yaml and generates .github/ in the current directory
+vstack validate       # confirm no errors
 ```
 
+When you omit `--target`, vstack uses the current working directory. The equivalent
+explicit form is `vstack install --target /path/to/your/project`.
+
 Run a first task in Copilot Agent Mode:
 
 ```text
@@ -74,6 +81,57 @@ Expected result:
 - `vstack validate` reports no unresolved template tokens
 - Agent command returns a concrete verification summary for your repository
 
+## Quick upgrade
+
+### Patch or minor version (e.g. v3.1 → v3.2, same major)
+
+Docs paths never change within a major version. Only `.github/` artifacts are updated.
+
+```bash
+pipx upgrade vstack
+
+cd /path/to/your/project
+vstack init           # idempotent — safe to run in CI
+```
+
+### Major version (e.g. v2 → v3)
+
+Docs paths may change on a major version bump. Run `vstack migrate` before `vstack init`.
+
+```bash
+pipx upgrade vstack
+
+cd /path/to/your/project
+vstack migrate        # moves docs files to their new paths (auto-detects installed version)
+vstack init           # regenerates .github/ artifacts
+
+# Only if you see "Legacy manifest schema detected" in the output above:
+vstack manifest upgrade
+vstack init
+```
+
+Preview the docs moves without touching any files:
+
+```bash
+vstack migrate --dry-run
+```
+
+For upgrades spanning multiple major versions (e.g. v1 → v3), `vstack migrate` chains
+all intermediate steps automatically. Use `--from` and `--to` to specify the range
+explicitly if auto-detection from the manifest fails:
+
+```bash
+vstack migrate --from 1 --to 3
+vstack init
+```
+
+### Force reinstall (overwrite local edits)
+
+```bash
+vstack install --force                       # overwrite all managed artifacts
+vstack install --force-name agent/engineer   # overwrite one specific artifact
+```
+
 ## Why this helps
 
 - Consistent role boundaries for planning, implementation, validation, and release
@@ -85,10 +143,17 @@ Expected result:
 ```bash
 vstack --version
 vstack validate
+
+# Run from your repository root (--target defaults to the current directory)
+vstack install
+vstack init
+vstack migrate
+vstack manifest verify
+vstack manifest status
+vstack manifest upgrade
+
+# Or specify a path explicitly
 vstack install --target /path/to/your/project
-vstack manifest verify --target /path/to/your/project
-vstack manifest status --target /path/to/your/project
-vstack manifest upgrade --target /path/to/your/project
 ```
 
 ## Common usage patterns
@@ -96,6 +161,11 @@ vstack manifest upgrade --target /path/to/your/project
 Repository-scoped install (recommended for teams):
 
 ```bash
+# Move to your repository root and install there
+cd /path/to/your/project
+vstack install
+
+# Or specify a path explicitly from any directory
 vstack install --target /path/to/your/project
 ```
 
@@ -105,12 +175,25 @@ Profile-wide install (optional defaults for all projects):
 vstack install --global
 ```
 
-By default, `vstack install` preserves existing unmanaged files and local edits to tracked files by comparing the current file contents with the SHA-256 checksum recorded in `vstack.json`. Use `--adopt-name <name>` to start tracking one existing unmanaged file without overwriting it. `vstack uninstall` also preserves locally modified tracked files unless you explicitly pass `--force` or `--force-name <name>`. Use `vstack manifest status --target ...` (or `vstack status --target ...`) to see what still matches the manifest. If a legacy manifest schema is detected, run `vstack manifest upgrade --target ...` first.
+`vstack install` is the first-run command: it seeds `.vstack/config.yaml` in your project (never overwrites), then generates `.github/` artifacts from templates. `vstack init` re-runs generation idempotently — safe to use in CI after upgrading vstack.
+
+By default, `vstack install` preserves existing unmanaged files and local edits to tracked files by comparing the current file contents with the SHA-256 checksum recorded in `.vstack/vstack.json`. Use `--adopt-name <name>` to start tracking one existing unmanaged file without overwriting it. `vstack uninstall` also preserves locally modified tracked files unless you explicitly pass `--force` or `--force-name <name>`. Use `vstack manifest status --target ...` (or `vstack status --target ...`) to see what still matches the manifest. If a legacy manifest schema is detected, run `vstack manifest upgrade --target ...` first.
+
+To skip artifact types or individual artifacts you do not need, edit `.vstack/config.yaml`:
+
+```yaml
+exclude:
+  skills:
+    - terraform
+    - helm
+  instructions: all   # skip the entire type
+```
 
 If you already have agents, skills, or other files in `.github/`, run a dry-run first to see what would be preserved before committing:
 
 ```bash
-vstack install --dry-run --target /path/to/your/project
+# Run from your repository root
+vstack install --dry-run
 ```
 
 The summary lists preserved files as `type/name` selectors (e.g. `agent/engineer`). Resolve each conflict with `--force-name type/name` to overwrite, `--adopt-name type/name` to take ownership without overwriting, or `--force` to overwrite everything.
@@ -118,7 +201,7 @@ The summary lists preserved files as `type/name` selectors (e.g. `agent/engineer
 ## Fast troubleshooting
 
 - Command not found after install: ensure your `pipx` binary path is in `PATH`
-- Validation error: rerun `vstack install --target ...` and then `vstack validate`
+- Validation error: rerun `vstack install` from your repository root and then `vstack validate`
 - Agent results look generic: explicitly invoke a role (for example `@tester`) before a skill
 
 ## Full documentation

{vstack-2.2.0 → vstack-3.1.1}/pyproject.toml

@@ -5,7 +5,7 @@ description = "VS Code-native AI engineering workflow system for microservices,
 license = "MIT"
 readme = "README-pypi.md"
 requires-python = ">=3.11,<3.15"
-dependencies = []
+dependencies = ["pyyaml>=6.0"]
 keywords = [
     "github-copilot",
     "vscode",
@@ -19,8 +19,19 @@ keywords = [
     "api",
     "workflow-automation",
     "release-engineering",
+    "agentic-workflow",
+    "agentic-ai",
+    "ai-agent",
+    "llm",
+    "llm-agents",
+    "prompt-engineering",
+    "code-generation",
+    "scaffolding",
+    "cli",
+    "agents",
 ]
 classifiers = [
+    "Development Status :: 4 - Beta",
     "License :: OSI Approved :: MIT License",
     "Programming Language :: Python :: 3",
     "Programming Language :: Python :: 3.11",
@@ -30,9 +41,11 @@ classifiers = [
     "Environment :: Console",
     "Intended Audience :: Developers",
     "Topic :: Software Development :: Build Tools",
+    "Topic :: Software Development :: Code Generators",
     "Topic :: Software Development :: Libraries :: Python Modules",
+    "Topic :: Utilities",
 ]
-version = "2.2.0"
+version = "3.1.1"
 
 [project.urls]
 Homepage = "https://github.com/eschaar/vstack"
@@ -55,6 +68,7 @@ vstack = "vstack:main"
 packages = [{include = "vstack", from = "src"}]
 include = [
     { path = "src/vstack/_templates", format = ["sdist", "wheel"] },
+    { path = "src/vstack/_migrations", format = ["sdist", "wheel"] },
 ]
 # Keep the placeholder version last because the plugin may remove/re-add it in
 # PEP 621 mode, which otherwise causes noisy key reordering.
@@ -69,6 +83,7 @@ ruff = ">=0.15.12"
 mypy = ">=1.20.2"
 pre-commit = ">=4.6.0"
 tox = ">=4.15"
+types-PyYAML = ">=6.0"
 
 
 # ---------------------------------------------------------------------------
@@ -163,6 +178,7 @@ package = skip
 deps =
     pytest>=9.0
     pytest-cov>=6.0
+    pyyaml>=6.0
 setenv =
     PYTHONPATH = {tox_root}/src
 commands =
@@ -181,6 +197,7 @@ description = Run mypy type checks
 package = skip
 deps =
     mypy>=1.20
+    types-PyYAML>=6.0
 commands =
     mypy src tests
 """

vstack-3.1.1/src/vstack/_migrations/README.md

@@ -0,0 +1,44 @@
+# vstack migration records
+
+This directory contains machine-readable migration records for `docs/` artifact path
+changes across major vstack version boundaries.
+
+Each file covers one major version transition and is named `v{M}_to_v{N}.yaml` where
+`M` is the source major version and `N` is the target major version.
+
+These files are read by `vstack migrate` to relocate agent-owned docs files when their
+paths change between major versions.
+
+## Usage
+
+```
+vstack migrate [--target <dir>] [--from <major>] [--to <major>] [--dry-run]
+```
+
+Run from the project root (or pass `--target`) after upgrading vstack to a new major
+version. The command chains all necessary migration steps between the installed major
+and the current package major.
+
+| Flag             | Description                                                     |
+| ---------------- | --------------------------------------------------------------- |
+| `--target <dir>` | Project root to migrate (default: current directory)            |
+| `--from <major>` | Source major version (default: read from `.vstack/vstack.json`) |
+| `--to <major>`   | Target major version (default: current vstack package major)    |
+| `--dry-run`      | Print moves without touching the filesystem                     |
+
+`vstack migrate` only moves files that exist at the old path; absent files are silently
+skipped. It reads `artifacts.root` from `.vstack/config.yaml` and adjusts destination
+paths when the project uses a custom docs root.
+
+## Schema
+
+```yaml
+from_version: "3.x"        # semver range for the source version
+to_version: "4.0"          # first minor of the target major
+moves:
+  - old: docs/path/old.md  # path relative to project root
+    new: docs/path/new.md  # path relative to project root
+    type: docs              # always "docs" for this directory
+    notes: >               # optional: human-readable explanation
+      Why this path changed and what to do with the old file after migration.
+```

vstack-3.1.1/src/vstack/_migrations/v2_to_v3.yaml

@@ -0,0 +1,39 @@
+from_version: "2.x"
+to_version: "3.0"
+moves:
+  - old: docs/architecture/architecture.md
+    new: docs/architecture/overview.md
+    type: docs
+    notes: >
+      architect role primary output renamed from architecture.md to overview.md
+      in v3 to align with the generic overview.md convention used by all roles.
+      Content is the same — only the filename changed.
+
+  - old: docs/design/design.md
+    new: docs/design/overview.md
+    type: docs
+    notes: >
+      designer role primary output renamed from design.md to overview.md in v3
+      to align with the generic overview.md convention used by all roles.
+      Content is the same — only the filename changed.
+
+  - old: docs/test-report.md
+    new: docs/reports/test-report.md
+    type: docs
+    notes: >
+      tester role reports moved from the docs/ root into docs/reports/ in v3.
+      This groups all tester outputs under a single subdirectory.
+
+  - old: docs/security-report.md
+    new: docs/reports/security-report.md
+    type: docs
+    notes: >
+      tester role reports moved from the docs/ root into docs/reports/ in v3.
+      This groups all tester outputs under a single subdirectory.
+
+  - old: docs/performance-baseline.md
+    new: docs/reports/performance-baseline.md
+    type: docs
+    notes: >
+      tester role reports moved from the docs/ root into docs/reports/ in v3.
+      This groups all tester outputs under a single subdirectory.

vstack-3.1.1/src/vstack/_templates/agents/architect/artifacts/adr/NNN-template.md

@@ -0,0 +1,27 @@
+# ADR-NNN: {title}
+
+<!-- One file per decision. Suggested name: NNN-{slug}.md (e.g. 001-service-boundaries.md)
+Deviate from this structure as needed. -->
+
+> **date:** YYYY-MM-DD\
+> **status:** proposed | accepted | superseded by ADR-NNN
+
+## context
+
+<!-- What situation or problem led to this decision? -->
+
+## decision
+
+<!-- What was decided? State it clearly and positively. -->
+
+## alternatives considered
+
+<!-- What other options were evaluated? Why were they not chosen? -->
+
+## rationale
+
+<!-- Why is this decision the right one given the context? -->
+
+## consequences
+
+<!-- What is easier or harder as a result? What does this enable or constrain? -->

vstack-3.1.1/src/vstack/_templates/agents/architect/artifacts/overview.md

@@ -0,0 +1,41 @@
+# Architecture Overview
+
+<!-- Describes the system architecture. Deviate from this structure as needed. -->
+
+> Maintained by: **architect** role\
+> Last updated: YYYY-MM-DD
+
+## overview
+
+<!-- What system is this? What problem does it solve?
+Include a system style declaration: e.g. `**System style:** microservice | monolith | platform | library` -->
+
+## system structure
+
+<!-- Repository or deployment layout. Use a plain text tree for directory structure. -->
+
+```text
+{system}/
+├── ...
+```
+
+## components
+
+<!-- High-level component breakdown. Use a Mermaid diagram for flows; text tree for structure. -->
+
+## principles
+
+<!-- Key architectural constraints and non-negotiable decisions.
+These constrain all downstream design choices. -->
+
+## data flow
+
+<!-- How data moves through the system. -->
+
+## key decisions
+
+<!-- Links or summaries of significant ADRs. -->
+
+## open questions
+
+<!-- Unresolved architectural concerns. -->

{vstack-2.2.0 → vstack-3.1.1}/src/vstack/_templates/agents/architect/config.yaml

@@ -1,18 +1,17 @@
 name: architect
-version: 20260502015
+version: 20260503022
 description: >
   Senior software architect. Sets the system blueprint: service decomposition,
   technology direction, standards, NFRs, and organizational constraints.
   Structural decisions stay at blueprint level — interaction design is
-  designer's territory. Reads docs/product/vision.md and
-  docs/product/requirements.md; produces docs/architecture/architecture.md and
-  docs/architecture/adr/*.md. Baseline-first on branch, optional
-  docs/delta/{id} for complex drafts.
+  designer's territory. Reads product artifacts; produces architecture overview
+  and ADRs. Baseline-first on branch.
 argument-hint: "[design architecture | write ADR | review architecture | check implementation alignment]"
 tools:
   - read
   - search
   - edit
+  - execute
   - web
   - vscode
   - todo
@@ -22,13 +21,23 @@ model:
   - GPT-5.3-Codex (copilot)
   - Claude Opus 4.7 (copilot)
 agents: ["*"]
-handoffs:
-  - label: Continue to design
-    agent: designer
-    prompt: >
-      Translate docs/architecture/architecture.md into docs/design/design.md
-      with concrete interfaces and contracts.
 target: vscode
+defaults:
+  handoffs:
+    prompt: >
+      Architecture outputs are approved. Assess the current state and produce
+      design specifications as needed. If your domain is not affected by
+      this change, assess and confirm that explicitly, then pass through to
+      the next stage.
+  artifacts:
+    dir: architecture
+    input:
+      - product/**/*.md
+    output:
+      - path: overview.md
+        baseline: true
+      - path: adr/*.md
+        baseline: true
 user-invocable: true
 
 # Optional when needed: