Require labeled proposal sections (issue #10) #22
Loading…
Reference in a new issue
No description provided.
Delete branch "10-feat-voting-structured-proposal-template-and-minimum-required-sections"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
problem, optionalcontext,solution,pros_cons,summary,success_criteria) so voters can scan TL;DR, trade-offs, and goalposts before signing.body_hashis SHA-256 of canonical JSON (sorted keys, ammonia-cleaned HTML per section). New creates reject freeformbody_html. Legacy rows still render viabody_html.Related to #10. Do not close #10 until staging Terra and BSC compose is verified. Draft/review lifecycle remains #13.
Test plan
cargo test --workspace --lib(section validation + golden hash85b0e398…)LEDGER_TEST_DATABASE_URL=… cargo test --workspace --tests(Terra/BSC create, empty sections, hash mismatch, XSS, legacy GET)cd frontend && npm test(gates, golden JSON, list text TL;DR, legacy fallback)cd frontend && npm run test:e2e -- --workers=5(template compose → detail headings → list TL;DR)GET /v1/proposalsincludessummaryon live operator API after migratemarked this merge request as ready
changed the description
Closed: this MR targeted the empty issue auto-branch at main. Replacement comes from feat/10-proposal-template.
Pull request closed