chore: make the lint gate green and actually run it

[PhilflowIO]

Stacked on #32 — base is fix/todo-fetch-override, not master. See "Why stacked" below; GitHub will retarget this to master automatically once #32 merges. Review #32 first.

The three loose ends from #30/#31, and the reason they went unnoticed for so long.

The through-line

pnpm lint has been red on master. Nothing caught it, because the lint gate never ran:

• ci.yml — the workflow that runs typecheck, lint and test — triggers only on pull requests to main. The default branch is master and no main branch exists, so it has never run on any PR. That is also why the makeAddressBook typecheck error from fix(carddav): honour fetch override in makeAddressBook #31 sat on master unnoticed.
• release.yml had its lint step commented out.

So the only workflow that actually ran was quality-checks.yml, which does not lint.

Changes

Commit
style: apply prettier to the last lint holdouts	pnpm lint --fix. Whitespace only across 4 files.
chore(hooks): drop deprecated husky v8 preamble	Removes the shebang + _/husky.sh source.
ci: run CI on pull requests to master	branches: [main] → [master, main], matching quality-checks.yml.
ci: re-enable lint in the release workflow	Uncomments the step.

pnpm lint now reports 0 errors, and two workflows will actually enforce it.

The husky change is verified rather than assumed: the three commits after it were made with the preamble removed, and the hook still ran every check — signature scan, version check, dist rebuild — with the DEPRECATED warning gone.

The prettier pass is whitespace only, but the non-minified bundles pick up the reformatting, so dist/ is rebuilt and the patch version bumped. The dist diff is generated; the CI gate verifies it.

Why stacked on #32

Basing this on master produces a genuine merge conflict with #32. Both branches rewrite the same lines of client.ts: prettier collapses the six long single-line DAVClient todo methods into multi-line form, and #32 rewrites those same lines into multi-line form plus a fetch: this.fetchOverride entry. Two different rewrites of the same region — git cannot auto-merge them. I confirmed this by building the branch both ways.

Stacking avoids it: lint --fix runs against the post-#32 tree, where 6 of the 10 errors are already gone as a side effect of that PR, leaving only the 4 genuinely-formatting ones. Merge #32 first and this applies cleanly. If you would rather have it off master, say so and I will re-cut it — that just means #32 rebases instead.

Verification

$ pnpm lint      # 0 errors
$ pnpm typecheck # clean
$ pnpm test
Tests:       42 passed, 42 total

Workflow triggers after the change:

ci             -> pull_request: branches ['master', 'main']
release        -> release: types ['published']
quality-checks -> pull_request + push: branches ['master', 'main']

Note

ci.yml will now run for real for the first time, on this PR and every future one. It runs pnpm test across Node 18/20/22/24 with mocked fetch. If it turns up something that has been failing invisibly on a Node version I have not exercised locally (I am on 22, .nvmrc says 24), that is the gate doing its job rather than a regression from this PR — tell me and I will fix it separately.

CI status on this PR

This PR shows 0 checks, and that is expected: quality-checks.yml triggers on pull_request: branches: [master, main], so it does not fire for a PR targeting fix/todo-fetch-override. Once #32 merges and GitHub retargets this to master, the workflow will run.

Until then the gates were run locally against this exact tree: pnpm lint 0 errors, pnpm typecheck clean, 42/42 tests, and the dist gate (pnpm build then git diff dist/) reproduces the committed build.