toga-ai 1.0.38 → 1.0.40

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "toga-ai",
-  "version": "1.0.38",
+  "version": "1.0.40",
   "description": "TOGA Technology Team Claude Knowledge System — shared AI coding harness with skills, knowledge base CLI, and project installer for Claude Code.",
   "keywords": [
     "claude",

package/skills/capture/SKILL.md

@@ -71,6 +71,32 @@ persist the `.claude/` bundle path, or the next session will silently skip pushi
 
 Call the helper as `node "<TEAM_REPO>/knowledge.js" …`.
 
+## Step 1b — Resolve the author username (`owners` — NEVER leave empty)
+
+Every doc's `owners:` field must name the person authoring this session's changes.
+**Never write `owners: []` or an empty owner.** Resolve the username once and reuse it for
+every doc in this capture — call the result `AUTHOR_USERNAME`:
+
+1. **Claude memory** — look for a `user` memory named `author-username`. If present, use it
+   and do not ask again.
+2. **If absent, ASK the developer:** "What's your username for knowledge ownership?
+   (convention: first initial + last name, all lowercase — e.g. John Smith → `jsmith`)."
+   - Do **not** guess from the OS login or git config — ask and confirm.
+   - Normalize the answer to lowercase with no spaces.
+3. **Persist it** to Claude memory as a `user` memory named `author-username` (and add its
+   `MEMORY.md` pointer) so future captures never ask again.
+
+`owners` is a **list of everyone who has worked on the doc — it may hold several names**,
+not just one. Always include `AUTHOR_USERNAME`, and treat the field as cumulative:
+
+- **New doc:** start `owners` with `["<AUTHOR_USERNAME>"]`.
+- **Existing doc:** **union** — keep all existing owners and add `AUTHOR_USERNAME` if not
+  already present. Never replace or drop an existing owner.
+- **Co-authors:** if more than one person worked on this feature (e.g. pairing, or a handoff
+  this session), ask "Anyone else who should be listed as an owner? (usernames, comma-separated,
+  same first-initial+last-name convention)" and add each — deduplicated, lowercase — to the list.
+- Never leave `owners` empty.
+
 ## Step 2 — Determine framework / repo / project (ask if unknown)
 
 1. From the **live session context**, identify what was built, changed, debugged, or decided,
@@ -118,6 +144,8 @@ Write all docs to `<TEAM_REPO>/knowledge/...` — the git clone, not the project
 
 For every doc, set/refresh frontmatter: `framework`, `repo`, `project`, `client`,
 `type`, `status`, `updated` (today's date), `owners`, `files`, `related`.
+Set `owners` to `["<AUTHOR_USERNAME>"]` from Step 1b — **never leave it empty**; when a doc
+already has owners, add `AUTHOR_USERNAME` if missing rather than replacing.
 Add `related:` cross-links. Append new repos to `<TEAM_REPO>/knowledge/registry.json`.
 
 ## Step 6 — Validate, index, mirror back (mandatory)
@@ -224,7 +252,7 @@ client: <shared|client-slug>
 type: <feature|client-feature>
 status: active
 updated: <YYYY-MM-DD>
-owners: [<who>]
+owners: ["<AUTHOR_USERNAME>"]   # from Step 1b — never empty
 files:
   - <on-disk/path/one>
 related: []             # client-feature: link the shared apps/<repo>/features/<base>.md
@@ -262,7 +290,7 @@ client: <client-slug>
 type: workflow
 status: active
 updated: <YYYY-MM-DD>
-owners: [<who>]
+owners: ["<AUTHOR_USERNAME>"]   # from Step 1b — never empty
 files: []
 related: []
 ---
@@ -291,7 +319,7 @@ client: shared
 type: architecture
 status: active
 updated: <YYYY-MM-DD>
-owners: [<who>]
+owners: ["<AUTHOR_USERNAME>"]   # from Step 1b — never empty
 files: [<key paths>]
 related: []
 ---
@@ -310,7 +338,7 @@ client: shared
 type: standard
 status: active
 updated: <YYYY-MM-DD>
-owners: [<who>]
+owners: ["<AUTHOR_USERNAME>"]   # from Step 1b — never empty
 files: []
 related: []
 ---