chore: migrate to @harperfast/code-guidelines

[Ethan-Arrowood]

@harperdb/code-guidelines has been deprecated and republished as @harperfast/code-guidelines. Version 0.1.2 is functionally identical to 0.0.6 — no config changes, just the new package name (0.1.2 also adds a files allowlist so .claude and docs are no longer included in the published artifact).

This updates the dependency, any config references (prettier/eslint/docs), and the lockfile. No new lockfiles were added.

_{sent with Claude Fable 5}

[gemini-code-assist]

Code Review

This pull request updates the development dependency @harperdb/code-guidelines to @harperfast/code-guidelines (version ^0.1.1) in both package.json and package-lock.json, and updates the Prettier configuration path accordingly. Additionally, package-lock.json reflects minor metadata adjustments for several optional dependencies. There are no review comments, and I have no feedback to provide.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​harperfast/​code-guidelines@​0.1.2

View full report

[claude]

Reviewed; no blockers found.

[kriszyp]

code guidelines looks good. Again, package-lock.json.

_{🤖 Reviewed with GPT 5.6}

[kriszyp]

Could you preserve the unrelated libc metadata while regenerating this lockfile? The selector was removed from all four RocksDB Linux packages (and the affected oxlint bindings). npm treats a missing libc field as compatible: on x64 glibc, Arborist now leaves both the glibc and musl RocksDB packages active, so installs download both ~5–6 MB native tarballs, and the published shrinkwrap retains the missing selectors. I reproduced the source of the churn with the repo's base lock: npm 11.5.1 strips this field, while npm 11.16.0 preserves it. Regenerating the rename from the base lock with the current supported Node/npm toolchain, or restoring the dropped libc fields, keeps each Linux install on its single matching binary.

[kriszyp]

Looks good.
_{🤖 Reviewed with GPT 5.6}

[kriszyp]

Could you preserve the unrelated libc metadata while regenerating this lockfile? The selector was removed from all four RocksDB Linux packages (and the affected oxlint bindings). npm treats a missing libc field as compatible: on x64 glibc, Arborist now leaves both the glibc and musl RocksDB packages active, so installs download both ~5–6 MB native tarballs, and the published shrinkwrap retains the missing selectors. I reproduced the source of the churn with the repo's base lock: npm 11.5.1 strips this field, while npm 11.16.0 preserves it. Regenerating the rename from the base lock with the current supported Node/npm toolchain, or restoring the dropped libc fields, keeps each Linux install on its single matching binary.