Files

Docs CI / lint-and-preview (push) Waiting to run

Details

feat: Enhance Task Runner with simulation and failure policy support

- Added tests for output projection and failure policy population in TaskPackPlanner.
- Introduced new failure policy manifest in TestManifests.
- Implemented simulation endpoints in the web service for task execution.
- Created TaskRunnerServiceOptions for configuration management.
- Updated appsettings.json to include TaskRunner configuration.
- Enhanced PackRunWorkerService to handle execution graphs and state management.
- Added support for parallel execution and conditional steps in the worker service.
- Updated documentation to reflect new features and changes in execution flow.

2025-11-04 19:05:56 +02:00

1.9 KiB

Raw Blame History

DevOps agent guide

Mission

The DevOps module captures release, deployment, and migration playbooks that keep StellaOps deterministic across environments.

Key docs

How to get started

Open ../../implplan/SPRINTS.md and locate the stories referencing this module.
Review ./TASKS.md for local follow-ups and confirm status transitions (TODO → DOING → DONE/BLOCKED).
Read the architecture and README for domain context before editing code or docs.
Coordinate cross-module changes in the main /AGENTS.md description and through the sprint plan.

Guardrails

Honour the Aggregation-Only Contract where applicable (see ../../ingestion/aggregation-only-contract.md).
Preserve determinism: sort outputs, normalise timestamps (UTC ISO-8601), and avoid machine-specific artefacts.
Keep Offline Kit parity in mind—document air-gapped workflows for any new feature.
Update runbooks/observability assets when operational characteristics change.

Required Reading

docs/modules/devops/README.md
docs/modules/devops/architecture.md
docs/modules/devops/implementation_plan.md
docs/modules/platform/architecture-overview.md

Working Agreement

1. Update task status to DOING/DONE in both docs/implplan/SPRINTS.md and the local TASKS.md when you start or finish work.
1. Review this charter and the Required Reading documents before coding; confirm prerequisites are met.
1. Keep changes deterministic (stable ordering, timestamps, hashes) and align with offline/air-gap expectations.
1. Coordinate doc updates, tests, and cross-guild communication whenever contracts or workflows change.
1. Revert to TODO if you pause the task without shipping changes; leave notes in commit/PR descriptions for context.

1.9 KiB Raw Blame History