fix: retain global review precedence in entry guidance
This commit is contained in:
1 parent
35f0a7259c
commit
818869fae9
2 files changed
+3
-2
No files matched your search
@@ -51,7 +51,7 @@ This channel skill owns **delivery governance and project-channel coordination**
|
||||
| Taskfile, `.scripts/`, shell wrappers, environment validation, and Devbox | `development-scripts` | https://gitea.lego-cloud.eu/global-skills/development-scripts |
|
||||
| Gondor Argo CD template, rendered desired state, and repository connection | `development-gitops-argo-cd-home-gondor-v1` | https://gitea.lego-cloud.eu/home-gondor-v1-skills/development-gitops-argo-cd-home-gondor-v1 |
|
||||
|
||||
The channel skill may narrow authority, lifecycle, workspace, visibility, handoff, and evidence requirements. When a project/channel overlay conflicts with a reusable skill on branch naming, human confirmation, worker count, review identity, merge authority, deployment authority, or release authority, the explicit project/channel overlay wins; inherit only the non-conflicting mechanics. It must not restate generic RED–GREEN–REFACTOR mechanics, shell-module layouts, pnpm workspace conventions, ordinary Git branching mechanics, exact-head gate algorithms, or Argo CD authoring procedures. Improve those reusable skills at their linked sources and keep only the project/channel overlay here.
|
||||
The channel skill may narrow authority, lifecycle, workspace, visibility, handoff, and evidence requirements. Project bindings must not contradict global skills. The global `development-gates` contract governs independent review, review-before-push ordering, candidate/base identity and CI. Project overlays supply branch naming, human ownership, one implementation worker, visibility and existing merge/deployment/release authority without weakening these gates; inherit only non-conflicting mechanics. It must not restate generic RED–GREEN–REFACTOR mechanics, shell-module layouts, pnpm workspace conventions, ordinary Git branching mechanics, exact-head gate algorithms, or Argo CD authoring procedures. Improve those reusable skills at their linked sources and keep only the project/channel overlay here.
|
||||
|
||||
## Implementation Entry Gate
|
||||
|
||||
|
||||
@@ -27,7 +27,8 @@ def test_delivery_reference_routes_reusable_development_procedures() -> None:
|
||||
def test_generic_automation_is_owned_by_development_scripts() -> None:
|
||||
assert "`development-scripts` owns Taskfile, `.scripts/`" in SKILL
|
||||
assert "must not restate generic RED–GREEN–REFACTOR mechanics" in SKILL
|
||||
assert "the explicit project/channel overlay wins" in SKILL
|
||||
assert "Project bindings must not contradict global skills" in SKILL
|
||||
assert "the explicit project/channel overlay wins" not in SKILL
|
||||
|
||||
|
||||
def test_gitops_reference_requires_one_environment_per_repository() -> None:
|
||||
|
||||
Reference in new issue
Block a user