Automations-Project · ARHAEEM · Jul 30, 2026 · Jun 15, 2026 · Jun 15, 2026 · Jun 16, 2026
diff --git a/.gitignore b/.gitignore
@@ -49,4 +49,6 @@
 **/PLAN.md
 packages/mcp-server/.chrome-profile/
 packages/mcp-server/dev-tools/
-packages/extension/README.md
+packages/extension/README.md
+packages/webview/.ds-css/
+packages/webview/.ds-src/
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -6,6 +6,62 @@ Check [Keep a Changelog](http://keepachangelog.com/) for recommendations on how
 
 ## [Unreleased]
 
+### Formula round-trip + daemon upload fixes (2026-07-09)
+
+#### Fixed
+- **MCP server — formula downloads emit real field names.** `download_base_formulas` / `download_formula_field` used to write Airtable's internal `{column_value_fldXXX}` refs verbatim — unreadable, and rejected by Airtable on re-upload ("Unknown field names"). Refs are now resolved to `{Field Name}` (native syntax); unknown ids fall back to `{fldXXX}`, which the API accepts. Non-field placeholders (`{FOO_PLACEHOLDER}`) pass through untouched.
+- **MCP server — formula writes normalize legacy refs.** All formula write paths (`create_formula_field`, `update_formula_field`, `update_field_config`, `validate_formula`) convert `{column_value_fldXXX}` → `{fldXXX}` before sending, so previously-downloaded files round-trip without manual rewriting.
+- **Extension — "Upload formula" no longer fails with HTTP 406.** The right-click upload/download commands' daemon HTTP client now sends the MCP-spec-required `Accept: application/json, text/event-stream` header, and parses both JSON and SSE-framed responses (older daemons). The daemon side now answers stateless `/mcp` POSTs as plain JSON (`enableJsonResponse`).
+- **MCP server — `list_fields` lightweight by default**: returns `{ id, name, type }`; full `typeOptions` is opt-in via `includeOptions: true` (previously ~350K chars on a wide table). The installed AI-skill template and `server.json` tool listing were updated to match.
+- **Language services — field names with special characters no longer produce false errors.** With downloads now emitting real `{Field Name}` refs, names containing apostrophes (`{Owner's List}`), parentheses (`{Total (USD)}`), or smart quotes (`{Owner’s List}`, common via Airtable UI autocorrect) used to trigger spurious `Unclosed quote` / `Missing closing parenthesis` / `Smart quote` Errors in the `.formula` editor — and the smart-quote quick fix would rename the ref into a dangling reference. The paren/bracket/quote/smart-quote checkers now skip `{…}` field-ref bodies (real errors outside refs still report; an unclosed `{` still reports).
+
+### MCP server — sync_base schema-orphan deletion under mirror (2026-06-21)
+
+#### Added
+- `sync_base mode=apply` — **schema-orphan deletion** (`pruneSchema`): under `policy=mirror`, dest-only fields/views/tables that have no counterpart in the source are deleted from the destination after `applyPlan` completes. Two independent gates: `confirmDeletions:true` is required to delete dest-only **fields and views** (same flag as `pruneRecords`); the new `confirmTableDeletions:true` is required to drop dest-only **tables** — `confirmDeletions` alone never deletes an entire table. Without each gate the operation is a dry-count only (`DELETION_GATED` for fields/views, `TABLE_DELETION_GATED` for tables). Deletion is dependency-safe: fields are deleted without `force` (so no matched field is ever cascade-deleted), orphan→orphan formula dependencies are resolved by retry-until-stable, and a field blocked by a matched-field dependency is kept and reported as `SCHEMA_DELETE_BLOCKED`. Deletion order: views first (no dependents), then fields, then tables (after their content). Applied counts are surfaced in the result as `schemaDeleted` (fields + views) and `tablesDeleted`; failures are continue-on-failure warnings (`SCHEMA_DELETE_FAILED`). Per-table `policyOverrides` are respected — `overlay`/`preserve` tables are never pruned. Module: `src/sync/prune-schema.js`. Deferred: retypes, view-section orphan deletion, attachment-strip (M4).
+
+### MCP server — sync_base natural-key record matching (2026-06-21)
+
+#### Added
+- `sync_base` — **natural-key record matching** (`naturalKeys: { [tableName]: fieldName }`): matches dest↔source records by a shared key field's value (resolved by name per base) and grows `idmap.records` without any write to either base. Add-only + ambiguity-safe: existing mappings are never overwritten, already-mapped dest records are never re-claimed, and ambiguous/duplicate key values are skipped with a `NATURAL_KEY_AMBIGUOUS` warning; a missing key field emits `NATURAL_KEY_FIELD_MISSING`. Runs in two places: (1) **`mode=reconcile`** — after the existence-prune, snapshots source records and calls the matcher, then saves the updated idmap; (2) **`mode=apply` auto pre-pass** — runs before Pass 1 and before `pruneRecords`, so records `mirror` no longer treats real-but-unmapped dest records as orphans and re-syncs no longer duplicate them. The key field must be stable across bases (autoNumber renumbers → bad key; name/email/injected `InjectID` → good key). Single-field keys only; composite keys and value normalization are deferred. A `matched` count is returned in the result.
+
+### MCP server — sync_base reconciliation policy + custom field mappings (2026-06-20)
+
+#### Added
+- `sync_base mode=apply` — **records reconciliation policy**: new `policy` param (`mirror` | `overlay` | `preserve`, default `overlay`) controls two independent axes — **extras** (keep or remove dest-only records) and **conflicts** (source-wins or dest-wins when both bases hold the record). Presets: `mirror` = {remove, source-wins} (make dest identical to source), `overlay` = {keep, source-wins} (default — today's existing behavior), `preserve` = {keep, dest-wins} (never overwrite dest edits). `policyOverrides` (`{ [tableName]: preset }`) overrides the global preset per table.
+- `sync_base mode=apply` — **deletion gate** (`confirmDeletions`): under `mirror` policy (or any table override that removes extras), dest-only orphan records are not deleted unless `confirmDeletions: true`. Without it, `pruneRecords` reports a `DELETION_GATED` warning with the would-delete count and does nothing — poll `mode=status` to see counts, then re-run with `confirmDeletions:true` to apply. Separately, `createTable` unconditionally clears the ~3 blank scaffolding rows it seeds (best-effort; `SCAFFOLDING_ROWS_KEPT` warning if the deletion attempt fails); `pruneRecords` under `mirror`+`confirmDeletions` additionally removes any leftover dest-only blank rows as part of the ordinary orphan prune. Attachment-strip under mirror remains a deferred follow-up (schema-orphan deletion and natural-key matching shipped separately).
+- `sync_base` — **custom field mappings** (`fieldMappings: { [tableName]: { sourceFieldName: destFieldName } }`): inject a source field's value (including computed fields like `autoNumber` or formula) into a different writable scalar dest field during record sync. Classic use: inject a source `autoNumber` field (`Code`) into a writable dest text field (`InjectID`) so a dest primary-key formula can reconstruct original identity across bases. Fail-fast pre-flight validation aborts `mode=apply` synchronously on any error (`FIELD_MAP_INVALID`); `mode=plan` and `mode=diff` run the same validation as a dry check and return errors in `fieldMappingErrors` (machine output). Validation codes: `FIELD_MAP_TABLE_MISSING`, `FIELD_MAP_SOURCE_MISSING`, `FIELD_MAP_TARGET_MISSING`, `FIELD_MAP_TARGET_COMPUTED` (dest must be writable scalar), `FIELD_MAP_TYPE_INCOMPATIBLE` (array-typed source/dest rejected), `FIELD_MAP_COLLISION` (two sources targeting the same dest).
+
+### MCP server — sync_base compare, curatable changeset, selective apply (2026-06-19)
+
+#### Added
+- `sync_base mode=diff` (read-only): comprehensive schema comparison of two bases via a new pure `src/sync/compare.js`. Every difference is classified as **drift** (sync enforces it — table/field/view existence, field type/options/choices, view filters/sorts/groups content, column visibility, colors/cover/frozen/rowHeight, primary, form), **best-effort** (sync applies but doesn't guarantee — field/view/column order, sort/group clause order), or **not-synced** (view sections, now captured by the snapshot). Two verdicts: `identical` (zero diffs) and `converged` (zero drift; best-effort/not-synced may remain). The full diff is persisted to `~/.airtable-user-mcp/sync/<src>__<dest>/diff-<id>.json`; the tool returns a token-budgeted DIGEST (verdicts + class counts + per-table count rollup + a capped driftSample, ≤25). Drill into one table via `mode=diff detail="<table>"` (params: `detail`, `diffId`, `offset`, `limit`).
+- `sync_base mode=plan` now emits a curatable **changeset**: each action carries a stable name-based `changeId` (`<op>|<table>|<target>`), a `class`, and an `apply:true` flag; the digest includes a `sample` + an `editHint`. New `direction` param (`to-dest` default | `to-source`) targets either base as the destination.
+- `sync_base mode=apply` accepts a `skip:[changeId]` list (and honors `apply:false` on changeset entries) → applies everything except the removed changes. Journal-safe; skipped dependencies degrade gracefully to UNRESOLVABLE_REF.
+
+#### Fixed
+- `sync_base mode=apply` field creation — **autoNumber** fields now create. The read-only runtime counter `maxUsedAutoNumber` is stripped from `typeOptions` before `createField` (the internal API rejected it with 422 "options not valid").
+- `sync_base mode=apply` field creation — **count** fields now create. `toWritableComputedOptions` emitted the public-REST key `recordLinkFieldId`, but internal-API snapshots store a count's link under `relationColumnId` (like rollup) and the count create path passes `typeOptions` through untranslated — so every count field 422'd "options not valid". It now reads/emits the internal `relationColumnId`. (Both fixes validated live by converging a full base copy: 5 autoNumber + 3 count fields that previously failed now create cleanly.)
+- `sync_base mode=apply` — **createTable scaffolding rows are now removed** (clean mirror). A new table is seeded with ~3 blank rows (like the 6 default fields); apply already deleted the scaffolding fields but left the rows, so every synced table carried blank rows. The rows are now cleared right after create (best-effort; `SCAFFOLDING_ROWS_KEPT` warning on failure). Live-confirmed: createTable → 3 rows → 0.
+- `sync_base mode=diff` / view convergence — **empty-predicate filter representations no longer report false drift.** Airtable's internal API stores the same emptiness check two equivalent ways (`isNotEmpty`/null ≡ `!=`/"" and `isEmpty`/null ≡ `=`/""): a source base holds the named-operator form, the dest holds the `=`/`!=` form after the sync applied it. `canonFilterSet` now normalizes these (only when the value is genuinely empty — `0`/`false` are preserved), so semantically-equal filters compare equal in the diff report and stop re-emitting `applyViewConfig` every apply.
+
+### MCP server — sync_base record sync (2026-06-17)
+
+#### Added
+- `sync_base mode=apply`: after schema + view sync, launches a **background** record sync and returns a `jobId` immediately. Two-pass: Pass 1 creates/updates scalar + single/multi-select cells (computed fields + computed primary are never written) and fills a persisted `idmap.records` (rec→rec map); Pass 2 writes linked-record cells (remapped via record map, unresolved targets reported). Attachments are then downloaded from source and re-uploaded to dest (deduped by filename+size). Record-referencing view filters that were stripped during view sync are restored once records exist. Throttling is handled by per-request 429 backoff in the auth queue; resumable (records journal, per-chunk persist) and continue-on-failure (per-record errors are warnings, not aborts).
+- `sync_base mode=status`: poll a background record job by planId — returns running/done/failed plus live records-mapped count.
+- `sync_base mode=reconcile`: **prune** dead record-map entries (existence-prune). Per-table natural-key re-match is planned (not yet implemented); reconcile does not de-duplicate records.
+
+### MCP server — sync_base collaborative view sync (2026-06-17)
+
+#### Added
+- `sync_base`: full collaborative-view sync — create views + mirror filters, sorts, group levels, field visibility + column order, frozen columns, color config, cover, calendar date columns, form metadata, and row height, with source→dest field+choice ID remapping, per-view-type anchor validation + grid fallback, applied after fields. Idempotent (convergent canonical compare). Personal views skipped; orphan views reported (not deleted).
+
+### MCP server — sync_base mode=apply (2026-06-16)
+
+#### Added
+- `sync_base mode=apply`: execute a saved base-to-base schema plan against the destination — creates tables, reconciles the primary, creates scalar/link/computed fields (source→dest reference remapping + dest-space formula validation), and applies non-destructive field updates. Drift-guarded (aborts if the destination changed since the plan) and resumable via an on-disk journal. Type-changing retypes, deletions, records, and views are out of scope for this release.
+
 ### LSP server — fix runtime startup + CI bin-link warning (2026-06-12)
 
 - **`airtable-user-lsp` was runtime-broken when executed with Node directly**

diff --git a/CLAUDE.md b/CLAUDE.md
diff --git a/README.md b/README.md
@@ -208,6 +208,7 @@ Manage Airtable bases with capabilities **not available through the official RES
 | **Form Metadata** | 2 | Description, redirect URL, attribution, copy-to-respondent, branding (legacy form views) |
 | **Extension Management** | 7 | Create, install, enable/disable, rename, duplicate, remove extensions |
 | **Tool Management** | 1 | List profiles, switch profile, toggle tools/categories (meta-tool, always enabled) |
+| **Base Sync** | 1 | `sync_base` — copy a base's schema to another base. `mode=plan` produces a diff report; `mode=apply` executes it (creates tables/fields with ref remapping, drift-guarded, resumable via journal) and also syncs collaborative views (filters, sorts, groups, column order, frozen, color, cover, calendar, form, row height). Retypes, deletions, and records are out of scope. |
 
 See the full tool reference in [`packages/mcp-server/README.md`](packages/mcp-server/README.md).