docs: link completion criteria to Gitea issues and add issue tracking guidance

- Created 52 Gitea issues across milestones 1-7, one per completion criterion
- Each criterion now links to its corresponding issue ([#N](url) format)
- Milestone Tracking sections updated with Issue Updates subsection:
  when/how to comment, close issues via CLI or web UI
- Phases 4-7 criteria converted from plain bullets to checkbox format

docs/plans/phases/phase-1-decomposition.md

@@ -37,6 +37,23 @@ echo $CGO_ENABLED   # should print 1 (or be unset; we set it explicitly below)
 
 This phase corresponds to **Milestone 1** in [Gitea](https://gitea.dohertylan.com/dohertj2/natsnet/milestone/1). When starting this phase, verify the milestone is open. Assign relevant issues to this milestone as work progresses.
 
+### Issue Updates
+
+Each completion criterion has a corresponding Gitea issue. Update issues as you work:
+
+- **Starting a criterion**: Add a comment noting work has begun
+- **Blocked**: Add a comment describing the blocker
+- **Complete**: Close the issue with a comment summarizing the result (e.g., counts, verification output)
+
+Close issues via CLI:
+```bash
+curl -s -X PATCH "https://gitea.dohertylan.com/api/v1/repos/dohertj2/natsnet/issues/{N}" \
+  -H "Content-Type: application/json" \
+  -H "Authorization: token $GITEA_TOKEN" \
+  -d '{"state":"closed"}'
+```
+Or close via the Gitea web UI.
+
 ## Steps
 
 ### Step 1: Initialize the porting database
@@ -201,16 +218,16 @@ dotnet run --project tools/NatsNet.PortTracker -- report export --format md --ou
 
 Phase 1 is complete when ALL of the following are true:
 
-- [ ] `porting.db` exists and contains data in all five tables (modules, features,
+- [ ] [#1](https://gitea.dohertylan.com/dohertj2/natsnet/issues/1) `porting.db` exists and contains data in all five tables (modules, features,
       unit_tests, dependencies, library_mappings).
-- [ ] All Go source files under `golang/nats-server/server/` are accounted for
+- [ ] [#2](https://gitea.dohertylan.com/dohertj2/natsnet/issues/2) All Go source files under `golang/nats-server/server/` are accounted for
       (no files silently skipped without a logged warning).
-- [ ] All public and private functions/methods are extracted as features.
-- [ ] All `Test*` and `Benchmark*` functions are extracted as unit_tests.
-- [ ] Test-to-feature links are populated where naming conventions allow inference.
-- [ ] Module-level dependencies are recorded in the dependencies table.
-- [ ] External import paths are recorded in the library_mappings table.
-- [ ] `phase check 1` shows all checklist items marked `[x]`:
+- [ ] [#3](https://gitea.dohertylan.com/dohertj2/natsnet/issues/3) All public and private functions/methods are extracted as features.
+- [ ] [#4](https://gitea.dohertylan.com/dohertj2/natsnet/issues/4) All `Test*` and `Benchmark*` functions are extracted as unit_tests.
+- [ ] [#5](https://gitea.dohertylan.com/dohertj2/natsnet/issues/5) Test-to-feature links are populated where naming conventions allow inference.
+- [ ] [#6](https://gitea.dohertylan.com/dohertj2/natsnet/issues/6) Module-level dependencies are recorded in the dependencies table.
+- [ ] [#7](https://gitea.dohertylan.com/dohertj2/natsnet/issues/7) External import paths are recorded in the library_mappings table.
+- [ ] [#8](https://gitea.dohertylan.com/dohertj2/natsnet/issues/8) `phase check 1` shows all checklist items marked `[x]`:
 
 ```bash
 dotnet run --project tools/NatsNet.PortTracker -- phase check 1 --db porting.db