teamshare-bridge 0.5.2 → 0.7.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "teamshare-bridge",
-  "version": "0.5.2",
+  "version": "0.7.0",
   "description": "Local bridge for TeamShare agents - CLI session runner, auto-wake WebSocket daemon, and teamshare:// protocol handler.",
   "type": "commonjs",
   "license": "MIT",
@@ -43,5 +43,8 @@
   "devDependencies": {
     "@types/node": "^22.0.0",
     "typescript": "^5.6.0"
+  },
+  "optionalDependencies": {
+    "node-pty": "^1.1.0"
   }
 }

package/skills/teamshare-cdd/SKILL.md

@@ -44,37 +44,49 @@ Rules that are not optional:
 ## The workflow — three gates
 
 ### START (before touching any code)
-1. `list_document_folders` + `list_documents` for the project.
-2. Read `docs/contracts`, `docs/adr`, `docs/guides` that exist — they govern
+1. **Read the cloud project context** via `get_project_context` — the
+   structured AGENTS.md every agent maintains (overview, architecture,
+   structure, workflows, conventions, gotchas). This is your map of the
+   codebase; it tells you where things live BEFORE you explore.
+2. `list_document_folders` + `list_documents` for the project.
+3. Read `docs/contracts`, `docs/adr`, `docs/guides` that exist — they govern
    your implementation (same way `docs/api-contract.md` and
    `docs/ui-style-guide.md` govern TeamShare's repos).
-3. Read your own task folder if this is a `--continue`/resumed session.
-4. **Write `plan.md` FIRST** via `create_document`: goal, decisions, files to
+4. Read your own task folder if this is a `--continue`/resumed session.
+5. **Write `plan.md` FIRST** via `create_document`: goal, decisions, files to
    touch, step list. No code until the plan note exists.
-5. **Move the task to `in_progress`** via `update_task` — you are now working it.
+6. **Move the task to `in_progress`** via `update_task` — you are now working it.
 
 ### DO (while working)
-6. Check off subtasks (`update_subtask done: true`) and update
+7. Check off subtasks (`update_subtask done: true`) and update
    `progress.md`/`plan.md` via `update_document_note` as you go — the human
    watches the app.
-7. **Checklist items — ALWAYS list first.** Before creating checklist items,
+8. **Checklist items — ALWAYS list first.** Before creating checklist items,
    call `list_checklist_items` (pass `taskId` or `subtaskId`) to see what
    already exists. Use `update_checklist_item` with the existing ID to toggle
    done/rename — do NOT create duplicates. Only call `create_checklist_item`
    for genuinely new items. The `get_task` response also includes
    `checklistItems` for task-level items, and `list_subtasks` includes them
    per subtask.
-8. When you make an architecture decision worth keeping, add it to `docs/adr`
+9. When you make an architecture decision worth keeping, add it to `docs/adr`
    as `ADR-<n>-<title>.md` (short: context → decision → consequences).
-9. Blocked? Use `ask_human` and include a pointer to the relevant note.
+10. Blocked? Use `ask_human` and include a pointer to the relevant note.
 
 ### DONE (before closing)
-10. **Move the task to `in_review`** via `update_task` — signals the human
+11. **Move the task to `in_review`** via `update_task` — signals the human
     to review your work.
-11. Write `summary.md`: what you built, why, how it maps to the plan, links to
+12. Write `summary.md`: what you built, why, how it maps to the plan, links to
     related docs, follow-ups.
-12. Post the closing comment referencing the summary doc.
-13. Never leave a task without `plan.md` + `summary.md` notes.
+13. Post the closing comment referencing the summary doc.
+14. Never leave a task without `plan.md` + `summary.md` notes.
+15. **Update the project context when reality changed** (mandatory). If your
+    work added/moved/deleted folders or files that matter, changed commands or
+    workflows, or established new conventions — call `update_project_context`
+    with the affected sections (`structure`, `workflows`, `conventions`,
+    `architecture`, `gotchas`) and the `baseVersion` from your last read.
+    A stale version means another writer got there first: re-read via
+    `get_project_context`, merge, retry. The next agent depends on this being
+    accurate — do not leave the map stale.
 
 ## Task status progression (guidance)
 
@@ -133,6 +145,8 @@ run, the following rules apply ON TOP of everything above:
 
 ## Tools to use
 
+- `get_project_context <projectId>` — the cloud AGENTS.md (all sections + version).
+- `update_project_context` — partial section update (pass `baseVersion`; 409 = re-read + merge).
 - `list_document_folders <projectId>` — the tree, with per-folder counts.
 - `list_documents <projectId>` — files (optionally filter by folder).
 - `read_document <documentId>` — content (notes return their markdown body).