GeezerVison

Summary

• Six copies of Object.keys(updateData).filter(k => k !== 'updatedAt') across four files each decided independently which columns an audit row reports. The updatedAt exclusion is an audit convention, not a local detail, so it moves to @sim/audit as auditUpdatedFields and becomes a single edit
• Fixes a real inconsistency along the way: v1/admin/organizations/[id]/route.ts evaluated the expression twice in one handler and filed it under the metadata key fields, while every other site uses updatedFields. Any consumer filtering on updatedFields silently missed org updates. Verified nothing reads metadata.fields before renaming
• Follow-up to fix(mcp): audit the columns an MCP server update wrote, not the params it got #6598 and fix(mcp): audit an upsert that rewrites or revives a server #6602, which converged the MCP paths onto reporting written columns

Sites converted

Testing-mock note

auditMock carries the real implementation, not a vi.fn() stub — callers under test derive their audit metadata through it, so stubbing would erase exactly what those tests assert. The two suites that hand-roll their own @sim/audit factory (credentials/orchestration, workflow-mcp-lifecycle) source it from auditMock rather than re-inlining, so there is still one implementation.

Type of Change

• Refactor

Testing

• New packages/audit/src/updated-fields.test.ts: written columns, updatedAt dropped, explicitly-null columns kept (clearing a value is a change), and the only-updatedAt empty case
• 933 tests pass across lib/mcp, lib/credentials, lib/copilot/tools/handlers/deployment, app/api/mcp, app/api/v1/admin, app/api/v2/mcp; 29 in packages/audit
• lint:check and check:api-validation:strict pass; typecheck clean

Local-verification caveat worth knowing: this was developed in a git worktree whose node_modules symlinks to the main checkout, so @sim/audit and @sim/testing resolve to the main copy and a new package export is invisible to the worktree's test run. Every result above was produced by temporarily materializing the two package files into the main checkout, running, then restoring it — otherwise the run reports phantom failures that look like this change breaking 100+ audit-mocking suites.

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)