Summary
After submitting a bug report through the Amicode bug dock and closing the window, there is no way to view what was submitted, check its status, or find the issue number. There is also no mechanism to track submission history across sessions or surface any engagement signal that would encourage users to report more.
Context
- Extension: harmoniqs.amicode 0.2.1
- OS: Darwin 25.2.0 arm64
- Engine: harmoniqs/opencode @ v1.18.10-amicode.4 (base v1.18.10)
- Active run: none
Expected vs actual
Expected: After closing the bug dock, the user can navigate to a history view showing previously filed reports — their title, status (open/closed/resolved), and issue number — with optional engagement signals to incentivize participation.
Actual: Closing the bug dock discards all session state. There is no persistent history, no issue number surfaced to the user, no way to follow up or confirm the report landed.
Additional context
The reporter specifically flagged engagement incentives as a desirable direction: prizes or badges awarded at submission milestones (e.g. "10 bugs filed"), and a visual status signal on the Amicode token itself — the token color or appearance changing as the user reaches higher contribution tiers (however those tiers are defined). The goal is to make bug and feature reporting feel rewarding rather than a dead drop.
Diagnostics
- No active run this session
- diagnostics: inline
intake: not-ready — mature per the maturity contract before picking up
suggested_path: B
diagnostics: inline
upstream: n/a
Summary
After submitting a bug report through the Amicode bug dock and closing the window, there is no way to view what was submitted, check its status, or find the issue number. There is also no mechanism to track submission history across sessions or surface any engagement signal that would encourage users to report more.
Context
Expected vs actual
Expected: After closing the bug dock, the user can navigate to a history view showing previously filed reports — their title, status (open/closed/resolved), and issue number — with optional engagement signals to incentivize participation.
Actual: Closing the bug dock discards all session state. There is no persistent history, no issue number surfaced to the user, no way to follow up or confirm the report landed.
Additional context
The reporter specifically flagged engagement incentives as a desirable direction: prizes or badges awarded at submission milestones (e.g. "10 bugs filed"), and a visual status signal on the Amicode token itself — the token color or appearance changing as the user reaches higher contribution tiers (however those tiers are defined). The goal is to make bug and feature reporting feel rewarding rather than a dead drop.
Diagnostics
intake: not-ready — mature per the maturity contract before picking up
suggested_path: B
diagnostics: inline
upstream: n/a