P0-B of the S9 acceptance report: a self-contained duties-flows browser harness (scripts/e2e-duties.sh).
Builds RDM (origin/main archive + pins snapshot), base CLI (same pinned backend), frontend dist; seeds via the current login-key credential contract (identity ensure, dual bootstrap-admin, redeem+set-password).
Drives the three-views duties page in a real browser: granted non-admin preview 200, in-flight doc round + reviewer change surfaces the confirmation checkbox and a confirmed save invalidates the doc submission, idempotent re-save applied=0 unchanged=1, unauthorized member preview 400, void-legacy then doc submit passes.
Scripts-only; no product code or pins change. Formal run recorded in the task card (make evidence).
P0-B of the S9 acceptance report: a self-contained duties-flows browser harness (scripts/e2e-duties.sh).
- Builds RDM (origin/main archive + pins snapshot), base CLI (same pinned backend), frontend dist; seeds via the current login-key credential contract (identity ensure, dual bootstrap-admin, redeem+set-password).
- Drives the three-views duties page in a real browser: granted non-admin preview 200, in-flight doc round + reviewer change surfaces the confirmation checkbox and a confirmed save invalidates the doc submission, idempotent re-save applied=0 unchanged=1, unauthorized member preview 400, void-legacy then doc submit passes.
- Scripts-only; no product code or pins change. Formal run recorded in the task card (make evidence).
Refs: S9 acceptance report P0-B; findings 2/4 retest.
Why: establish the authorized task workspace and its initial baseline.
Evidence: preserved precheck receipt in .task/feature-duty-acceptance-e2e.md; R0=e8d3e61a38e9690763ef46f272b2643604629cc4.
Impact: task metadata only; the feature workspace starts at e8d3e61a38.
Refs: .task/feature-duty-acceptance-e2e.md
Why: the S9 acceptance corrections left no repeatable harness for the
duty-flows browser verification, and the doc-level in-flight confirmation
path had never been driven in a real browser; the legacy e2e.sh seeding
predates the login-key credential contract.
Evidence: bash scripts/e2e-duties.sh end-to-end PASS — granted non-admin
preview 200, in-flight round + reviewer change surfaces the confirmation
checkbox and a confirmed save invalidates the doc submission, idempotent
re-save applied=0 unchanged=1, unauthorized member preview 400,
void-legacy then doc submit passes (evidence row in this card).
Impact: scripts-only; no product code or pins change.
Refs: S9 acceptance report P0-B
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=d295342c4f5654d916c612b9cc059ccd39445d14.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
weichen
merged commit 197155c405 into main2026-10-16 04:34:37 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
P0-B of the S9 acceptance report: a self-contained duties-flows browser harness (scripts/e2e-duties.sh).
Refs: S9 acceptance report P0-B; findings 2/4 retest.