@kevin0181/memoc 1.4.6 → 1.4.11

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.
@@ -1,27 +0,0 @@
1
- ---
2
- name: memoc-upgrade
3
- description: >
4
- Upgrade memoc runtime and wrappers in the current project without deleting existing memory.
5
- Refreshes managed sections based on current project state.
6
- Trigger: /memoc-upgrade, "upgrade memoc", "update memoc", "refresh memoc runtime".
7
- ---
8
-
9
- Run `memoc upgrade` in the current working directory.
10
-
11
- ## Steps
12
-
13
- 1. **Find binary** (priority order):
14
- - Windows: `.\.memoc\bin\memoc.cmd upgrade`
15
- - macOS/Linux: `.memoc/bin/memoc upgrade`
16
- - Fallback: `npx @kevin0181/memoc@latest upgrade`
17
-
18
- 2. **Run upgrade** and capture output.
19
-
20
- 3. **Report**:
21
- - Which files were refreshed vs preserved
22
- - New memoc version vs previous version (if shown)
23
- - Any managed sections that were updated
24
-
25
- ## Key behavior
26
-
27
- Upgrade preserves all manually-written memory content. Only memoc-managed sections (marked with `<!-- memoc:managed -->` or equivalent) are updated. User-written content is never overwritten.
@@ -1,31 +0,0 @@
1
- ---
2
- name: memoc-work
3
- description: >
4
- Create a conflict-light actor worklog entry for the current work session.
5
- Records what was done, by whom, and when — for shared repos with multiple actors.
6
- Trigger: /memoc-work, "log work", "create worklog", "record what I did",
7
- "add work entry", "memoc log session".
8
- ---
9
-
10
- Run `memoc work "<title>"` in the current working directory.
11
-
12
- ## Steps
13
-
14
- 1. **Get title** from user's message or args. If not provided, ask: "Brief title for this work entry?"
15
-
16
- 2. **Find binary** (priority order):
17
- - Windows: `.\.memoc\bin\memoc.cmd work "<title>"`
18
- - macOS/Linux: `.memoc/bin/memoc work "<title>"`
19
- - Fallback: `npx @kevin0181/memoc@latest work "<title>"`
20
-
21
- 3. **Run command** and report the created file path.
22
-
23
- 4. **Open the file** and help user fill in the work details:
24
- - What was done
25
- - Files changed
26
- - Decisions made
27
- - Next steps
28
-
29
- ## Entry format
30
-
31
- Worklog entries are Markdown scaffolds stored per-actor to avoid merge conflicts in shared repos. Each entry is timestamped and attributed to the current actor (`memoc actor` to check/set).