feat: add reuse feedback path and prep v0.1.5

Author: hahajunj

.github/ISSUE_TEMPLATE/config.yml

@@ -1,5 +1,8 @@
 blank_issues_enabled: false
 contact_links:
+  - name: Tried this in a real repository?
+    url: https://github.com/junjapp/oss-maintainer-workflows/issues/new?template=reuse-report.yml
+    about: Share what you kept, cut, or rewrote so the maintainer kit can improve against real reuse cases.
   - name: Not sure which issue type fits?
     url: https://github.com/junjapp/oss-maintainer-workflows/issues/new?template=open-question.yml
     about: Use the open question template if the current issue types feel too specific or do not fit your situation yet.

.github/ISSUE_TEMPLATE/reuse-report.yml

@@ -0,0 +1,28 @@
+name: Reuse report
+description: Share how you copied, trimmed, or adapted this kit in a real repository.
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Use this if you tried the kit in a real repository and want to share what helped, what you cut, or what still felt too source-repo-specific.
+  - type: textarea
+    id: repository_context
+    attributes:
+      label: What kind of repository did you try this in?
+      description: Describe the project shape in plain language. If you can share a public link, include it.
+    validations:
+      required: true
+  - type: textarea
+    id: kept_cut_changed
+    attributes:
+      label: What did you keep, cut, or change?
+      description: Call out the pieces you actually kept, removed, or rewrote on the first pass.
+    validations:
+      required: true
+  - type: textarea
+    id: outcome
+    attributes:
+      label: What helped, and what still felt off?
+      description: Share what made reuse easier and what still felt too specific, heavy, or unclear.
+    validations:
+      required: true

CHANGELOG.md

@@ -4,6 +4,9 @@ All notable changes to this project will be documented in this file.
 
 ## [Unreleased]
 
+## [0.1.5] - 2026-03-23
+
+- Added a reuse-report issue path so real downstream maintainers can share what they kept, cut, or rewrote after trying the kit.
 - Added an open-question issue template and removed issue title prefixes so unclear reports can arrive without being forced into the wrong bucket first.
 - Added a smaller, concrete copy path for repositories that only want core docs, one issue template, and an optional trimmed validation baseline, including a new minimal-copy example.
 - Added a lightweight code of conduct and issue-template chooser config so copied repositories get a clearer public governance baseline.

README.md

@@ -156,6 +156,10 @@ That keeps the public checks truthful while still giving the repository a minima
 - contributor-facing docs that stay close to actual repository behavior
 - lightweight governance files that make maintenance easier to hand over
 
+## Using this kit?
+
+If you try this in a real repository, open a reuse report and say what you kept, cut, or rewrote on the first pass. That kind of feedback is more useful here than a generic +1 because it shows where the maintainer layer is actually helping and where it still reads too much like the source repository.
+
 ## Next step
 
 Adapt the templates to a real repository, then keep the docs, issue flow, and release process aligned as the project evolves.

package-lock.json

@@ -1,6 +1,6 @@
 {
   "name": "oss-maintainer-workflows",
-  "version": "0.1.4",
+  "version": "0.1.5",
   "description": "Reusable maintainer operations kit for small public OSS repositories.",
   "type": "module",
   "private": false,

package.json

@@ -17,6 +17,7 @@ export const requiredPaths = [
   ".github/ISSUE_TEMPLATE/bug-report.yml",
   ".github/ISSUE_TEMPLATE/docs-request.yml",
   ".github/ISSUE_TEMPLATE/open-question.yml",
+  ".github/ISSUE_TEMPLATE/reuse-report.yml",
   ".github/ISSUE_TEMPLATE/workflow-improvement.yml",
   ".github/workflows/validate.yml",
   ".github/workflows/release-check.yml",

scripts/validate-repo.mjs

@@ -134,6 +134,10 @@ test("public docs describe a concrete adoption and release path", async () => {
     path.join(repoRoot, ".github", "ISSUE_TEMPLATE", "open-question.yml"),
     "utf8",
   );
+  const reuseReportTemplate = await fs.readFile(
+    path.join(repoRoot, ".github", "ISSUE_TEMPLATE", "reuse-report.yml"),
+    "utf8",
+  );
 
   assert.match(readme, /Minimal rollout path/);
   assert.match(readme, /Replace before reuse/);
@@ -148,6 +152,7 @@ test("public docs describe a concrete adoption and release path", async () => {
   assert.match(readme, /first downstream pass can look like/);
   assert.match(readme, /smallest believable downstream pass/);
   assert.match(readme, /neutral open-question issue path/);
+  assert.match(readme, /If you try this in a real repository, open a reuse report/);
   assert.match(readme, /CODE_OF_CONDUCT\.md/);
   assert.match(readme, /\.github\/ISSUE_TEMPLATE\/config\.yml/);
   assert.match(codeowners, /Replace this entry before reusing the scaffold/);
@@ -158,13 +163,17 @@ test("public docs describe a concrete adoption and release path", async () => {
   assert.match(codeOfConduct, /public, respectful, and workable/);
   assert.match(issueTemplateConfig, /blank_issues_enabled: false/);
   assert.match(issueTemplateConfig, /open-question\.yml/);
+  assert.match(issueTemplateConfig, /reuse-report\.yml/);
   assert.match(issueTemplateConfig, /contact_links:/);
   assert.doesNotMatch(bugTemplate, /title:/);
   assert.doesNotMatch(docsTemplate, /title:/);
   assert.doesNotMatch(workflowTemplate, /title:/);
   assert.match(openQuestionTemplate, /name: Open question/);
   assert.match(openQuestionTemplate, /labels:\s*\n\s*- triage/);
   assert.match(openQuestionTemplate, /rough report is fine/);
+  assert.match(reuseReportTemplate, /name: Reuse report/);
+  assert.match(reuseReportTemplate, /real repository/);
+  assert.match(reuseReportTemplate, /kept, removed, or rewrote|keep, cut, or change/);
   assert.match(releasePlaybook, /Versioning notes/);
   assert.match(releasePlaybook, /Release note/);
   assert.match(releasePlaybook, /Pre-tag command sequence/);
@@ -191,7 +200,7 @@ test("public docs describe a concrete adoption and release path", async () => {
   assert.match(roadmap, /How to use this roadmap/);
   assert.match(roadmap, /copy and cleanup cycle/);
   assert.match(roadmap, /real downstream first pass/);
-  assert.equal(packageJson.version, "0.1.4");
+  assert.equal(packageJson.version, "0.1.5");
   assert.equal(
     packageJson.description,
     "Reusable maintainer operations kit for small public OSS repositories.",

tests/public-surface.test.mjs

@@ -90,6 +90,7 @@ test("requiredPaths reflect the renamed public docs layout", () => {
 
 test("requiredPaths include the generic issue intake path", () => {
   assert.ok(requiredPaths.includes(".github/ISSUE_TEMPLATE/open-question.yml"));
+  assert.ok(requiredPaths.includes(".github/ISSUE_TEMPLATE/reuse-report.yml"));
 });
 
 test("requiredPaths stay limited to the public scaffold", () => {