fix: builder ID showing unknown after registration

[Kahtaf]

Summary

After running npm run register-builder, the output displays Builder ID: unknown instead of the actual builder ID. This makes it impossible for users to confirm their registration succeeded or to reference their builder ID for downstream configuration.

Root Cause

The gateway returns builder registrations with a builderId property, but the script was reading .id from the response body, which doesn't exist — causing the nullish coalescing to fall through to "unknown".

Additionally, the 409 conflict error message was misleading: it stated "This app URL is already registered with a different key", but the gateway's 409 is actually triggered by a duplicate granteeAddress, not a duplicate appUrl.

Changes

scripts/register-builder.ts

• Read .builderId instead of .id from the gateway response, fixing the "unknown" output
• Corrected the 409 error message to accurately describe the grantee address conflict
• Added type cast for signTypedData message parameter to fix a preexisting TS2322 error

scripts/register-server.ts

• Same signTypedData message type cast fix (preexisting TS2322)

scripts/tsconfig.json (new)

• Added a tsconfig for the scripts directory extending tsconfig.base.json, so scripts get proper type-checking with skipLibCheck and strict mode

tsconfig.json

• Added scripts to project references so tsc --build covers the scripts directory

Validation

• tsc --build passes with zero errors
• tsc --noEmit -p scripts/tsconfig.json passes with zero errors
• All pre-commit hooks (eslint, prettier, commitlint) pass