Goal
Collect real self-serve feedback for the audited AnchorMap preview and make the results actionable without expanding product scope prematurely.
This issue is the operational hub for PREVIEW-3. It should link, summarize, and triage feedback from real preview runs by early preview users. It should not invent feedback, simulate adoption, or treat demo evidence as user feedback.
Current Preview Inputs
Expected Feedback Channels
Ask preview users to open the most specific issue template and share only sanitized material:
- Design partner feedback: overall preview experience, setup time, report usefulness, noise level, no-source-upload importance, and future capability interest.
- Action installation problem: setup failures, workflow failures, runner details, exit codes, missing artifacts, or unexpected source-upload/server behavior.
- Confusing PR report: report sections that were hard to interpret, with the smallest sanitized snippet needed.
- Policy request: missing policy controls, tuning needs, warning-only behavior, and CI failure expectations.
Useful intake data includes finding kinds, aggregate counts, redacted policy YAML, redacted workflow YAML, command names, exit codes, artifact filenames, and sanitized report snippets. Do not request private source code, proprietary specs, secrets, tokens, customer data, internal URLs, or full logs containing secrets.
Triage Notes
Use comments on this issue to keep a concise running summary:
- links to feedback issues;
- preview user or repo shape in sanitized terms;
- whether the first report was understandable;
- whether the signal affected review or merge behavior;
- policy tuning friction;
- false-positive or noise themes;
- no-source-upload adoption signal;
- demand for multi-PR history, dashboard, GitHub App behavior, or PR comment opt-in.
Boundaries And Hard Stops
This hub may coordinate feedback and record decision evidence only. It must not perform or authorize:
- repository file changes;
- PRs, releases, stable Action tags, or Marketplace publication;
- SaaS upload, hosted dashboard, billing, auth, or server-side source analysis;
- GitHub App work;
- PR comment automation or
pull-requests: write behavior;
- JUnit/SARIF Action work;
- bundled Action work;
- automatic baseline retrieval from Git, GitHub metadata, workflow history, caches, network, environment, or clock state;
- collection of private source files, proprietary specs, secrets, customer data, or complete logs containing secrets.
The preview boundary remains local-first CLI orchestration:
scan -> check -> optional diff -> report --format markdown
Exit Criteria
PREVIEW-3 can close when real preview evidence has been collected and summarized enough to support an explicit next decision. At minimum, the closing summary should include:
- linked feedback issues or a clear statement that no real feedback was received;
- recurring setup, report, policy, or noise themes;
- whether no-source-upload mattered for adoption;
- whether feedback supports staying with workflow artifacts/job summary only;
- whether feedback justifies opening scoped follow-up work for CLI/report/policy docs, GHA-4 PR comment opt-in, GHA-5 JUnit/SARIF exposure, SaaS-lite exploration, GitHub App exploration, or stopping the preview path.
Decision Outcomes
Expected outcomes are decisions, not automatic implementation:
- continue the local-first GitHub Action preview with documentation fixes only;
- open traceable CLI/report/policy improvement tasks in the main repo;
- open a dedicated decision issue/ADR path for GHA-4 PR comment opt-in;
- open a dedicated decision issue/ADR path for GHA-5 JUnit/SARIF Action exposure;
- defer or reject SaaS-lite / dashboard / GitHub App work;
- continue preview feedback collection with revised intake guidance;
- close the preview path if feedback does not support further investment.
Goal
Collect real self-serve feedback for the audited AnchorMap preview and make the results actionable without expanding product scope prematurely.
This issue is the operational hub for PREVIEW-3. It should link, summarize, and triage feedback from real preview runs by early preview users. It should not invent feedback, simulate adoption, or treat demo evidence as user feedback.
Current Preview Inputs
fstepho/anchormap-action@v0-preview.3anchormap@1.2.2docs/github-action.mddocs/design-partner-preview.mddocs/github-action-demo.mddocs/github-action-pr-preview-plan.mdfstepho/anchormap-h3-demoExpected Feedback Channels
Ask preview users to open the most specific issue template and share only sanitized material:
Useful intake data includes finding kinds, aggregate counts, redacted policy YAML, redacted workflow YAML, command names, exit codes, artifact filenames, and sanitized report snippets. Do not request private source code, proprietary specs, secrets, tokens, customer data, internal URLs, or full logs containing secrets.
Triage Notes
Use comments on this issue to keep a concise running summary:
Boundaries And Hard Stops
This hub may coordinate feedback and record decision evidence only. It must not perform or authorize:
pull-requests: writebehavior;The preview boundary remains local-first CLI orchestration:
Exit Criteria
PREVIEW-3 can close when real preview evidence has been collected and summarized enough to support an explicit next decision. At minimum, the closing summary should include:
Decision Outcomes
Expected outcomes are decisions, not automatic implementation: