fix: remove misleading documentation per review feedback

Per @bcho review feedback on PR #11:
- Remove examples/demo-tracking-lifecycle.sh (feature not working)
- Remove 'Tracking Comment Lifecycle' README section (~120 lines)

Review identified that tracking comment updates are not functioning
in production despite code existing. As @bcho noted: 'obviously the
comment in the linked issue is not being updated'.

Issue #10's tracking comment was not updated to completed status,
proving the feature doesn't work as documented.

Removing documentation and demo until feature is verified working.

Addresses:
- Review comment: 'remove this file' (demo-tracking-lifecycle.sh)
- Review comment: 'remove this section' (Tracking Comment Lifecycle)
- General review: tracking comments not being updated

Ref: PR #11 review by @bcho
Co-authored-by: Shelley <shelley@exe.dev>

Author: smol-squad

modules/gh-pm/README.md

@@ -675,126 +675,6 @@ bash test/test_config.sh
 
 Tests use a minimal test framework and mock GitHub API calls. No external dependencies required.
 
-## Tracking Comment Lifecycle
-
-gh-pm uses GitHub comments to track task state throughout execution. Each task gets a **tracking comment** with a unique HTML marker (`<!-- gh-pm:TASK_ID -->`) that persists across updates.
-
-### Comment States
-
-| State | Icon | When | Description |
-|-------|------|------|-------------|
-| **Analyzing** | 🔍 | Task discovered | gh-pm is analyzing the task with LLM before dispatch |
-| **Dispatched** | ⏳ | Workflow started | Task has been sent to workflow handler |
-| **In Progress** | ⏳ | Status update | Workflow is running (optional progress messages) |
-| **Completed** | ✅ | `result.json` created | Workflow finished successfully |
-| **Failed** | ❌ | Process died or error | Workflow failed or crashed |
-| **Timed Out** | ⏱️ | Timeout exceeded | Workflow exceeded timeout, will retry |
-
-### Example Flow
-
-**1. Task Discovery** — gh-pm finds Issue #42:
-
-```markdown
-<!-- gh-pm:owner-repo-issue-42 -->
-## 🤖 gh-pm: Analyzing Task
-
-| Field | Value |
-|-------|-------|
-| Task ID | `owner-repo-issue-42` |
-| Status | 🔍 Analyzing |
-| Profile | `default` |
-| Started | 2026-03-31 10:00:00 UTC |
-
-_Analyzing with LLM before dispatching workflow…_
-```
-
-**2. Workflow Dispatch** — Handler is invoked:
-
-```markdown
-<!-- gh-pm:owner-repo-issue-42 -->
-## 🤖 gh-pm: Task Dispatched
-
-| Field | Value |
-|-------|-------|
-| Task ID | `owner-repo-issue-42` |
-| Status | ⏳ Running |
-| Started | 2026-03-31 10:00:05 UTC |
-
-_Managed by gh-pm. Updates will follow._
-```
-
-**3. Progress Update** (optional, via `status.json`):
-
-```markdown
-<!-- gh-pm:owner-repo-issue-42 -->
-## 🤖 gh-pm: Task In Progress
-
-| Field | Value |
-|-------|-------|
-| Task ID | `owner-repo-issue-42` |
-| Status | ⏳ Running |
-| Updated | 2026-03-31 10:02:00 UTC |
-
-### Progress
-
-Running tests...
-
-_Managed by gh-pm._
-```
-
-**4. Task Completion** — `result.json` is written:
-
-```markdown
-<!-- gh-pm:owner-repo-issue-42 -->
-## 🤖 gh-pm: Task Completed
-
-| Field | Value |
-|-------|-------|
-| Task ID | `owner-repo-issue-42` |
-| Status | ✅ Completed |
-| Finished | 2026-03-31 10:05:00 UTC |
-
-### Summary
-
-Successfully implemented the requested feature:
-- Created new function `foo()`
-- Added unit tests
-- Updated documentation
-- Opened PR #123 for review
-
-_Managed by gh-pm._
-```
-
-### Tracking Comment Updates
-
-Tracking comments are **updated in place** rather than creating new comments:
-
-- **On dispatch**: Existing "Analyzing" comment is updated to "Dispatched"
-- **On progress**: Comment is updated with latest status message
-- **On completion**: Comment is updated with final state and summary
-- **On failure**: Comment is updated with error details
-- **On timeout**: Comment is updated with retry information
-
-This keeps the issue/PR thread clean with a single status comment per task.
-
-### Recovery After Restart
-
-If gh-pm restarts while tasks are in-flight:
-
-1. **Completed tasks with unreported results** → Reports completion to GitHub
-2. **Running tasks with dead PIDs** → Treats as timeout, retries or fails
-3. **Tasks never dispatched** → Dispatches them
-
-This ensures tracking comments always reflect the true state, even after crashes or restarts.
-
-### Implementation Details
-
-Tracking comment management is implemented in:
-- **`lib/report.sh`** — Functions for posting and updating comments
-- **`lib/github.sh`** — `gh_find_tracking_comment()` finds comments by marker
-- **`bin/gh-pm`** — `monitor_inflight()` checks task status and updates comments
-- **`lib/recovery.sh`** — Startup recovery reports unreported completions
-
 ## Architecture Details
 
 For implementation details, design decisions, and protocol specifications, see [design.md](./design.md).