azclaude-copilot 0.4.10 → 0.4.12
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "azclaude-copilot",
|
|
3
|
-
"version": "0.4.
|
|
4
|
-
"description": "AI coding environment —
|
|
3
|
+
"version": "0.4.12",
|
|
4
|
+
"description": "AI coding environment — 27 commands, 8 skills, 13 agents, memory, reflexes, evolution. Install: npm install -g azclaude-copilot@latest, then in Claude Code: azclaude-copilot setup --full",
|
|
5
5
|
"bin": {
|
|
6
6
|
"azclaude": "bin/cli.js",
|
|
7
7
|
"azclaude-copilot": "bin/copilot.js"
|
|
@@ -22,9 +22,9 @@ Read only what's recent and relevant:
|
|
|
22
22
|
|
|
23
23
|
### CONSOLIDATE
|
|
24
24
|
Group harvested content by pattern:
|
|
25
|
-
- Same friction appearing in
|
|
26
|
-
- Same workflow appearing in
|
|
27
|
-
- Same fact referenced in
|
|
25
|
+
- Same friction appearing in 2+ sessions → candidate for re-derivation
|
|
26
|
+
- Same workflow appearing in 2+ sessions → candidate for skill
|
|
27
|
+
- Same fact referenced in 2+ files → candidate for knowledge-index entry
|
|
28
28
|
|
|
29
29
|
Rules:
|
|
30
30
|
- Do not consolidate single-occurrence items — they are noise
|
|
@@ -90,7 +90,7 @@ If PLAN is empty: skip to Cycle 2.
|
|
|
90
90
|
|
|
91
91
|
---
|
|
92
92
|
|
|
93
|
-
## Cycle 2: Knowledge Consolidation (if sessions ≥
|
|
93
|
+
## Cycle 2: Knowledge Consolidation (if sessions ≥ 2 since last consolidation)
|
|
94
94
|
|
|
95
95
|
Read `capabilities/evolution/cycle2-knowledge.md` and run.
|
|
96
96
|
Outputs: consolidated patterns, pruned stale memory, enriched knowledge-index
|
|
@@ -57,12 +57,23 @@ Parse $ARGUMENTS:
|
|
|
57
57
|
Check if hooks were modified outside of AZCLAUDE.
|
|
58
58
|
|
|
59
59
|
```bash
|
|
60
|
-
|
|
61
|
-
|
|
60
|
+
# Project-level (preferred) — hooks are registered in .claude/settings.local.json
|
|
61
|
+
PROJECT_INTEGRITY=".claude/.azclaude-integrity"
|
|
62
|
+
PROJECT_SETTINGS=".claude/settings.local.json"
|
|
63
|
+
# Global fallback
|
|
64
|
+
GLOBAL_INTEGRITY="$HOME/.claude/.azclaude-integrity"
|
|
62
65
|
if [ -n "$APPDATA" ]; then
|
|
63
|
-
|
|
66
|
+
GLOBAL_SETTINGS="$APPDATA/Claude/settings.json"
|
|
64
67
|
else
|
|
65
|
-
|
|
68
|
+
GLOBAL_SETTINGS="$HOME/.claude/settings.json"
|
|
69
|
+
fi
|
|
70
|
+
# Use project-level if both project files exist; otherwise fall back to global
|
|
71
|
+
if [ -f "$PROJECT_INTEGRITY" ] && [ -f "$PROJECT_SETTINGS" ]; then
|
|
72
|
+
INTEGRITY="$PROJECT_INTEGRITY"; SETTINGS="$PROJECT_SETTINGS"
|
|
73
|
+
echo "integrity_scope=project"
|
|
74
|
+
else
|
|
75
|
+
INTEGRITY="$GLOBAL_INTEGRITY"; SETTINGS="$GLOBAL_SETTINGS"
|
|
76
|
+
echo "integrity_scope=global"
|
|
66
77
|
fi
|
|
67
78
|
[ -f "$INTEGRITY" ] && echo "integrity_file=found" || echo "integrity_file=missing"
|
|
68
79
|
[ -f "$SETTINGS" ] && echo "settings_file=found" || echo "settings_file=missing"
|
|
@@ -70,15 +81,13 @@ fi
|
|
|
70
81
|
|
|
71
82
|
If both exist:
|
|
72
83
|
```bash
|
|
73
|
-
cat "$
|
|
84
|
+
cat "$INTEGRITY"
|
|
74
85
|
```
|
|
75
|
-
Compute SHA-256 of the `hooks` key in
|
|
86
|
+
Compute SHA-256 of the `hooks` key in `$SETTINGS` and compare.
|
|
76
87
|
- Match → +25 pts — "Hook integrity verified"
|
|
77
88
|
- Mismatch → +0 pts — **BLOCK** "Hook integrity mismatch — hooks modified outside AZCLAUDE"
|
|
78
89
|
- Missing integrity file → +15 pts — "No integrity baseline (run `npx azclaude install` to establish one)"
|
|
79
90
|
|
|
80
|
-
Note: AZCLAUDE registers hooks in `.claude/settings.local.json` (project-level), not `~/.claude/settings.json` (global). The integrity baseline must be computed against `settings.local.json` — comparing against global settings will always produce a hash mismatch (MEDIUM finding).
|
|
81
|
-
|
|
82
91
|
Check each hook script for dangerous patterns:
|
|
83
92
|
```bash
|
|
84
93
|
ls .claude/hooks/ 2>/dev/null || ls "$HOME/.claude/hooks/" 2>/dev/null
|