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 #283 and GitLab closes the issue. A mention or an updated timestamp is not completion. Awarded points appear in Activity.

Description

UxS components already carry weight_g and spec_json, and import helpers exist. Add an offline quality report that makes ambiguous source units visible before anyone proposes an import.

Who might enjoy this

  • Community interests: sUAS / Drones, Hardware / fabrication, Research
  • Skills: python, data
  • Experience: intermediate; work style: analytical.
  • Readiness: ready; bounty size: M (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

  • A read-only Python CLI over an explicitly selected synthetic JSON component export.
  • A small declared allowlist of mass/voltage/capacity units and a machine-readable report separating valid, convertible, missing and ambiguous values.

Dependencies and decisions

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

Acceptance criteria

  • [ ] Fixtures demonstrate equivalent g/kg values produce the same proposed weight_g while leaving the source file byte-identical.
  • [ ] Unknown unit strings, contradictory structured/free-text values and null values remain review-needed instead of receiving guessed values.
  • [ ] The CLI has no DB/network options; regression fixtures assert expected record IDs and reasons, including an empty input.
  • [ ] 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:

Audit a checked-in synthetic component catalog locally and review the proposed unit conversions as a JSON report.

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 canonical catalog writes, scraping, compliance decisions or general BOM CSV exporter; #213, #214 and #238 keep those scopes.
  • Do not infer electrical compatibility, airworthiness or actual device performance.
  • 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:uxs-spec-unit-audit -->

Relevant files

Hints

No hints yet.

Activity

  • +100 Hugo Zarate earned M bounty 6h ago

Comments

No comments yet. Be the first to weigh in.

↑ Top