fix: repair cross-skill contract gaps and harden Tracker handling (v1.1.1)

- deploy: create "! Rule Needed" label on first deploy (was promised in
  frontmatter but never implemented; rule-review depends on it)
- rule-review: accept Bootstrap-mode entry (Phase: Bootstrap, no Tracker yet)
- survey: create the three artifacts before invoking handoff so handoff's
  sanity check no longer loops
- deploy: name manage_gmail_filter params explicitly (action/criteria/filter_action)
- rule-review: quote label query (label:"! Rule Needed")
- deploy: renumber execution-flow block to the 7 phases the body runs
- survey: frame Tracker About tab as a technical reference
- import + rule-review: de-duplicate rule_id before writing to Tracker
- survey/import/deploy/rule-review: document XLSX Tracker Drive round-trip
- all skills: use session date only in _status.md (no fabricated clock time)

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

skills/import/SKILL.md

@@ -286,6 +286,12 @@ For each note:
 
 Write all approved (and parked) rules to the Tracker after the queue is complete.
 
+**Guarantee unique rule_ids before writing.** Read the existing `rule_id` values from the
+Rules sheet first. For every rule about to be written, if its ID already exists (a
+subcontractor may reuse IDs across batches, or collide with a prior import), append a
+numeric suffix (`-2`, `-3`, …) until unique. Never overwrite an existing row or write a
+duplicate ID.
+
 ### Tracker Column Schema
 
 ```
@@ -325,7 +331,12 @@ Always:
 
 ### Writing to XLSX Tracker
 
-Invoke the xlsx skill to append rows to the Rules sheet. Same field rules apply.
+The file lives in Drive, so this is a round-trip, not an in-place edit. Download the
+current file with `get_drive_file_content`, invoke the xlsx skill to append the rows to
+the Rules sheet (same field rules apply), then upload it back to the same Drive location,
+replacing the existing file (`update_drive_file` if available; otherwise re-create it in
+the same folder and confirm the old copy is replaced — never leave two Trackers). Verify
+the row count grew by exactly the number of rules written.
 
 ### After writing:
 
@@ -344,7 +355,7 @@ Invoke the xlsx skill to append rows to the Rules sheet. Same field rules apply.
 Update `_status.md`:
 
 ```
-Last Updated: [timestamp]
+Last Updated: [YYYY-MM-DD — today's date from the session; do not fabricate a clock time]
 Last Agent: Claude (CoWork) — import skill
 Phase: Rule Build [or Deploy-ready if all batches are in]
 Last Completed Step: [N] rules from [batch name] reviewed and loaded.