@pcircle/memesh 2.9.1 → 2.9.2
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,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@pcircle/memesh",
|
|
3
|
-
"version": "2.9.
|
|
3
|
+
"version": "2.9.2",
|
|
4
4
|
"description": "MeMesh — Persistent memory plugin for Claude Code. Remembers architecture decisions, coding patterns, and project context across sessions.",
|
|
5
5
|
"main": "dist/index.js",
|
|
6
6
|
"type": "module",
|
|
@@ -1,46 +0,0 @@
|
|
|
1
|
-
## Required Plan Sections
|
|
2
|
-
|
|
3
|
-
Your plan MUST include all of the following sections. Incomplete plans will be rejected.
|
|
4
|
-
|
|
5
|
-
### 1. System Design Description (SDD)
|
|
6
|
-
- Component architecture and responsibilities
|
|
7
|
-
- Data flow between components
|
|
8
|
-
- Interface contracts (input/output types)
|
|
9
|
-
- Dependencies and integration points
|
|
10
|
-
|
|
11
|
-
### 2. Behavior-Driven Design (BDD)
|
|
12
|
-
For EACH feature, write Gherkin scenarios:
|
|
13
|
-
|
|
14
|
-
```gherkin
|
|
15
|
-
Scenario: [descriptive name]
|
|
16
|
-
Given [precondition]
|
|
17
|
-
When [action]
|
|
18
|
-
Then [expected outcome]
|
|
19
|
-
```
|
|
20
|
-
|
|
21
|
-
Cover: happy path, error path, edge cases.
|
|
22
|
-
|
|
23
|
-
### 3. Edge Case Handling
|
|
24
|
-
|
|
25
|
-
| Edge Case | How Handled | Test Coverage |
|
|
26
|
-
|-----------|------------|---------------|
|
|
27
|
-
| [case] | [strategy] | [yes/no] |
|
|
28
|
-
|
|
29
|
-
Include at minimum: empty input, null/undefined, boundary values, concurrent access, timeout, large data.
|
|
30
|
-
|
|
31
|
-
### 4. Dry-Run Test Plan
|
|
32
|
-
Before dispatching heavy tasks, verify:
|
|
33
|
-
- [ ] Core function compiles (`tsc --noEmit` or `node --check`)
|
|
34
|
-
- [ ] Unit test for critical path passes
|
|
35
|
-
- [ ] Integration point verified with real call
|
|
36
|
-
- [ ] No regressions in existing tests
|
|
37
|
-
|
|
38
|
-
### 5. Risk Assessment
|
|
39
|
-
|
|
40
|
-
| Risk | Probability | Impact | Mitigation |
|
|
41
|
-
|------|------------|--------|------------|
|
|
42
|
-
| [risk] | High/Med/Low | High/Med/Low | [strategy] |
|
|
43
|
-
|
|
44
|
-
---
|
|
45
|
-
|
|
46
|
-
**IMPORTANT**: After completing this plan, present it to the user and wait for explicit approval before proceeding to implementation. Do NOT auto-execute.
|