Added automated upstream git pull before deterministic audit runs

Why

When developers pushed new commits to GitHub, the VPS clone did not automatically pull them, resulting in repeated “4 behind master (not synced)” warnings during audits.

Problem

scripts/emiclaw-audit.mjs performed git fetch origin master to calculate commit drift, but did not execute a pull command. Audits were consequently running against stale local revisions instead of the true master commit.

Approach

Added an automated fast-forward pull step in Step 1 of emiclaw-audit.mjs that triggers whenever behindCount > 0, and brought the audit script into Git version control.

Implementation

• Added scripts/emiclaw-audit.mjs directly into the repository root.
• Integrated git pull origin master --ff-only before Vitest and Astro typecheck steps.
• Created docs/EMICLAW_CHANGELOG.md to formally record all future developer contributions and bug fixes.
• Deployed the updated script to /home/deploy/scripts/emiclaw-audit.mjs on the VPS.

Verification

• Executed audit script: successfully pulled new commits from origin/master, ran 120 Vitest suites (PASS), ran 168-file typecheck (PASS), and output synced: Yes (0 behind).

Result

Audits now automatically evaluate the latest master commit without manual operator intervention.