P1.5: voluntary feedback path (testbed)#14
Open
MrBinnacle wants to merge 1 commit into
Open
Conversation
Per launch board P1.5 decision (mailto: mlpgruber@gmail.com locked). Adds the inbound channel for feedback and questions across three surfaces. Changes - .github/ISSUE_TEMPLATE/feedback.yml — new issue template for questions / observations / requests that aren't bug reports. The existing bug_report.yml stays untouched. Lifts mlpgruber@gmail.com inline as a direct-email alternative. - README.md — new "Feedback or questions" section before License, links the bug template, the feedback template, and the mailto:. - testbed/App.jsx orientation banner "What next" card — adds a Feedback-or-questions line with the issue link + mailto. The placeholder line referencing P1.5 is gone; the P1.2 (article) placeholder remains and will resolve when the article URL lands. Why surface the mailto: alongside the issue template - Evaluator-class operators expect a direct-reach channel; many won't file a GitHub issue for a one-line note. The mailto: is the lower-friction path that turns "interesting" into a call. - The issue template is the higher-friction path that produces a durable artifact for things worth keeping. Verified - npm run build -> green (192.83 KB bundle) - feedback.yml validates as standard GitHub issue-form schema (name, description, body with type/id/attributes/validations) - mailto: link is mlpgruber@gmail.com per locked decision Do not merge until - Cold-read of the deploy preview confirms the new feedback line renders inside the orientation banner card without breaking the responsive grid. - Matthew approves. Merge + manual netlify deploy --prod ships to production. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Owner
Author
|
Held pending Substack article publish. Disposition will be revisited after the launch sequence completes — voluntary feedback path is a nice-to-have on publish day, not blocking. Not abandoned. |
MrBinnacle
added a commit
that referenced
this pull request
Jun 5, 2026
- .gitignore: add .day1-state.json, graphify-out/, drafts/ (paste-and-ship surfaces, not versioned product) - ci.yml: add weekly Monday 12:00 UTC cron trigger so npm audit runs against the locked deps without waiting for a push. Closes the false-negative trap where commit 58332db flipped CI red because a Critical vitest alert was published between pushes and the audit step only fires on push by default. Session-close housekeeping companions (no source changes, not in this commit): - Filed issue #19 (React 19 + plugin-react 6 + Vite 8 coordinated trio merge) - Filed issue #20 (CI Node 20 → 22 bump before 2026-06-16) - Closed PRs #1, #2, #4, #5 with @dependabot ignore-major directives + cross-ref to umbrella issue #19 - Posted held-pending-Substack-publish disposition on PRs #13, #14 Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds the inbound channel for feedback / questions across three surfaces. Per launch board P1.5 decision (`mailto: mlpgruber@gmail.com` locked).
Each surface offers both a low-friction email path (`mlpgruber@gmail.com`) and a durable issue path.
Why two paths
Preview
https://deploy-preview-p15--azimuth-testbed.netlify.app
Cold-read in deployed bundle:
Verified
Do not merge until
🤖 Generated with Claude Code