chore: OSS polish — labels, stale workflow, citation, repo settings

.github/workflows/stale.yml

@@ -0,0 +1,33 @@
+name: Stale Issues
+
+on:
+  schedule:
+    - cron: "30 1 * * *" # Daily at 01:30 UTC
+  workflow_dispatch:
+
+permissions:
+  issues: write
+  pull-requests: write
+
+jobs:
+  stale:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/stale@v9
+        with:
+          stale-issue-message: >
+            This issue has been automatically marked as stale because it has not had
+            recent activity. It will be closed in 14 days if no further activity occurs.
+            If this issue is still relevant, please comment or remove the stale label.
+          stale-pr-message: >
+            This pull request has been automatically marked as stale because it has not
+            had recent activity. It will be closed in 14 days if no further activity occurs.
+          close-issue-message: >
+            This issue was closed because it has been stale for 14 days with no activity.
+            Feel free to reopen if it's still relevant.
+          days-before-stale: 60
+          days-before-close: 14
+          stale-issue-label: "stale"
+          stale-pr-label: "stale"
+          exempt-issue-labels: "priority: critical,priority: high,epic,story"
+          exempt-pr-labels: "priority: critical,priority: high"

CITATION.cff

@@ -0,0 +1,17 @@
+cff-version: 1.2.0
+title: "go-modkit/benchmarks"
+message: "If you use this benchmark harness or reference its results, please cite it."
+type: software
+authors:
+  - family-names: Kogan
+    given-names: Arye
+    email: aryekogan@gmail.com
+url: "https://github.com/go-modkit/benchmarks"
+repository-code: "https://github.com/go-modkit/benchmarks"
+license: MIT
+keywords:
+  - benchmark
+  - go
+  - framework-benchmark
+  - api-parity
+  - performance-testing