Fixed-scope browser extension patch sprint

Fake Filler Auto-Submit Sprint

A $100 prepared implementation package for the open Fake Filler request asking for an auto-submit option after form filling. The patch is local; no upstream comment, email, PR, or patch delivery has been sent.

Scope Evidence Claim steps Acceptance text Draft response Prepared notes Patch CSV Payment activation

Patch size5568 bytes

Primary sprint price$100

Confirmed money$0

Concrete Deliverable

Add a disabled-by-default autoSubmitAfterFill option.
Add a General Settings checkbox labelled "Automatically submit after filling a form".
Persist the setting through the existing Redux/settings flow.
Submit after Fill this form when enabled.
Submit after Fill all inputs only when the page has exactly one form.
Use requestSubmit() when available, with a cancelable submit-event fallback.

Implementation Evidence

File	Prepared change
src/types.ts	Adds `autoSubmitAfterFill` to option types.
src/common/helpers.ts	Defaults the setting to `false`.
src/options/actions.ts	Saves the setting from the options form.
GeneralSettingsForm.tsx	Adds the settings checkbox.
src/common/fake-filler.ts	Adds bounded submit behavior.
messages.json	Adds English locale strings.

Verification note

# Fake Filler Auto-Submit Patch Notes

Generated: 2026-06-27 22:33:45 JST

## Lead

- Source issue: https://github.com/FakeFiller/fake-filler-extension/issues/151
- Source repo: https://github.com/FakeFiller/fake-filler-extension
- Issue state checked: open, no comments
- Buyer signal: issue author asked for an auto-submit option and wrote that they were happy to pay someone for the feature.
- License checked via GitHub metadata and repository `LICENSE`: MIT.

## Local Checkout

- Checkout: `/Users/jax/autonomous_earning_run_2026-06-09/non_bounty/fake-filler-extension`
- Base commit: `36daf90 Update changelog and version`
- Patch file: `/Users/jax/autonomous_earning_run_2026-06-09/non_bounty/fakefiller_auto_submit.patch`

## Implementation

- Added `autoSubmitAfterFill` to `IFakeFillerOptions` and `IFakeFillerOptionsForm`.
- Defaulted the setting to `false`.
- Added a General Settings checkbox: "Automatically submit after filling a form".
- Saved the option through the existing Redux/settings flow.
- Implemented bounded submit behavior in `FakeFiller`:
- `Fill this form` submits the matched form after filling when enabled.
- `Fill all inputs` submits only when the page has exactly one form.
- `Fill this input` does not auto-submit.
- Uses `form.requestSubmit()` when available, falling back to a cancelable `submit` event and `form.submit()`.

## Verification

- `git diff --stat`: 45 inserted lines across 6 files.
- `git -c core.whitespace=blank-at-eol,blank-at-eof,space-before-tab,cr-at-eol diff --check`: passed.
- `public/_locales/en/messages.json` JSON parse: passed.
- `npm ci`: blocked before install because the upstream `package-lock.json` is out of sync with `package.json`.
- `npm install --package-lock=false --ignore-scripts --no-audit --no-fund`: interrupted after several minutes of no output; no `node_modules` directory was produced.
- Direct `tsc` invocation: only reached dependency-resolution checks and reported missing project dependencies/globals because dependencies were not installed.

## Money Boundary

Confirmed money remains `$0`. This is a prepared MIT-licensed patch packet only. It should not be counted as earned unless the issue requester, maintainer, marketplace, or payment provider produces external acceptance/payment proof.

## Next Action To Claim

1. Review the patch file and the source issue.
2. Decide whether to publish it upstream as a PR/comment or keep it as a paid handoff packet.
3. If pursuing payment, use a seller-owned payment route and require explicit fixed-scope acceptance before delivery.
4. If publishing unpaid, do not count money unless payment proof arrives later.

Exact Claim Steps

Open the source issue and confirm it is still open.
Review the public patch and prepared notes.
Add only your seller-owned checkout, invoice, marketplace order, funded milestone, or payment-request URL.
Use the draft response only after you approve it.
Require the exact acceptance sentence before payment.
Deliver the patch only after external payment proof or after you explicitly decide to publish it unpaid.
Capture proof: accepted scope, payment reference, amount, fees, hold/refund state, delivery URL or PR URL, buyer/platform acceptance if required, payout/payable/cleared status, and date.
Count $0 until the external proof shows posted, released, payable, cleared, credited, or verified net money.

Exact Acceptance Before Payment

I accept the Fake Filler Auto-Submit Sprint fixed-scope terms at $100. I understand work starts only after seller-owned external payment proof exists; I will provide only public or buyer-authorized non-sensitive requirements; the deliverable is limited to the prepared disabled-by-default auto-submit option, settings UI, saved option wiring, bounded submit behavior, apply notes, and verification notes; and production form testing, private browser/account data, store publication, public posting, pull requests, or ongoing revisions are not included unless separately agreed before payment.

open_paid_feature_request_prepared_patch_packet

Auto submit after filling a form

The source issue says: "Is it possible to add a auto submit option as well where it submits the form after it fills it out? (Happy to pay someone for this feature)"

Draft response not posted

I prepared a small local patch for the auto-submit request. It adds a disabled-by-default General Settings checkbox, persists an `autoSubmitAfterFill` option, and submits after `Fill this form`. For `Fill all inputs`, it submits only when the page has exactly one form, so it avoids guessing on multi-form pages. It uses `requestSubmit()` when available and falls back to a cancelable submit event plus `form.submit()`. I can hand over the patch or adapt it to a branch after fixed-scope acceptance and external payment proof.

Draft response prepared only. External comments, emails, direct messages, pull requests, or patch delivery require explicit send approval.

Money And Posting Boundary

Signal	Counted as money?
Prepared patch, notes, page, CSV, draft response, or IndexNow result	No. Counts $0.
Issue text says happy to pay	No. Requires accepted scope and external payment proof.
External payment posted, released, payable, or cleared after delivery proof	Yes. Count only verified net amount after fees/refunds.