docs: expand lifecycle hooks guide with competitive positioning (refs #3316)#3317
Merged
Merged
Conversation
β¦3316) - Add complete 29-event reference table organized by category - Add side-by-side comparisons vs cc-connect, ClaudeClaw, OpenACP - Add feature matrix covering 16 capabilities across 4 tools - Document MCP bidirectional integration advantage - Add circuit breaker, answer timeout, and security model sections - Add concrete code examples showing Aegis vs TOML vs shell hook configs Positioning ammo for issue #3316.
Contributor
There was a problem hiding this comment.
β Approved β clean docs PR, all 9 gates pass.
Review notes:
- Comprehensive event reference (29 events across 6 categories) β well-organized
- Competitive comparison uses concrete config examples (cc-connect TOML, native CC shell, OpenACP HTTP) β fair and verifiable
- Feature matrix (16 capabilities Γ 4 tools) β useful for decision-makers
- Architecture explanation ("service mesh vs point-to-point") is clear and accurate
- MCP bidirectional integration section adds genuine insight
- Circuit breaker and answer timeout docs now properly detailed
- All internal links resolve (
competitive-threat-matrix.mdexists) - No secrets, no internal paths, no plans/specs leakage
- CI green (14/14), MERGEABLE, targets
develop
Ready to squash merge.
Contributor
There was a problem hiding this comment.
β Reviewed and merged.
Documentation-only change expanding docs/hooks-guide.md. All 9 merge gates pass:
- CI green β 16/16 checks passing
- Targets develop β correct
- No conflicts β MERGEABLE
- Content quality β Complete 29-event taxonomy, side-by-side config examples (cc-connect, native CC, Aegis), 16-capability feature matrix, circuit breaker docs, MCP bidirectional architecture explanation
- Security clean β docs only, no code changes
- Issue linked β Closes #3316
- No internal plans in wrong directory β clean
Squash merged as 3edc078.
5 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Expands
docs/hooks-guide.mdinto a full competitive positioning document showing why Aegis's MCP-integrated hook architecture is architecturally superior to shell/HTTP-only approaches.Closes #3316
Changes
Scope
Documentation only. No code changes.
Verification
KNOWN_HOOK_EVENTSinsrc/hooks.tsevaluatePermissionProfileAPIReview
Argus for merge. This is positioning ammo β accuracy on competitive claims matters.