@mytechtoday/augment-extensions 1.2.0 → 1.2.1

package/AGENTS.md

@@ -157,7 +157,7 @@ Use 'bd' for task tracking
 1. **Create Task**: Append to `.beads/issues.jsonl` with unique hash-based ID
 2. **Add Dependencies**: Use `blocks` and `blocked_by` fields
 3. **Find Ready Tasks**: Tasks with no open blockers
-4. **Work on Task**: Update status to `in-progress`, add comments
+4. **Work on Task**: Update status to `in_progress`, add comments
 5. **Close Task**: Update status to `closed`
 
 ### Beads Files
@@ -246,7 +246,7 @@ const specsForFile = Object.entries(coord.specs)
 
 1. **File issues for remaining work** - Create issues for anything that needs follow-up
 2. **Run quality gates** (if code changed) - Tests, linters, builds
-3. **Update issue status** - Close finished work, update in-progress items
+3. **Update issue status** - Close finished work, update in_progress items
 4. **PUSH TO REMOTE** - This is MANDATORY:
    ```bash
    git pull --rebase

package/augment-extensions/workflows/beads/examples/complete-workflow-example.md

@@ -95,14 +95,14 @@ Only `bd-a3f8.1` is ready because it has no blockers.
 
 ```bash
 # With CLI
-bd update bd-a3f8.1 --status in-progress
+bd update bd-a3f8.1 --status in_progress
 bd comment bd-a3f8.1 "Creating users table with email, password_hash, created_at columns"
 ```
 
 **Without CLI** - Append to `.beads/issues.jsonl`:
 
 ```jsonl
-{"id":"bd-a3f8.1","status":"in-progress","updated":"2024-01-20T11:00:00Z"}
+{"id":"bd-a3f8.1","status":"in_progress","updated":"2024-01-20T11:00:00Z"}
 {"id":"bd-a3f8.1","comments":[{"text":"Creating users table with email, password_hash, created_at columns","timestamp":"2024-01-20T11:00:00Z"}],"updated":"2024-01-20T11:00:00Z"}
 ```
 
@@ -145,7 +145,7 @@ bd comment bd-a3f8.2 "Using bcrypt with cost factor 12"
 bd close bd-a3f8.2
 
 # Work on JWT generation
-bd update bd-a3f8.3 --status in-progress
+bd update bd-a3f8.3 --status in_progress
 bd comment bd-a3f8.3 "Using HS256 algorithm, 24-hour expiry"
 
 # Complete it
@@ -155,10 +155,10 @@ bd close bd-a3f8.3
 **Without CLI** - Append to `.beads/issues.jsonl`:
 
 ```jsonl
-{"id":"bd-a3f8.2","status":"in-progress","updated":"2024-01-20T12:30:00Z"}
+{"id":"bd-a3f8.2","status":"in_progress","updated":"2024-01-20T12:30:00Z"}
 {"id":"bd-a3f8.2","comments":[{"text":"Using bcrypt with cost factor 12","timestamp":"2024-01-20T12:30:00Z"}],"updated":"2024-01-20T12:30:00Z"}
 {"id":"bd-a3f8.2","status":"closed","closed":"2024-01-20T13:00:00Z","updated":"2024-01-20T13:00:00Z"}
-{"id":"bd-a3f8.3","status":"in-progress","updated":"2024-01-20T13:30:00Z"}
+{"id":"bd-a3f8.3","status":"in_progress","updated":"2024-01-20T13:30:00Z"}
 {"id":"bd-a3f8.3","comments":[{"text":"Using HS256 algorithm, 24-hour expiry","timestamp":"2024-01-20T13:30:00Z"}],"updated":"2024-01-20T13:30:00Z"}
 {"id":"bd-a3f8.3","status":"closed","closed":"2024-01-20T14:00:00Z","updated":"2024-01-20T14:00:00Z"}
 ```
@@ -179,7 +179,7 @@ Now `bd-a3f8.4` is ready because both blockers are closed.
 
 ```bash
 # With CLI
-bd update bd-a3f8.4 --status in-progress
+bd update bd-a3f8.4 --status in_progress
 bd comment bd-a3f8.4 "POST /api/auth/login endpoint created, returns JWT on success"
 bd close bd-a3f8.4
 ```
@@ -187,7 +187,7 @@ bd close bd-a3f8.4
 **Without CLI** - Append to `.beads/issues.jsonl`:
 
 ```jsonl
-{"id":"bd-a3f8.4","status":"in-progress","updated":"2024-01-20T14:30:00Z"}
+{"id":"bd-a3f8.4","status":"in_progress","updated":"2024-01-20T14:30:00Z"}
 {"id":"bd-a3f8.4","comments":[{"text":"POST /api/auth/login endpoint created, returns JWT on success","timestamp":"2024-01-20T14:30:00Z"}],"updated":"2024-01-20T14:30:00Z"}
 {"id":"bd-a3f8.4","status":"closed","closed":"2024-01-20T15:00:00Z","updated":"2024-01-20T15:00:00Z"}
 ```
@@ -266,7 +266,7 @@ What Beads tasks are ready to work on?
 ### Documenting Progress
 
 ```
-Update Beads task bd-a3f8.2 to in-progress.
+Update Beads task bd-a3f8.2 to in_progress.
 Add comment: "Using bcrypt with cost factor 12"
 ```
 

package/augment-extensions/workflows/beads/rules/best-practices.md

@@ -116,7 +116,7 @@ Deeper hierarchies become hard to manage.
 Keep status current:
 
 ```
-open → in-progress → closed
+open → in_progress → closed
 ```
 
 ### Use Blocked Status
@@ -223,7 +223,7 @@ Track who is working on what:
   "id": "bd-a1b2",
   "title": "Add authentication",
   "assignee": "agent-1",
-  "status": "in-progress"
+  "status": "in_progress"
 }
 ```
 

package/augment-extensions/workflows/beads/rules/file-format.md

@@ -64,7 +64,7 @@ Beads stores issues in `.beads/issues.jsonl` using JSONL (JSON Lines) format. Ea
 
 - **id** (string): Unique hash-based ID, format: `bd-<hash>` or `bd-<hash>.<number>` for hierarchical
 - **title** (string): Short description of the task
-- **status** (string): One of: `"open"`, `"in-progress"`, `"blocked"`, `"closed"`
+- **status** (string): One of: `"open"`, `"in_progress"`, `"blocked"`, `"closed"`
 - **created** (string): ISO 8601 timestamp
 - **updated** (string): ISO 8601 timestamp
 
@@ -109,7 +109,7 @@ bd-a3f8.2      # Another task under epic
 ## Status Values
 
 - **open** - Task is ready to work on (no blockers)
-- **in-progress** - Currently being worked on
+- **in_progress** - Currently being worked on
 - **blocked** - Waiting on dependencies
 - **closed** - Completed or cancelled
 
@@ -227,7 +227,7 @@ Tasks that are related but not blocking:
 
 ```jsonl
 {"id":"bd-a1b2","title":"Task 1","status":"open","created":"2024-01-20T10:00:00Z","updated":"2024-01-20T10:00:00Z"}
-{"id":"bd-a1b2","status":"in-progress","updated":"2024-01-20T11:00:00Z"}
+{"id":"bd-a1b2","status":"in_progress","updated":"2024-01-20T11:00:00Z"}
 {"id":"bd-a1b2","status":"closed","closed":"2024-01-20T12:00:00Z","updated":"2024-01-20T12:00:00Z"}
 ```
 
@@ -310,7 +310,7 @@ echo '{"id":"bd-a1b2","title":"New task","status":"open","created":"2024-01-20T1
 ### Start Work
 
 ```jsonl
-{"id":"bd-a1b2","status":"in-progress","updated":"2024-01-20T11:00:00Z"}
+{"id":"bd-a1b2","status":"in_progress","updated":"2024-01-20T11:00:00Z"}
 ```
 
 ### Add Comment

package/augment-extensions/workflows/beads/rules/manual-setup.md

@@ -63,7 +63,7 @@ Append a JSON line:
 Append a JSON line with the same ID and updated fields:
 
 ```json
-{"id":"bd-<hash>","status":"in-progress","updated":"<ISO-8601>"}
+{"id":"bd-<hash>","status":"in_progress","updated":"<ISO-8601>"}
 ```
 
 ### Closing Tasks
@@ -77,7 +77,7 @@ Append a JSON line with status "closed":
 ## Task States
 
 - **open** - Ready to work on
-- **in-progress** - Currently being worked on
+- **in_progress** - Currently being worked on
 - **blocked** - Waiting on dependencies
 - **closed** - Completed
 
@@ -100,7 +100,7 @@ Tasks are ready when:
 1. Create task by appending to `.beads/issues.jsonl`
 2. Add dependencies with `blocks`/`blocked_by` fields
 3. Find ready tasks (no open blockers)
-4. Update status to "in-progress"
+4. Update status to "in_progress"
 5. Add comments as needed
 6. Close task when complete
 ```
@@ -206,7 +206,7 @@ Parse .beads/issues.jsonl and find tasks where:
 Ask your AI:
 
 ```
-Update Beads task bd-a1b2 to status "in-progress"
+Update Beads task bd-a1b2 to status "in_progress"
 Append an update to .beads/issues.jsonl
 ```
 

package/augment-extensions/workflows/beads/rules/workflow.md

@@ -220,7 +220,7 @@ The AI will:
 bd comment bd-a1b2 "Started implementation, added login endpoint"
 
 # Update status
-bd update bd-a1b2 --status in-progress
+bd update bd-a1b2 --status in_progress
 
 # Add labels
 bd update bd-a1b2 --labels backend,auth
@@ -231,7 +231,7 @@ bd update bd-a1b2 --labels backend,auth
 Append update to `.beads/issues.jsonl`:
 
 ```json
-{"id":"bd-a1b2","title":"Implement user authentication","status":"in-progress","priority":0,"comments":[{"text":"Started implementation","timestamp":"2024-01-20T11:00:00Z"}],"updated":"2024-01-20T11:00:00Z"}
+{"id":"bd-a1b2","title":"Implement user authentication","status":"in_progress","priority":0,"comments":[{"text":"Started implementation","timestamp":"2024-01-20T11:00:00Z"}],"updated":"2024-01-20T11:00:00Z"}
 ```
 
 ## Step 6: Close Task

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mytechtoday/augment-extensions",
-  "version": "1.2.0",
+  "version": "1.2.1",
   "description": "CLI tool for managing Augment Code AI extension modules",
   "main": "cli/dist/index.js",
   "bin": {