[botandbang]

What and why

Issues are now planned in Linear (workspace localnetwork, team LOC). Linear's GitHub integration syncs this repository's issues both ways with that team and links pull requests, so the GitHub Projects tooling that did this job is removed.

Removed: tools/project.sh, tools/project/plan.jq and plan.test, .github/project.json, .github/projects/ and .github/workflows/project.yml, plus the planner test step and its mention in repo-checks.yml.

Changed: CONTRIBUTING.md replaces "Issues and the project" with "Issues and planning", which covers what syncs, the Triage to Done statuses, linking pull requests with Fixes LOC-123 or a bnb/loc-123-… branch, and labels. NEW_PROJECT.md lists the Linear settings this depends on (the GitHub app, two-way Issues Sync, the importer, the branch format, Triage and the PR automations) and drops the step that created a GitHub project for each new app. The PR template mentions Fixes LOC-123.

Issue forms, labels, the labeler and the scheduled-failure issues are unchanged. GitHub stays where issues are filed.

Part of LOC-2

How it was tested

tools/policy.sh (60/60 policies, 41 tests), ast-grep test and ast-grep scan, actionlint and zizmor --offline over .github, all passing locally. The open issues were imported into Linear first: LOC has the same 93 open issues as GitHub, each linked to its GitHub issue.

Checklist

• Tests cover the change
• For the website: Storybook stories cover any new UI states
• For locallibrary: apps/locallibrary/CHANGELOG.md has a line under Unreleased, if people using it will notice
• The READMEs, docs/ and --help still say what the code does (apps/locallibrary/docs/rpc/ too, for a sidecar change)

[linear-code]

LOC-2

[github-actions]

Size

Compared with main. KiB are 1,024 bytes.

	This pull request	main	Change
Client JavaScript	619.2 KiB	619.2 KiB	0 B (0%)
Client JavaScript, brotli	204.5 KiB	204.5 KiB	0 B (0%)
Client CSS	87.6 KiB	87.6 KiB	0 B (0%)
Client CSS, brotli	12.5 KiB	12.5 KiB	0 B (0%)