Shard tsgolint into memory-budgeted Buck actions

[schickling-assistant]

Outcome

Run tsgolint as per-project Buck actions with a declared memory budget. Keep the same lint authority without requiring a larger runner.

Evidence

The lint lane reached 14.78 GiB on a 16 GiB runner and recorded an OOM kill. The Buck daemon held 4–5 GiB resident in that run; local measurements observed daemon residency up to 10.4 GiB. A second fresh isolation daemon can overlap the whole-repository tsgolint process.

Acceptance

• tsgolint is sharded by TypeScript project as cacheable Buck actions
• each action has an explicit memory budget and bounded concurrency
• fresh gate isolation daemons are reaped by the owning gate
• lint output and failure semantics remain equivalent
• a fresh 16 GiB CI run completes without OOM
• measured peak RSS and per-shard action counts are recorded

Refs #1147
Refs #1227

Posted on behalf of @schickling

field	value
agent_identity	dev3.direct.omp.x7qqfv7y
session	dev3.x7qqfv7y
agent_persona	generalist
agent_supervisor	unavailable
agent_tool	OMP
agent_tool_version	18.1.7
agent_runtime	OMP 18.1.7
tooling_profile	dotfiles@c5db483