Add developer foundation: Git hooks suite, issue templates, editorconfig

.editorconfig

@@ -0,0 +1,21 @@
+root = true
+
+[*]
+charset = utf-8
+end_of_line = lf
+insert_final_newline = true
+trim_trailing_whitespace = true
+indent_style = space
+indent_size = 2
+
+[*.go]
+indent_style = tab
+
+[Makefile]
+indent_style = tab
+
+[{go.mod,go.sum}]
+indent_style = tab
+
+[*.{md,markdown}]
+trim_trailing_whitespace = false

.githooks/commit-msg

@@ -0,0 +1,37 @@
+#!/usr/bin/env bash
+# commit-msg hook: enforce DCO sign-off and ≤72-char subject locally so we
+# don't burn a CI cycle (or push, see the maintainer's mood drop) discovering
+# either after the fact. Skips git-managed commit shapes (Merge, fixup!,
+# squash!, amend!) where the rules don't apply or git rewrites the message.
+# Bypass with `git commit --no-verify` if you must — CI still checks.
+set -euo pipefail
+
+msg_file="$1"
+[ -f "$msg_file" ] || exit 0
+
+# First non-comment line is the subject (`git commit -v` prepends comments).
+subject=$(grep -v '^#' "$msg_file" | head -n 1)
+
+case "$subject" in
+    Merge*|fixup!*|squash!*|amend!*) exit 0 ;;
+esac
+
+# Subject length — see STYLE.md §"Commits".
+subject_len=${#subject}
+if [ "$subject_len" -gt 72 ]; then
+    echo "ERROR: commit subject is $subject_len chars (limit: 72)." >&2
+    echo "  Subject: $subject" >&2
+    echo "  Trim the subject; put detail in the body." >&2
+    exit 1
+fi
+
+# DCO sign-off — mirrors the rules enforced by .github/scripts/dco-check.sh
+# (the CI gate). Keep this check in sync if that script changes.
+if ! grep -q '^Signed-off-by: ' "$msg_file"; then
+    echo "ERROR: missing Signed-off-by trailer." >&2
+    echo "  Use 'git commit -s' to add it, or amend with --signoff." >&2
+    echo "  See CONTRIBUTING.md §'Sign off your commits'." >&2
+    exit 1
+fi
+
+exit 0

.githooks/pre-commit

@@ -0,0 +1,6 @@
+#!/usr/bin/env bash
+# Pre-commit hook: run `make check` to keep the inner loop honest.
+# Installed by `make hooks`, which sets core.hooksPath to .githooks.
+# Bypass with `git commit --no-verify` if you must — CI will still catch you.
+set -euo pipefail
+exec make check

.githooks/pre-push

@@ -0,0 +1,7 @@
+#!/usr/bin/env bash
+# pre-push hook: run `make ci` so the moment of truth is `git push`, not the
+# wait for GitHub Actions. Catches what `make check` (the pre-commit gate)
+# deliberately skips: license-check, full build, govulncheck-adjacent checks.
+# Bypass with `git push --no-verify` if you must — CI will still catch you.
+set -euo pipefail
+exec make ci

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,58 @@
+---
+name: Bug report
+about: Report something that isn't working
+title: ''
+labels: bug
+---
+
+<!--
+Before filing: please check existing issues to avoid duplicates, and confirm
+you're on a recent build. For security issues, use a private advisory — not
+this template. See SECURITY.md.
+-->
+
+## What happened
+
+<!-- A clear, concrete description of the unexpected behavior. -->
+
+## What you expected
+
+<!-- What should have happened instead. -->
+
+## Reproduction
+
+<!--
+Minimal config + commands that reproduce the bug. The smaller, the better.
+If the repro needs hardware we may not have (specific GPU, NCCL version,
+kernel feature), say so explicitly.
+-->
+
+```yaml
+# minimal config here
+```
+
+```sh
+# commands here
+```
+
+## Environment
+
+- tracecore version (`tracecore --version`):
+- OS / kernel:
+- Go version (`go version`) — only if building from source:
+- GPU / driver / NCCL versions — only if relevant to the bug:
+
+## Logs
+
+<!--
+Run with `--log.level=debug` if possible and paste the relevant excerpt.
+Redact secrets, tokens, and anything you wouldn't post in public.
+-->
+
+```
+logs here
+```
+
+## Additional context
+
+<!-- Anything else that might help: when it started, related issues, workarounds tried. -->

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,11 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Architectural proposal (RFC)
+    url: https://github.com/TraceCoreAI/tracecore/blob/main/docs/rfcs/0000-template.md
+    about: Architectural decisions go through the RFC process. Copy the template into docs/rfcs/ and open a PR — not an issue.
+  - name: Security vulnerability
+    url: https://github.com/TraceCoreAI/tracecore/security/advisories/new
+    about: Report vulnerabilities privately, never as public issues. See SECURITY.md.
+  - name: Question or discussion
+    url: https://github.com/TraceCoreAI/tracecore/discussions
+    about: For open-ended questions and design discussion. Bugs and feature requests belong in issues.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,48 @@
+---
+name: Feature request
+about: Suggest a new feature or enhancement
+title: ''
+labels: enhancement
+---
+
+<!--
+Before filing: please check existing issues and the milestone roadmap in
+MILESTONES.md to see whether this is already planned or out of scope.
+
+If the change is *architectural* (new subsystem, new dependency, new
+public surface), please file an RFC under docs/rfcs/ instead. See
+CONTRIBUTING.md §"RFC process".
+-->
+
+## Problem
+
+<!--
+What problem does this solve? Who hits it, how often, and what's the
+cost of *not* having it? Skip "wouldn't it be cool if" framing — start
+with the concrete pain.
+-->
+
+## Proposal
+
+<!--
+What change would address it? Be specific enough that someone could
+estimate effort. Sketch the user-facing API, config, or behavior.
+-->
+
+## Alternatives considered
+
+<!--
+What other approaches did you think about? Why are they worse? If you
+considered nothing, that's a signal the proposal isn't ready yet.
+-->
+
+## Out of scope
+
+<!--
+Things this proposal explicitly does NOT include, to keep discussion
+focused. Future extensions can be follow-ups.
+-->
+
+## Additional context
+
+<!-- Related issues, prior art in other tools, links to discussions. -->

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,6 +1,9 @@
 <!--
 Thanks for contributing to tracecore. Please read CONTRIBUTING.md and STYLE.md
-before submitting. Keep PRs under 500 lines and focused on one concern.
+before submitting. Keep PRs focused on one concern — split when the diff
+outgrows the concern, not at an arbitrary line count. Prerequisite cleanup
+the change itself surfaces (e.g., a tidy-drift fix needed for a new gate to
+land green) can ride along when called out in the PR body.
 -->
 
 ## What this PR does
@@ -9,9 +12,13 @@ before submitting. Keep PRs under 500 lines and focused on one concern.
 
 ## Linked issue(s)
 
-<!-- "Fixes #123" or "Refs #123". Use "Fixes" only if this PR closes the issue. -->
+<!--
+"Fixes #123" or "Refs #123". Use "Fixes" only if this PR closes the issue.
+Replace this block with the actual reference, or delete the entire
+"Linked issue(s)" section if no issue applies.
+-->
 
-Fixes #
+_No linked issue._
 
 ## Release notes
 
@@ -28,7 +35,8 @@ Categories: FEATURE, ENHANCEMENT, BUGFIX, PERF, SECURITY, CHANGE
 ## Checklist
 
 - [ ] Tests added or updated
-- [ ] `make ci` passes locally
+- [ ] `make check` runs green continuously while editing; `make ci` passes before pushing
 - [ ] Commits are signed off (`git commit -s`)
 - [ ] If AI-assisted, commit message includes `Assisted-by:` trailer (see [`AGENTS.md`](../AGENTS.md))
 - [ ] For new components, follows the layout required by [`STYLE.md`](../STYLE.md)
+- [ ] PR title and Summary still reflect the current diff (re-check after pushing fixes)

CONTRIBUTING.md

@@ -23,15 +23,21 @@ When you choose to file one:
 All developer tools (gofumpt, goimports, golangci-lint, govulncheck, addlicense) are pinned in `go.mod` under the `tool` directive and fetched automatically. There is no separate `install-tools` step.
 
 ```sh
-go mod download       # one-time after clone
+scripts/setup-dev.sh  # one-shot: go mod download + install all hooks
 make build            # builds ./tracecore
 make test             # unit tests with race detector
 make lint             # runs golangci-lint
 make check            # fast inner loop: fmt + tidy-check + lint + test
 make ci               # what CI runs: license-check + vet + tidy-check + lint + test + build
 ```
 
-Use `make check` continuously while editing; use `make ci` once before pushing.
+`scripts/setup-dev.sh` is idempotent — rerun it whenever. It installs three hooks (opt-in via `core.hooksPath = .githooks`) so problems surface before they hit CI:
+
+- **`pre-commit`** runs `make check` — fmt, tidy, lint, race-tested tests.
+- **`commit-msg`** enforces the ≤72-char subject and DCO sign-off rules from STYLE.md §"Commits".
+- **`pre-push`** runs `make ci` — the full gate CI runs, locally, before the network round-trip.
+
+Bypass any hook with `--no-verify` if you must (`git commit --no-verify`, `git push --no-verify`); CI still catches what you skip.
 
 ## Pull requests
 

Makefile

@@ -1,4 +1,4 @@
-.PHONY: help build run test fmt fmt-fix vet lint lint-fix tidy tidy-check mod-verify license-check license-fix govulncheck dco-check ai-review clean check ci
+.PHONY: help build run test fmt fmt-fix vet lint lint-fix tidy tidy-check mod-verify license-check license-fix govulncheck dco-check ai-review hooks clean check ci
 
 BIN          := tracecore
 PKG          := ./cmd/tracecore
@@ -93,6 +93,14 @@ dco-check:  ## Verify DCO sign-off on every commit since origin/main.
 ai-review:  ## Run advisory Claude review on staged Go changes (never blocks).
 	@scripts/ai-review.sh
 
+hooks:  ## Install repo-managed Git hooks (sets core.hooksPath to .githooks).
+	@git config core.hooksPath .githooks
+	@echo "Hooks installed under .githooks/ — all three now active:"
+	@echo "  pre-commit  -> make check  (fmt, tidy-check, lint, test)"
+	@echo "  commit-msg  -> ≤72-char subject + DCO sign-off"
+	@echo "  pre-push    -> make ci     (full gate)"
+	@echo "Bypass any one with --no-verify; CI still catches what you skip."
+
 clean:  ## Remove built binaries.
 	rm -f $(BIN)
 	go clean

scripts/setup-dev.sh

@@ -0,0 +1,33 @@
+#!/usr/bin/env bash
+# One-shot dev environment bootstrap. Run after cloning. Idempotent —
+# rerunning is safe and only re-applies what changed.
+set -euo pipefail
+
+cd "$(git rev-parse --show-toplevel)"
+
+if ! command -v go >/dev/null 2>&1; then
+    required=$(cat .go-version 2>/dev/null || echo "see .go-version")
+    echo "ERROR: Go is not installed or not on PATH." >&2
+    echo "  Required version: $required" >&2
+    echo "  Install from https://go.dev/dl/ or via your package manager." >&2
+    exit 1
+fi
+
+echo "==> Downloading Go modules..."
+go mod download
+
+echo "==> Installing Git hooks..."
+make hooks
+
+cat <<'EOF'
+
+Setup complete. The hooks now run automatically:
+  pre-commit  -> make check  (fmt, tidy-check, lint, test)
+  commit-msg  -> DCO sign-off + subject length
+  pre-push    -> make ci     (license, vet, lint, tidy, test, build)
+
+Manual commands you'll still want:
+  make check        fast inner loop (~10s)
+  make ci           full pre-push gate (~30s)
+  make help         every target with one-line docs
+EOF