chore: add t3.json with Tests and Lint scripts

[seankoji]

Summary

Adds a t3.json so T3 Code threads can run this repo's checks with one click. No setup script: the repo has no lockfile and nothing to install except PyYAML for the tests. Nothing else changes, and no workflow is touched.

What changed

• t3.json with two scripts, copied from .github/workflows/public-test.yml:
  • Tests: python3 -B -m unittest discover -s tests -p 'test_*.py' (-B keeps __pycache__ out of the checkout; .gitignore doesn't cover it).
  • Lint: py_compile over scripts/*.py. CI runs it as python -m py_compile scripts/*.py under 3.10. Here PYTHONPYCACHEPREFIX sends bytecode to $TMPDIR. The repo has no linter config that CI runs locally (static analysis is a reusable workflow).

Test plan

• Tests pass locally: fresh independent clone plus a linked worktree of it, venv with requirements-test.txt (PyYAML 6.0.3), Python 3.15.0: Ran 306 tests in 528s, OK
• Lint exits 0 in the linked worktree; git status stays clean afterwards
• CI passes
• Verified on live infra where applicable (n/a)
• No secrets, personal data, private hostnames, or private logs were added

Notes for reviewer

• Tests needs PyYAML on the interpreter (pip install -r requirements-test.txt), as in CI. Lint is stdlib-only. Without a setup script, a thread must have PyYAML available for Tests.
• Local Python is 3.15, not the 3.10 CI uses for py_compile, so Lint here is a syntax check on the local interpreter.
• No lifecycle scripts or hook installers exist (no package manifest), so nothing writes outside the checkout.

🤖 Generated with Claude Code