@every-env/compound-plugin 2.34.5 → 2.34.6
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/CHANGELOG.md
CHANGED
|
@@ -7,6 +7,13 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
|
|
|
7
7
|
|
|
8
8
|
Release numbering now follows the repository `v*` tag line. Starting at `v2.34.0`, the root CLI package and this changelog stay on that shared version stream. Older entries below retain the previous `0.x` CLI numbering.
|
|
9
9
|
|
|
10
|
+
## [2.34.6](https://github.com/EveryInc/compound-engineering-plugin/compare/v2.34.5...v2.34.6) (2026-03-10)
|
|
11
|
+
|
|
12
|
+
|
|
13
|
+
### Bug Fixes
|
|
14
|
+
|
|
15
|
+
* **mcp:** add API key auth support for Context7 server ([c649cfc](https://github.com/EveryInc/compound-engineering-plugin/commit/c649cfc17f895b58babf737dfdec2f6cc391e40a)), closes [#153](https://github.com/EveryInc/compound-engineering-plugin/issues/153)
|
|
16
|
+
|
|
10
17
|
## [2.34.5](https://github.com/EveryInc/compound-engineering-plugin/compare/v2.34.4...v2.34.5) (2026-03-10)
|
|
11
18
|
|
|
12
19
|
|
package/package.json
CHANGED
|
@@ -53,12 +53,11 @@ Agents are organized into categories for easier discovery.
|
|
|
53
53
|
| `design-iterator` | Iteratively refine UI through systematic design iterations |
|
|
54
54
|
| `figma-design-sync` | Synchronize web implementations with Figma designs |
|
|
55
55
|
|
|
56
|
-
### Workflow (
|
|
56
|
+
### Workflow (4)
|
|
57
57
|
|
|
58
58
|
| Agent | Description |
|
|
59
59
|
|-------|-------------|
|
|
60
60
|
| `bug-reproduction-validator` | Systematically reproduce and validate bug reports |
|
|
61
|
-
| `every-style-editor` | Edit content to conform to Every's style guide |
|
|
62
61
|
| `lint` | Run linting and code quality checks on Ruby and ERB files |
|
|
63
62
|
| `pr-comment-resolver` | Address PR comments and implement fixes |
|
|
64
63
|
| `spec-flow-analyzer` | Analyze user flows and identify gaps in specifications |
|
|
@@ -190,6 +189,8 @@ Supports 100+ frameworks including Rails, React, Next.js, Vue, Django, Laravel,
|
|
|
190
189
|
|
|
191
190
|
MCP servers start automatically when the plugin is enabled.
|
|
192
191
|
|
|
192
|
+
**Authentication:** To avoid anonymous rate limits, set the `CONTEXT7_API_KEY` environment variable with your Context7 API key. The plugin passes this automatically via the `x-api-key` header. Without it, requests go unauthenticated and will quickly hit the anonymous quota limit.
|
|
193
|
+
|
|
193
194
|
## Browser Automation
|
|
194
195
|
|
|
195
196
|
This plugin uses **agent-browser CLI** for browser automation tasks. Install it globally:
|
|
@@ -220,13 +221,16 @@ claude /plugin install compound-engineering
|
|
|
220
221
|
"mcpServers": {
|
|
221
222
|
"context7": {
|
|
222
223
|
"type": "http",
|
|
223
|
-
"url": "https://mcp.context7.com/mcp"
|
|
224
|
+
"url": "https://mcp.context7.com/mcp",
|
|
225
|
+
"headers": {
|
|
226
|
+
"x-api-key": "${CONTEXT7_API_KEY:-}"
|
|
227
|
+
}
|
|
224
228
|
}
|
|
225
229
|
}
|
|
226
230
|
}
|
|
227
231
|
```
|
|
228
232
|
|
|
229
|
-
Or add it globally in `~/.claude/settings.json` for all projects.
|
|
233
|
+
Set `CONTEXT7_API_KEY` in your environment to authenticate. Or add it globally in `~/.claude/settings.json` for all projects.
|
|
230
234
|
|
|
231
235
|
## Version History
|
|
232
236
|
|
|
@@ -21,7 +21,45 @@ Captures problem solutions while context is fresh, creating structured documenta
|
|
|
21
21
|
/ce:compound [brief context] # Provide additional context hint
|
|
22
22
|
```
|
|
23
23
|
|
|
24
|
-
## Execution Strategy:
|
|
24
|
+
## Execution Strategy: Context-Aware Orchestration
|
|
25
|
+
|
|
26
|
+
### Phase 0: Context Budget Check
|
|
27
|
+
|
|
28
|
+
<critical_requirement>
|
|
29
|
+
**Run this check BEFORE launching any subagents.**
|
|
30
|
+
|
|
31
|
+
The /compound command is token-heavy - it launches 5 parallel subagents that collectively consume ~10k tokens of context. Running near context limits risks compaction mid-compound, which degrades output quality significantly.
|
|
32
|
+
</critical_requirement>
|
|
33
|
+
|
|
34
|
+
Before proceeding, the orchestrator MUST:
|
|
35
|
+
|
|
36
|
+
1. **Assess context usage**: Check how long the current conversation has been running. If there has been significant back-and-forth (many tool calls, large file reads, extensive debugging), context is likely constrained.
|
|
37
|
+
|
|
38
|
+
2. **Warn the user**:
|
|
39
|
+
```
|
|
40
|
+
⚠️ Context Budget Check
|
|
41
|
+
|
|
42
|
+
/compound launches 5 parallel subagents (~10k tokens). Long conversations
|
|
43
|
+
risk compaction mid-compound, which degrades documentation quality.
|
|
44
|
+
|
|
45
|
+
Tip: For best results, run /compound early in a session - right after
|
|
46
|
+
verifying a fix, before continuing other work.
|
|
47
|
+
```
|
|
48
|
+
|
|
49
|
+
3. **Offer the user a choice**:
|
|
50
|
+
```
|
|
51
|
+
How would you like to proceed?
|
|
52
|
+
|
|
53
|
+
1. Full compound (5 parallel subagents, ~10k tokens) - best quality
|
|
54
|
+
2. Compact-safe mode (single pass, ~2k tokens) - safe near context limits
|
|
55
|
+
```
|
|
56
|
+
|
|
57
|
+
4. **If the user picks option 1** (or confirms full mode): proceed to Phase 1 below.
|
|
58
|
+
5. **If the user picks option 2** (or requests compact-safe): skip to the **Compact-Safe Mode** section below.
|
|
59
|
+
|
|
60
|
+
---
|
|
61
|
+
|
|
62
|
+
### Full Mode
|
|
25
63
|
|
|
26
64
|
<critical_requirement>
|
|
27
65
|
**Only ONE file gets written - the final documentation.**
|
|
@@ -99,6 +137,44 @@ Based on problem type, optionally invoke specialized agents to review the docume
|
|
|
99
137
|
|
|
100
138
|
</parallel_tasks>
|
|
101
139
|
|
|
140
|
+
---
|
|
141
|
+
|
|
142
|
+
### Compact-Safe Mode
|
|
143
|
+
|
|
144
|
+
<critical_requirement>
|
|
145
|
+
**Single-pass alternative for context-constrained sessions.**
|
|
146
|
+
|
|
147
|
+
When context budget is tight, this mode skips parallel subagents entirely. The orchestrator performs all work in a single pass, producing a minimal but complete solution document.
|
|
148
|
+
</critical_requirement>
|
|
149
|
+
|
|
150
|
+
The orchestrator (main conversation) performs ALL of the following in one sequential pass:
|
|
151
|
+
|
|
152
|
+
1. **Extract from conversation**: Identify the problem, root cause, and solution from conversation history
|
|
153
|
+
2. **Classify**: Determine category and filename (same categories as full mode)
|
|
154
|
+
3. **Write minimal doc**: Create `docs/solutions/[category]/[filename].md` with:
|
|
155
|
+
- YAML frontmatter (title, category, date, tags)
|
|
156
|
+
- Problem description (1-2 sentences)
|
|
157
|
+
- Root cause (1-2 sentences)
|
|
158
|
+
- Solution with key code snippets
|
|
159
|
+
- One prevention tip
|
|
160
|
+
4. **Skip specialized agent reviews** (Phase 3) to conserve context
|
|
161
|
+
|
|
162
|
+
**Compact-safe output:**
|
|
163
|
+
```
|
|
164
|
+
✓ Documentation complete (compact-safe mode)
|
|
165
|
+
|
|
166
|
+
File created:
|
|
167
|
+
- docs/solutions/[category]/[filename].md
|
|
168
|
+
|
|
169
|
+
Note: This was created in compact-safe mode. For richer documentation
|
|
170
|
+
(cross-references, detailed prevention strategies, specialized reviews),
|
|
171
|
+
re-run /compound in a fresh session.
|
|
172
|
+
```
|
|
173
|
+
|
|
174
|
+
**No subagents are launched. No parallel tasks. One file written.**
|
|
175
|
+
|
|
176
|
+
---
|
|
177
|
+
|
|
102
178
|
## What It Captures
|
|
103
179
|
|
|
104
180
|
- **Problem symptom**: Exact error messages, observable behavior
|