@ngocsangairvds/vsaf 5.5.1 → 5.5.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ngocsangairvds/vsaf",
-  "version": "5.5.1",
+  "version": "5.5.2",
   "description": "logging step",
   "main": "packages/core/dist/index.js",
   "types": "packages/core/dist/index.d.ts",

package/skills/sdlc/onboard-code/SKILL.md

@@ -142,7 +142,10 @@ Icon: `⏳` running, `✅` done, `❌` error.
     - Code module (from GitNexus) → is there a corresponding business concept? (check graph.json)
       - YES → record mapping
       - NO → technical module (infra, utils) — OK, record note
-17. Update `CONTEXT.md` with technical terms from code:
+17. Update `CONTEXT.md` with technical terms from code — IDEMPOTENTLY (never overwrite the whole file, never
+    blind-append; re-runs must not bloat it): PRESERVE the `## Shared Language` section written by onboard-docs;
+    own `## Cross-Domain Verification` + `## Technical Terms` — if a section exists REPLACE its body in place,
+    else append it; one row per mapping/term (dedupe, update rather than duplicate):
 
 ```markdown
 ## Technical Terms

package/skills/sdlc/onboard-docs/SKILL.md

@@ -155,7 +155,10 @@ Print conversion summary:
 [ONBOARD-DOCS] [4/4] Extract domain terms → CONTEXT.md... ⏳
 ```
 
-15. From the completed graph, extract domain terms → `CONTEXT.md`
+15. From the completed graph, extract domain terms → `CONTEXT.md` — update IDEMPOTENTLY (never overwrite the
+    whole file, never blind-append; re-runs must not bloat it): ensure one top `# Project Context: {name}`
+    heading, then own the `## Shared Language` section — if it exists REPLACE its body in place, else append it;
+    leave other sections (`## Technical Terms`, `## Cross-Domain Verification`) untouched; one row per Term (dedupe).
 16. Format Shared Language table:
 
 ```markdown

package/workflows/sdlc/onboard-code.yaml

@@ -87,7 +87,11 @@ nodes:
       Read `graphify-out/graph.json` (the docs graph from onboard-docs — READ ONLY) and query the code via GitNexus (`query`, `context`). Cross-reference:
       - business concept (graph.json) → is there a matching code module? YES → record `{concept} ↔ {module/class}`; NO → "{concept} not yet implemented".
       - code module (GitNexus) → matching business concept? YES → mapping; NO → technical module (infra/utils), record as such.
-      Append a "## Technical Terms" table to `CONTEXT.md` (| Term | Definition | Maps to Business Concept |).
+      Update `CONTEXT.md` IDEMPOTENTLY — never overwrite the whole file, and never blind-append (re-runs would bloat it). Manage BY SECTION:
+      - PRESERVE the `## Shared Language` section written by onboard-docs — do NOT delete or rewrite it.
+      - You OWN `## Cross-Domain Verification` (the concept↔module mappings above) and `## Technical Terms`
+        (table: | Term | Definition | Maps to Business Concept |). If a section already exists, REPLACE its body in place; otherwise append it.
+      - Keep ONE row per mapping/term (dedupe by key) — update rather than duplicate.
       Flag any cross-database access. If `graphify-out/graph.json` is absent, note that onboard-docs must run first.
 
   - id: summary

package/workflows/sdlc/onboard-docs.yaml

@@ -83,7 +83,16 @@ nodes:
       Print progress `[ONBOARD-DOCS] [4/4] Extract domain terms → CONTEXT.md... ⏳/✅`.
 
       From the completed `graph.json`, extract DOMAIN terms (business vocabulary, not technical/code terms —
-      those are added later by onboard-code). Append/update a "## Shared Language" table in `CONTEXT.md` at the project root:
+      those are added later by onboard-code).
+
+      Update `CONTEXT.md` at the project root IDEMPOTENTLY — never overwrite the whole file, and never blind-append
+      (re-running onboarding would bloat it). Manage the file BY SECTION:
+      - Ensure a single top `# Project Context: {project-name}` heading (create once if missing).
+      - You OWN the `## Shared Language` section: if it already exists, REPLACE its body in place; otherwise append it.
+        Leave every other section (e.g. `## Technical Terms`, `## Cross-Domain Verification`) untouched.
+      - Keep ONE row per Term (dedupe by term name) — update an existing term's row instead of adding a duplicate.
+
+      ## Shared Language
 
       | Term | Definition | Example |
       |------|-----------|---------|