vibe-coding-master 0.3.15 → 0.3.16
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/dist/backend/api/codex-translation-routes.js +4 -0
- package/dist/backend/services/codex-translation-service.js +168 -12
- package/dist-frontend/assets/{index-DFjuPlsk.js → index-BNJJ_Tcf.js} +19 -19
- package/dist-frontend/index.html +1 -1
- package/docs/codex-translation-plan.md +27 -8
- package/package.json +1 -1
package/dist-frontend/index.html
CHANGED
|
@@ -4,7 +4,7 @@
|
|
|
4
4
|
<meta charset="UTF-8" />
|
|
5
5
|
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
|
|
6
6
|
<title>VibeCodingMaster</title>
|
|
7
|
-
<script type="module" crossorigin src="/assets/index-
|
|
7
|
+
<script type="module" crossorigin src="/assets/index-BNJJ_Tcf.js"></script>
|
|
8
8
|
<link rel="stylesheet" crossorigin href="/assets/index-C1FPjOXU.css">
|
|
9
9
|
</head>
|
|
10
10
|
<body>
|
|
@@ -166,7 +166,7 @@ be computed from `getTaskRuntimeRepoRoot()` or any task worktree root.
|
|
|
166
166
|
|
|
167
167
|
Translation memory should be explicit files, not just model memory.
|
|
168
168
|
|
|
169
|
-
|
|
169
|
+
Core files:
|
|
170
170
|
|
|
171
171
|
- `translations/memory/glossary.md`: approved translations for project terms,
|
|
172
172
|
product names, protocol names, module names, acronyms, and phrases.
|
|
@@ -177,6 +177,16 @@ Recommended files:
|
|
|
177
177
|
translation accuracy.
|
|
178
178
|
- `translations/memory/decisions.md`: dated translation decisions and exceptions.
|
|
179
179
|
|
|
180
|
+
VCM must keep translation memory compact and predictable:
|
|
181
|
+
|
|
182
|
+
- the four core files are the only long-term memory files
|
|
183
|
+
- the four core files together must stay at or below `80KB`
|
|
184
|
+
- no archive, reports, candidates, scratch, log, or helper files should be
|
|
185
|
+
created under `translations/memory/`
|
|
186
|
+
- runtime request files for memory work are allowed under
|
|
187
|
+
`translations/runtime/memory-updates/`, and VCM deletes them after successful
|
|
188
|
+
completion
|
|
189
|
+
|
|
180
190
|
Codex Translator must read these files before each file translation job and may
|
|
181
191
|
use them for conversation translation. It may update them only when it discovers
|
|
182
192
|
a stable convention that should affect future translations. It must not store
|
|
@@ -184,10 +194,19 @@ transient task chatter, progress notes, or failed attempts in memory files.
|
|
|
184
194
|
|
|
185
195
|
Memory updates are automatic by default. Codex Translator may append stable
|
|
186
196
|
terms, style conventions, project context, and translation decisions to the
|
|
187
|
-
appropriate memory file without a separate approval step
|
|
188
|
-
|
|
189
|
-
|
|
190
|
-
|
|
197
|
+
appropriate memory file without a separate approval step, but it must compact
|
|
198
|
+
duplicates and stay within the `80KB` core-memory budget. The user may directly
|
|
199
|
+
edit memory files, ask Codex Translator to revise them in the embedded terminal,
|
|
200
|
+
or use the sidebar `Update memory` action to queue a dedicated memory
|
|
201
|
+
compaction pass.
|
|
202
|
+
|
|
203
|
+
The manual `Update memory` action is a single-threaded Codex Translator queue
|
|
204
|
+
item. It asks the long-lived translator session to use its current context,
|
|
205
|
+
recent stable user corrections, completed translation behavior, and existing
|
|
206
|
+
memory files to rewrite only the four core memory files. It must not create a
|
|
207
|
+
separate report or archive. On the Codex `Stop` hook, VCM validates that the
|
|
208
|
+
core memory total is at most `80KB` and that the memory directory contains no
|
|
209
|
+
non-core artifacts before marking the queue item complete.
|
|
191
210
|
|
|
192
211
|
Memory file format rules:
|
|
193
212
|
|
|
@@ -196,9 +215,9 @@ Memory file format rules:
|
|
|
196
215
|
translation, or conversation translation.
|
|
197
216
|
- User-edited entries have highest priority. Codex Translator must not overwrite
|
|
198
217
|
them automatically.
|
|
199
|
-
- If Codex finds a conflict with a user-edited entry, it should
|
|
200
|
-
|
|
201
|
-
|
|
218
|
+
- If Codex finds a conflict with a user-edited entry, it should leave the user
|
|
219
|
+
entry unchanged and mention the conflict only in the active runtime output or
|
|
220
|
+
terminal discussion.
|
|
202
221
|
- Duplicate terms should be merged only when the existing entry is automatic
|
|
203
222
|
and the meaning is clearly the same.
|
|
204
223
|
- `decisions.md` entries should explain the reason for the decision, not just
|