Last checked with GitLab: . Status comes from GitLab using a 2-minute cache. Merge events clear affected cached statuses. An already-open page does not update itself. Refresh page.

An MR completes this bounty when it is merged into main with Closes #285 and GitLab closes the issue. A mention or an updated timestamp is not completion. Awarded points appear in Activity.

Submit a merge request that closes this issue to earn points on merge — bounties stack on the standard +40 merge_pr award. New to the repo? See the Contributing guide, and Local Development & SSO to run the app locally (cp .dev.vars.example .dev.vars && pnpm dev, after rebasing on main) and fully test your change before opening the MR.

Description

Field Notes already has a Markdown draft editor. Add one opt-in starter outline so hobbyists can publish useful bench observations with setup, units, uncertainty and reproducible evidence.

Who might enjoy this

  • Community interests: sUAS / Drones, RF / SDR (Dragon), Hardware / fabrication, Research
  • Skills: frontend, docs, ux
  • Experience: starter; work style: visual.
  • Readiness: ready; bounty size: S (existing points tier; standard merge award stacks separately).

Current behavior and starting points

Source-reviewed against main cf05b29c6256dba70d0ebc09b22cc9867cdb786a on2026-10-18. Check current main and related issues/MRs before implementing so existing work is reused.

Relevant Files

Deliverables

  • One bench-report preset reachable from the existing submit editor, inserting editable Markdown only on explicit selection.
  • Original fictional example covering instrument/software version, synthetic sample, procedure, observations, limits and source/license.

Dependencies and decisions

No prerequisite issue is required. Re-read current main and linked MRs before starting.

Acceptance criteria

  • [ ] Through the authenticated submit route, select the preset and confirm every field remains editable and previewed by the existing Markdown path.
  • [ ] Existing draft text is preserved unless the author explicitly accepts a visible replacement confirmation; loading the editor never inserts or publishes text.
  • [ ] Save/reopen the draft and verify the same content and ordinary visibility/review rules; canceling selection has no effect.
  • [ ] Record named baseline failures and the exact commands used. A behavior fix includes a real route/database/protocol check observed failing before the change. Knowledge work includes source traceability and reproducible reviewer evidence.
  • [ ] Run the affected app's existing checks. Explain any baseline failures rather than reporting a matching failure count as proof.

Try it locally

Start from the existing source files above. The following is the target demo your contribution should enable; a newly proposed script or fixture is part of the deliverable:

In a local synthetic account, choose Bench report in the existing draft editor and replace the example measurement; save a draft only.

Use public or synthetic examples. Starter work should run without production access; explicitly name any software/device prerequisite before claiming it is ready.

Out of scope

  • No automatic publication, AI generation, new review policy, telemetry or bench-device access.
  • No general-purpose template marketplace or changes to library/review features owned by other stories.
  • Unrelated refactors, new services/providers, bulk dependency changes, production access changes, unrequested notifications, and copying private member material. Keep credentials and unresolved security findings outside the issue and repository.

For a coding agent and reviewer

Read AGENTS.md, applicable .cursor/rules/, app instructions and docs/contributing/agentic-bounty-review.md. Reuse the existing shared helpers, identity/access paths and app styling. Implement one bounded story and provide evidence the accepting app maintainer can reproduce. State updated / pre-release verified / released / live verified accurately.

A parent index carries no duplicate award for these child deliverables. Open one scoped MR using this issue's actual number after the closing keyword. Link your GitLab identity on Scoreboard; the existing merge webhook handles eligible points.

Catalog index: #258.

<!-- community-interest-bounty:2026-10-18:bench-report-draft-preset -->

Relevant files

Hints

No hints yet.

Activity

No points have been awarded for this bounty yet.

Comments

No comments yet. Be the first to weigh in.

↑ Top