polish(pull,docs): use ⬆️/⬇️ for drift direction; disambiguate from 📝 (file written)

The drift-direction-classifier feature overloaded 📝 in pull output: it
meant both 'engine wrote a file to disk' (pre-existing) AND 'local ahead
of dashboard, preserved' (new). In mixed-direction pulls these appear on
adjacent lines and the disambiguation-by-suffix is mild but real.

Pull-output icon legend (new mental model):
  ⬆️  = local-ahead, needs to flow UP to dashboard (preserved)
  ⬇️  = --resolve=theirs, flowed DOWN (overwrote local with platform)
  📝 = engine wrote/updated a file on disk (routine I/O)
  ✏️  = locally modified per git, preserved
  🔒 = platform-default (read-only)
  🚫 = matched .vapi-ignore
  🗑️ = locally deleted (intent recorded in state)

Swapped sites (5 in src/pull.ts):
- :882  classifier local-ahead log
- :1088 resolveBothDiverged --resolve=ours log (already ⬆️ via earlier commit)
- :1134 printDriftSummary local-ahead row
- :1356 end-of-pull legend
- new   end-of-pull legend now also documents ⬇️ and 📝 separately

The 'wrote file to disk' 📝 (lines 987, 998) is unchanged — that's the
pre-existing semantic and the one this feature should NOT have collided with.

AGENTS.md gains:
- The full icon legend table (mental model: ⬆️ flows up, ⬇️ flows down,
  📝 is routine I/O).
- A first-adoption-noise callout (L1 from code review): the first audit
  after this feature lands surfaces no-baseline info findings for every
  resource that predates lastPulledHash tracking. Info severity does NOT
  block CI; --bootstrap clears them all in one shot, or they naturally
  drain over the next few sync cycles.

Closes L1 (first-adoption noise documentation) and NIT (icon overload)
from the code review on this PR. No behavior change \u2014 cosmetic + docs only.

Tests: 266/266 green, tsc --noEmit clean.

Author: dhruva-vapi

AGENTS.md

@@ -101,6 +101,25 @@ Runs the engine's local validators against every YAML/MD file in the org without
 
 `--force` skips all of this and just overwrites local with dashboard. Use it ONLY when you literally need to nuke local and re-materialize dashboard truth (rare). Plain pull is the DEFAULT for both humans and agents; `--force` is the escape hatch.
 
+**Pull-output icon legend.** Distinct semantics in a single pulled-resource line:
+
+| Icon | Meaning |
+|------|---------|
+| `📝` | Engine wrote/updated a file on disk (clean / no-baseline path) |
+| `✨` | Engine created a NEW file on disk (first-time pull of this resource) |
+| `✏️`  | Locally modified file detected by git, preserved as-is |
+| `⬆️`  | `local-ahead` — local has unpushed edits, needs to flow UP to dashboard (preserved) |
+| `⬇️`  | `--resolve=theirs` — overwrote local with dashboard (flowed DOWN) |
+| `🔒` | Platform-default resource (read-only, immutable) |
+| `🚫` | Matched `.vapi-ignore` (not tracked locally) |
+| `🗑️`  | Locally deleted (deletion intent recorded in state) |
+
+Mental model: `⬆️` flows UP (push), `⬇️` flows DOWN (pull-overwrite), `📝` is the engine doing routine file I/O.
+
+**First-adoption noise on customer repos.** The first `npm run audit -- <org>` after upgrading to a version with the content-drift rule will surface `[content-drift] [no-baseline]` info findings for every resource whose state row predates `lastPulledHash` tracking. These are info-severity (do NOT block CI), but the noise is real. Two ways to clear:
+- `npm run pull -- <org> --bootstrap` — refreshes state with the current platform-hash baseline, no resource materialization. One-shot fix for the whole fleet.
+- Or just let them sit — each plain `npm run pull` after this writes `lastPulledHash` for whichever resources it touches, so the no-baseline rows naturally drain over the next few sync cycles.
+
 ### `npm run push -- <org>` — raw push, no pre-pull
 
 Skips the merge pass. Only use when (a) you literally just ran `pull` and (b) you're certain no one has touched the dashboard since. In a multi-developer environment or when dashboard editors are in play, default to `apply` instead. Stale local state can clobber recent dashboard edits or PATCH against UUIDs that no longer exist.

src/pull.ts

@@ -875,8 +875,11 @@ export async function pullResourceType(
           }
 
           if (direction === "local-ahead") {
+            // ⬆️ — local has unpushed edits, needs to flow UP to dashboard.
+            // Distinct from 📝 (= engine wrote a file to disk) to avoid icon
+            // overload in mixed-direction pulls.
             console.log(
-              `   📝 ${resourceId} (local ahead of dashboard) ${formatDriftLabel(direction)}`,
+              `   ⬆️  ${resourceId} (local ahead of dashboard) ${formatDriftLabel(direction)}`,
             );
             upsertState(newStateSection, resourceId, { uuid: resource.id });
             skipped++;
@@ -1128,7 +1131,7 @@ function printDriftSummary(counts: DriftDirectionCounts): void {
   }
   if (counts["local-ahead"] > 0) {
     lines.push(
-      `   📝 local-ahead      : ${counts["local-ahead"]}  (run npm run push to propagate local edits up)`,
+      `   ⬆️  local-ahead      : ${counts["local-ahead"]}  (run npm run push to propagate local edits up)`,
     );
   }
   if (counts["both-diverged"] > 0) {
@@ -1350,7 +1353,9 @@ export async function runPull(options: PullOptions = {}): Promise<PullResult> {
     );
     console.log("       🚫 = matched .vapi-ignore (not tracked)");
     console.log("       ✏️  = locally modified (preserved)");
-    console.log("       📝 = local ahead of dashboard (preserved)");
+    console.log("       ⬆️  = local ahead of dashboard (preserved)");
+    console.log("       ⬇️  = both diverged, --resolve=theirs (overwrote local)");
+    console.log("       📝 = engine wrote/updated file on disk");
     console.log("       🗑️  = locally deleted (intent in state)");
     console.log(
       `   Run with --force to overwrite: npm run pull -- ${VAPI_ENV} --force`,