@jterrats/open-orchestra 0.1.0 → 0.2.1

package/CHANGELOG.md

@@ -0,0 +1,53 @@
+# Changelog
+
+## 0.2.1 - 2026-05-06
+
+### Fixed
+
+- Generated runtime bootstrap guidance now uses the portable installed
+  executable form, `orchestra ...`, instead of repo-local
+  `node bin/orchestra.js ...` examples.
+- Skill render no longer creates partial `.agent-workflow/` state before
+  `orchestra init`, preventing CI validation failures in freshly cloned repos.
+- File-lock writes now create missing parent directories before locking, making
+  event recording safer in new workspaces.
+- Concurrent `evidence add` calls now create collision-resistant artifact
+  filenames instead of overwriting evidence recorded in the same millisecond.
+
+### Validation
+
+- Added regression coverage for portable bootstrap command examples, missing
+  lock parent directories, avoiding partial workflow state before init, and
+  concurrent evidence artifact creation.
+
+## 0.2.0 - 2026-05-06
+
+### Added
+
+- Runtime adapter catalog for `generic`, `claude`, `cursor`, `codex`, `vscode`,
+  and `windsurf`.
+- `orchestra runtime adapters --json` for clients and LLM runtimes that need
+  stable adapter metadata.
+- Target-specific init support with `orchestra init --target <csv>`.
+- Advisory init support for explicit runtime targets without default root
+  instruction writes.
+- Workspace classification and runtime adapter visibility in the web console.
+- Runtime adapter documentation covering Claude, Codex, Cursor, VS Code,
+  Windsurf, and generic LLM flows.
+
+### Changed
+
+- Runtime bootstrap and subagent protocol guidance now read from the runtime
+  adapter catalog instead of hardcoded target text.
+- Workspace classification uses the adapter catalog for supported target lists.
+- VS Code extension package version aligned with the CLI package.
+
+### Security
+
+- Extended workspace-local write guards to instruction apply/block paths.
+- Continued blocking unsafe workspace roots before init writes.
+
+### Validation
+
+- Added tests for runtime adapters, target-specific init, advisory target init,
+  workspace classification, and instruction path escape rejection.

package/README.md

@@ -14,12 +14,16 @@ node bin/orchestra.js status
 node bin/orchestra.js roles list --json
 ```
 
+For Claude, Codex, Cursor, VS Code, Windsurf, and generic LLM usage, see
+[docs/runtime-llm-flow.md](docs/runtime-llm-flow.md) and
+[docs/runtime-adapters.md](docs/runtime-adapters.md).
+
 
 ## Role Catalog
 
 Open Orchestra treats roles as capabilities and governance responsibilities, not only human job titles. Projects can keep roles inactive until risk, scope, impact area, or a workflow gate requires them.
 
-Core delivery roles remain available: Product Manager, Product Owner, Business Analyst, Architect, Developer, QA, Security, DevOps, SRE, DBA, UX/UI Designer, Release Manager, Compliance/Privacy, and Technical Writer.
+Core delivery roles remain available: Product Manager, Product Owner, Business Analyst, Architect, Developer, QA, Security, DevOps, SRE, DBA, Data Engineer, UX/UI Designer, Accessibility Reviewer, Release Manager, Compliance/Privacy, Technical Writer, Tech Lead, SDET, Platform Engineer, Frontend Specialist, Backend Specialist, Mobile Specialist, AI Evaluation Engineer, and Support/Customer Operations.
 
 State-of-the-art orchestration roles are also included:
 
@@ -36,7 +40,18 @@ State-of-the-art orchestration roles are also included:
 - Performance Engineer for load, latency, scalability, caching, concurrency, and graceful degradation.
 - Game Designer for gameplay loops, tutorialization, player feedback, and balance risk.
 
-Each default role declares activation criteria, expected evidence, and gate participation so a parent agent can select only the roles needed for a task.
+Each default role declares activation criteria, expected evidence, and gate participation so a parent agent can select only the roles needed for a task. See [docs/dev-team-specialist-role-profiles.md](docs/dev-team-specialist-role-profiles.md) for the specialist dev team profiles and source rationale.
+
+## Prompt Registry
+
+Open Orchestra scaffolds a stack-agnostic `.generated-prompts/` registry during `orchestra init`. Agents use it to preserve prompt intent, artifact decisions, and generated-work conventions without bloating the main instruction files.
+
+The registry is split by artifact type: code, UI, services, tests, CI/CD, docs, diagrams, and evals. Agents should read the relevant register before substantial generation and update it after substantial changes.
+
+## Skills and Context Loading
+
+Primary instruction files should stay short. Detailed procedures should live in task-scoped skills that are loaded only when a task needs them. See [docs/skill-loading-strategy.md](docs/skill-loading-strategy.md) for the proposed manifest, loading flow, built-in skill candidates, and middleware fallback for LLMs without native skill support.
+
 
 ## VS Code Control Center