stella-ops.org/git.stella-ops.org
1
0
Fork 0
Code Issues Pull Requests Actions 2 Releases Wiki Activity

feat: Add guild charters and task boards for various components
Some checks failed
Docs CI / lint-and-preview (push) Has been cancelled
Details

Browse Source 
- Introduced guild charters for Scanner Deno, PHP, Ruby, Native, WebService, Java, Surface.Env, Surface.FS, Surface.Secrets, Surface.Validation, UI, Zastava Observer, Zastava Webhook, Zastava Core, and Plugin Platform.
- Each charter outlines the mission, scope, required reading, and working agreements for the respective guilds.
- Created task boards for Surface.Env, Surface.FS, Surface.Secrets, Surface.Validation, and Zastava components to track progress and dependencies.
- Ensured all documents emphasize determinism, offline readiness, security, and integration with shared Surface libraries.
This commit is contained in:
master
2025-11-01 02:21:46 +02:00
parent e5629454cf
commit 66cb6c4b8a
227 changed files with 9913 additions and 6210 deletions
Download Patch File Download Diff File Expand all files Collapse all files

41
src/Sdk/StellaOps.Sdk.Generator/AGENTS.md
View File

@@ -1,15 +1,26 @@
# SDK Generator Guild Charter
## Mission
Generate and maintain official StellaOps SDKs across supported languages using reproducible code generation pipelines.
## Scope
- Manage code generation templates and tooling for TS, Python, Go, Java (C#/Rust follow-ons).
- Implement post-processing hooks for auth helpers, retries, paginators, error mapping, and telemetry.
- Provide language-specific smoke tests, example snippets, and continuous integration.
- Coordinate with Release Guild for publishing and version bumps.
## Definition of Done
- SDKs regenerate deterministically from `stella.yaml` without manual edits.
- Smoke tests and integration suites run per language in CI.
- Generated code adheres to language-specific style guides and passes lint/format checks.
# SDK Generator Guild Charter
## Mission
Generate and maintain official StellaOps SDKs across supported languages using reproducible code generation pipelines.
## Scope
- Manage code generation templates and tooling for TS, Python, Go, Java (C#/Rust follow-ons).
- Implement post-processing hooks for auth helpers, retries, paginators, error mapping, and telemetry.
- Provide language-specific smoke tests, example snippets, and continuous integration.
- Coordinate with Release Guild for publishing and version bumps.
## Definition of Done
- SDKs regenerate deterministically from `stella.yaml` without manual edits.
- Smoke tests and integration suites run per language in CI.
- Generated code adheres to language-specific style guides and passes lint/format checks.
## Required Reading
- `docs/modules/platform/architecture.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.
- 2. Review this charter and the Required Reading documents before coding; confirm prerequisites are met.
- 3. Keep changes deterministic (stable ordering, timestamps, hashes) and align with offline/air-gap expectations.
- 4. Coordinate doc updates, tests, and cross-guild communication whenever contracts or workflows change.
- 5. Revert to `TODO` if you pause the task without shipping changes; leave notes in commit/PR descriptions for context.

41
src/Sdk/StellaOps.Sdk.Release/AGENTS.md
View File

@@ -1,15 +1,26 @@
# SDK Release Guild Charter
## Mission
Own packaging, signing, publishing, and changelog automation for official StellaOps SDKs and dev portal bundles.
## Scope
- Manage language-specific release pipelines (npm, PyPI, Maven, Go modules) with provenance signing.
- Automate changelog generation and SemVer version bumps aligned with API releases.
- Coordinate publication of offline bundles for air-gapped environments.
- Operate release dashboards and notification hooks for SDK updates.
## Definition of Done
- Every SDK release is reproducible, signed, and accompanied by changelog + provenance.
- Registries updated via automated pipeline with rollback strategy.
- Offline bundle creation integrated with Export Center workflows.
# SDK Release Guild Charter
## Mission
Own packaging, signing, publishing, and changelog automation for official StellaOps SDKs and dev portal bundles.
## Scope
- Manage language-specific release pipelines (npm, PyPI, Maven, Go modules) with provenance signing.
- Automate changelog generation and SemVer version bumps aligned with API releases.
- Coordinate publication of offline bundles for air-gapped environments.
- Operate release dashboards and notification hooks for SDK updates.
## Definition of Done
- Every SDK release is reproducible, signed, and accompanied by changelog + provenance.
- Registries updated via automated pipeline with rollback strategy.
- Offline bundle creation integrated with Export Center workflows.
## Required Reading
- `docs/modules/platform/architecture.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.
- 2. Review this charter and the Required Reading documents before coding; confirm prerequisites are met.
- 3. Keep changes deterministic (stable ordering, timestamps, hashes) and align with offline/air-gap expectations.
- 4. Coordinate doc updates, tests, and cross-guild communication whenever contracts or workflows change.
- 5. Revert to `TODO` if you pause the task without shipping changes; leave notes in commit/PR descriptions for context.