zsp/everything-claude-code
1
0
Fork 0
mirror of https://github.com/affaan-m/everything-claude-code.git synced 2026-05-15 13:23:13 +08:00
Code Issues Packages Projects Releases Wiki Activity

feat: add observability readiness gate

Browse Source
This commit is contained in:
Affaan Mustafa
2026-05-11 18:23:53 -04:00
committed by Affaan Mustafa
parent ab6e998383
commit 8aa8c32d2a
9 changed files with 624 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
docs/releases/2.0.0-rc.1/quickstart.md
View File

@@ -31,6 +31,15 @@ Expected result: every test passes with zero failures. For release-specific drif
node tests/docs/ecc2-release-surface.test.js
```
Then check the local observability surface:
```bash
npm run observability:ready
```
This runs the [observability readiness gate](../../architecture/observability-readiness.md)
for loop status, session traces, harness audit, and ECC2 tool-risk logs.
## First Skill
Read `skills/hermes-imports/SKILL.md` first.

8
docs/releases/2.0.0-rc.1/release-notes.md
View File

@@ -13,6 +13,7 @@ Claude Code remains a core target. Codex, OpenCode, Cursor, Gemini, and other ha
- Clarified the split between ECC as the reusable substrate and Hermes as the operator shell.
- Documented the cross-harness portability model for skills, hooks, MCPs, rules, and instructions.
- Added a Hermes import playbook for turning local operator patterns into publishable ECC skills.
- Added a local [observability readiness gate](../../architecture/observability-readiness.md) for loop status, session traces, harness audit, and ECC2 tool-risk logs.
## Why This Matters
@@ -50,6 +51,7 @@ What stays local:
1. Follow the [rc.1 quickstart](quickstart.md).
2. Read the [Hermes setup guide](../../HERMES-SETUP.md).
3. Review the [cross-harness architecture](../../architecture/cross-harness.md).
4. Start with one workflow lane: engineering, research, content, or outreach.
5. Import only sanitized operator patterns into ECC skills.
6. Treat `ecc2/` as an alpha control plane until release packaging and installer behavior are finalized.
4. Run the [observability readiness gate](../../architecture/observability-readiness.md).
5. Start with one workflow lane: engineering, research, content, or outreach.
6. Import only sanitized operator patterns into ECC skills.
7. Treat `ecc2/` as an alpha control plane until release packaging and installer behavior are finalized.