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

Description

Post.source_url and the article Original Source link already exist, but the reviewed member submit form/INSERT do not expose or save that field. Close this provenance gap using the existing column and helpers.

Who might enjoy this

  • Community interests: Research, Warfare studies, Professional development
  • Skills: frontend, backend
  • Experience: intermediate; work style: visual.
  • 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

  • An optional original-source URL field on member create/edit paths with a clear separate label from the article URL.
  • Shared safeHttpUrl validation and consistent persisted readback through the existing article access path; edits still use the existing review/version rules.

Dependencies and decisions

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

Acceptance criteria

  • [ ] Router/local-D1 create and edit tests save an HTTPS source, clear it intentionally, and reject a javascript: source without losing the prior valid value.
  • [ ] An authorized reader sees exactly one safely escaped Original Source link; draft/private posts retain current access restrictions.
  • [ ] Run Field Notes existing checks and capture before/after local editor/read-view evidence.
  • [ ] 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:

Create a synthetic research draft citing https://example.test/paper, save it, then follow its separate Original Source control.

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 source scraping, automatic imports, bibliography engine, URL fetching or additional provenance database.
  • 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:fieldnotes-original-source-form -->

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