feat: add retention feedback loop and honest support matrix (#2681)

* feat: add retention feedback loop

* test: retire obsolete README parity row guard

* fix: harden public feedback guidance

* fix: let feedback CLI output flush

* test: keep feedback help coverage focused
This commit is contained in:
haelyra authored and GitHub committed 2026-08-04 21:42:25 -04:00
1 parent 7a5757e6c0
commit f1fec0e539
21 files changed
+486 -93

No files matched your search

+8
View File
@@ -0,0 +1,8 @@
blank_issues_enabled: true
contact_links:
- name: ECC questions and setup help
url: https://github.com/affaan-m/ECC/discussions/categories/q-a
about: Ask a public question or get help from the community.
- name: Private security report
url: https://github.com/affaan-m/ECC/security/advisories/new
about: Report vulnerabilities privately. Do not put secrets in a public issue.
@@ -0,0 +1,40 @@
name: Feature idea
description: Describe the outcome you need and your current workaround.
title: "[Idea] "
labels:
- enhancement
- needs-triage
body:
- type: markdown
attributes:
value: |
This is a public GitHub issue. Do not include secrets, prompts, customer data, private repository details, or unredacted paths.
- type: textarea
id: outcome
attributes:
label: What outcome do you need?
description: Describe the job to be done, not an implementation if you do not have one in mind.
validations:
required: true
- type: textarea
id: workaround
attributes:
label: What do you do today?
description: Optional. A workaround helps us understand urgency and scope.
- type: dropdown
id: harness
attributes:
label: Which harness is affected?
options:
- All harnesses
- Claude Code
- Codex
- Cursor
- OpenCode
- GitHub Copilot
- Another harness
- type: textarea
id: success
attributes:
label: What would success look like?
description: Optional acceptance criteria or a small example.
@@ -0,0 +1,93 @@
name: Install or runtime problem
description: Tell us what failed without writing a full diagnostic report.
title: "[Problem] "
labels:
- bug
- needs-triage
- area:install
body:
- type: markdown
attributes:
value: |
Thanks for reporting this. Keep it short: what happened and which setup you used are enough to start.
This issue is public. Do not paste secrets, prompts, private repository names, or unredacted home/project paths. ECC never uploads diagnostics automatically.
- type: dropdown
id: impact
attributes:
label: What is the impact?
options:
- ECC will not install
- ECC installs, but nothing loads
- Some components are missing or silently ignored
- ECC is duplicated or conflicts with another install
- A hook or command interrupts normal work
- Doctor or repair does not recover the install
- Other runtime problem
validations:
required: true
- type: textarea
id: happened
attributes:
label: What happened?
description: Include the shortest error or symptom that explains the problem.
placeholder: I expected …, but …
validations:
required: true
- type: dropdown
id: harness
attributes:
label: Harness
options:
- Claude Code
- Codex app or CLI
- Cursor
- OpenCode
- GitHub Copilot
- Kimi Code
- Gemini CLI
- Zed
- Antigravity
- Qwen
- Hermes
- OpenClaw
- CodeBuddy or JoyCode
- Other
validations:
required: true
- type: dropdown
id: install_method
attributes:
label: Install method
options:
- Claude plugin marketplace
- ecc or ecc-install CLI
- Manual clone or copy
- Codex sync script
- Codex marketplace plugin
- Harness-specific installer target
- Unknown
- Other
- type: dropdown
id: operating_system
attributes:
label: Operating system
options:
- Windows (native)
- Windows (WSL)
- macOS
- Linux
- Other
validations:
required: true
- type: input
id: versions
attributes:
label: ECC and harness versions
description: If known. A tag, commit, or package version is enough.
placeholder: ECC 2.1.0; Claude Code 2.x
- type: textarea
id: diagnostics
attributes:
label: Optional redacted diagnostics
description: Paste only the relevant lines from `ecc doctor`. Remove paths, repository names, prompts, tokens, and secrets.
+56
View File
@@ -0,0 +1,56 @@
name: Quick product feedback
description: One required choice and an optional sentence. Leaving ECC is valid feedback.
title: "[Feedback] "
labels:
- feedback
- needs-triage
body:
- type: markdown
attributes:
value: |
Thank you for telling us what got in the way. This form is intentionally short.
This is a public GitHub issue. Do not include secrets, prompts, customer data, or private repository details.
Report a vulnerability through [GitHub's private security advisory form](https://github.com/affaan-m/ECC/security/advisories/new), not here. Non-vulnerability security or trust concerns are welcome in this form.
- type: dropdown
id: reason
attributes:
label: What best describes your feedback?
options:
- I could not install or activate ECC
- ECC made the agent slower or the output worse
- ECC used too much token or context budget
- Hooks or gates interrupted normal work
- ECC was too complicated or required too much configuration
- My harness or operating system was missing or unreliable
- I had a security or trust concern
- A feature I needed was missing
- Support was too slow
- I was only testing and no longer need it
- Something worked especially well
- Other
validations:
required: true
- type: dropdown
id: harness
attributes:
label: Where did you use ECC?
options:
- Claude Code
- Codex
- Cursor
- OpenCode
- GitHub Copilot
- Another harness
- I did not get far enough to use it
- type: textarea
id: change
attributes:
label: What is the one change that would matter most?
description: Optional. One sentence is plenty.
- type: textarea
id: keep
attributes:
label: What should ECC keep?
description: Optional. Tell us what was valuable even if the overall experience did not work.