Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Changelog

## 1.7.2 (Prepared August 3, 2026)
## 1.7.2 (Submitted August 3, 2026)

- Added Add Content mode for anchoring proposed text, image placeholders, lists, and safe HTML/embed-frame placeholders to existing page elements.
- Added reversible before, after, inside-start, and inside-end previews with explicit filler, support intent, and acceptance checks.
Expand Down
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

Pick and annotate browser elements or regions, propose new content blocks, then copy AI-ready prompts or export local visual change specs for Codex, Claude Code, Cursor, or another developer. Dev Feedback Capture supports four evidence-rich workflows:

> [Chrome Web Store v1.7 is public](https://chromewebstore.google.com/detail/dev-feedback-capture/hhdmfaaplpiokafjieefpgoppckijafc). This source checkout prepares the v1.7.2 Add Content update; the latest GitHub Release ZIP remains v1.2.0 as a manual fallback.
> [Chrome Web Store v1.7 is public](https://chromewebstore.google.com/detail/dev-feedback-capture/hhdmfaaplpiokafjieefpgoppckijafc). The v1.7.2 Add Content update is pending Google review and will publish automatically after approval; the latest GitHub Release ZIP remains v1.2.0 as a manual fallback.

- `Element` mode injects a lightweight in-page UI so you can click DOM elements and save selectors, styles, and notes.
- `Visual` mode lets you directly drag and resize one live DOM element, records original versus proposed intent, and restores the page after Save or Cancel.
Expand Down
14 changes: 7 additions & 7 deletions docs/chrome-web-store-submission-draft.md
Original file line number Diff line number Diff line change
@@ -1,13 +1,13 @@
# Chrome Web Store Submission Record

Status: v1.7.0 is public in the Chrome Web Store. The exact v1.7.1 discovery package was submitted for normal review on August 3, 2026, and v1.7.2 is now the prepared Add Content replacement candidate. Replacing the active submission requires an explicit cancel, upload, publish, and API readback sequence. Google distributes the Browser Code icon inside the public v1.7 CRX, but the Store listing still rendered the retired purple-flag asset before these submissions.
Status: v1.7.0 is public in the Chrome Web Store. The v1.7.1 review was cancelled and replaced by the exact v1.7.2 Add Content package on August 3, 2026. Google accepted v1.7.2 for normal review with no warnings; it is pending review at a 100% target and will publish automatically after approval. Google distributes the Browser Code icon inside the public v1.7 CRX, but the Store listing still rendered the retired purple-flag asset before these submissions.

The next package is v1.7.2. It adds the user-triggered Add Content workflow plus the v1.7.1 discovery metadata and refreshed icon encoding without adding permissions, remote code, or network services. Keep the separate v1.8 Feedback Session work out of this package. The existing Store approval and automated checks do not prove the deferred browser runtime gates in `docs/manual-release-checklist.md`.
The submitted v1.7.2 package adds the user-triggered Add Content workflow plus the v1.7.1 discovery metadata and refreshed icon encoding without adding permissions, remote code, or network services. It excludes the separate v1.8 Feedback Session work. Store acceptance and automated checks do not prove the deferred browser runtime gates in `docs/manual-release-checklist.md`.

## Ready inputs

- Publisher: `FlyingChanges Code`
- Candidate extension package: `dist/dev-feedback-capture-v1.7.2.zip`
- Submitted extension package: `dist/dev-feedback-capture-v1.7.2.zip`
- Store icon: `icon128.png` (`128x128` PNG)
- Public product page: `https://monroes.tech/software/dev-feedback-capture/`
- Privacy policy: `https://monroes.tech/software/dev-feedback-capture/privacy/`
Expand Down Expand Up @@ -167,14 +167,14 @@ Target: 75-90 seconds, `1920x1080`, recorded in a clean Edge window on the publi
- Publisher: `FlyingChanges Code`; durable owner and verified public contact: `monroe@flyingchangesfarm.net`.
- Store item ID: `hhdmfaaplpiokafjieefpgoppckijafc`.
- Current public package: v1.7.0.
- Submitted package: `dist/dev-feedback-capture-v1.7.1.zip`; SHA-256 `440b41157386ae75e42a15e0f7f12c9bcbe645966e57330ec97f55fdb61a1dc3`.
- API readback on August 3, 2026: v1.7.1 is `PENDING_REVIEW` at a 100% target with no warning or takedown flag.
- Replacement candidate: `dist/dev-feedback-capture-v1.7.2.zip`; final SHA-256 and API state must be recorded after the release package is built and submitted.
- Cancelled submission: `dist/dev-feedback-capture-v1.7.1.zip`; SHA-256 `440b41157386ae75e42a15e0f7f12c9bcbe645966e57330ec97f55fdb61a1dc3`.
- Submitted package: `dist/dev-feedback-capture-v1.7.2.zip`; SHA-256 `4c40215036eef05f5459f408d8e11ed74327db39d16892a78a14345e95f65bef`.
- API readback on August 3, 2026: v1.7.2 is `PENDING_REVIEW` at a 100% target with no warning or takedown flag; v1.7.0 remains public until approval.
- Category: Developer Tools; language: English (United States).
- The single purpose, permission justifications, no-remote-code declaration, data-use categories, privacy-policy URL, homepage, and support URL were saved before submission.
- One valid 1280x800 screenshot remains on the Store listing. Monroe explicitly waived replacement screenshots for this submission; the fresh five-shot set remains optional follow-up work.
- Monitor the verified contact email and dashboard for approval or a focused reviewer request.
- Confirm the dashboard's publication timing choice before an approved item goes live; that setting was not independently recorded here.
- Monroe explicitly authorized the v1.7.1 upload without a new unpacked-browser smoke or replacement screenshots. Those checks remain open and the release must not be described as runtime-verified.
- Monroe explicitly authorized the v1.7.2 upload without a new unpacked-browser smoke or replacement screenshots. Those checks remain open and the release must not be described as runtime-verified.
- The feature video, 440x280 promotional tile, and backup publisher Admin remain optional follow-up work.
- Keep payments, authentication, network sync, additional permissions, and v1.8 Feedback Sessions out of v1.7.2.
4 changes: 3 additions & 1 deletion docs/manual-release-checklist.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,10 +2,12 @@

Automated checks are necessary but do not replace the unpacked-extension gate.

Store status on August 3, 2026: v1.7.0 is public in the Chrome Web Store, v1.7.1 is pending review, and v1.7.2 is the prepared Add Content replacement. The distributed CRX contains the Browser Code icon, while the Store listing still renders the retired purple-flag artwork. Store approval is not proof that the deferred checks below passed. Keep them open and do not call these releases runtime-verified until the relevant evidence is recorded.
Store status on August 3, 2026: v1.7.0 is public in the Chrome Web Store, v1.7.1 was cancelled, and v1.7.2 is pending review for automatic publication. The distributed CRX contains the Browser Code icon, while the Store listing still renders the retired purple-flag artwork. Store approval is not proof that the deferred checks below passed. Keep them open and do not call these releases runtime-verified until the relevant evidence is recorded.

Submission record: Monroe explicitly waived the new unpacked-browser smoke and replacement screenshot gates. The exact v1.7.1 ZIP with SHA-256 `440b41157386ae75e42a15e0f7f12c9bcbe645966e57330ec97f55fdb61a1dc3` was uploaded successfully and submitted for normal review on August 3, 2026. The API readback showed `PENDING_REVIEW` at a 100% target with no warning or takedown flag. The unchecked runtime and screenshot items below remain open proof gaps, not blockers to that authorized submission.

v1.7.2 submission record: The v1.7.1 review was cancelled, and the exact clean-main v1.7.2 ZIP with SHA-256 `4c40215036eef05f5459f408d8e11ed74327db39d16892a78a14345e95f65bef` was uploaded and submitted for normal review on August 3, 2026. API readback showed v1.7.2 `PENDING_REVIEW` at a 100% target with no warning or takedown flag. v1.7.0 remains public until Google approves and automatically publishes v1.7.2.

## v1.7.2 Add Content package and submission

Before submitting v1.7.2:
Expand Down
4 changes: 2 additions & 2 deletions product.json
Original file line number Diff line number Diff line change
Expand Up @@ -26,8 +26,8 @@
"summary": "Feedback stays in local extension storage or an explicitly selected project sidecar. Capture, export, and MCP import actions are user-triggered, and no cloud sync or hosted AI integration is included."
},
"distribution": {
"current": "Chrome Web Store v1.7.0 is public, v1.7.1 is pending review, and v1.7.2 is the prepared Add Content update. GitHub Release v1.2.0 remains available for manual unpacked installation.",
"planned": "Replace the pending v1.7.1 submission with v1.7.2, then verify the public version, revised listing metadata, icon, and Add Content workflow after review; keep v1.8 Feedback Sessions in a separate gated release lane.",
"current": "Chrome Web Store v1.7.0 is public, v1.7.1 was cancelled, and v1.7.2 is pending review for automatic publication. GitHub Release v1.2.0 remains available for manual unpacked installation.",
"planned": "Monitor the v1.7.2 review, then verify the public version, revised listing metadata, icon, and Add Content workflow after publication; keep v1.8 Feedback Sessions in a separate gated release lane.",
"latestReleaseApi": "https://api.github.com/repos/StoneHub/webDevFeedbackExt/releases/latest",
"assetNamePattern": "dev-feedback-capture-v{version}.zip",
"downloadUrlPolicy": "Resolve the latest release asset at publish time instead of hardcoding a stale versioned URL."
Expand Down
Loading