Corrected this session — the mechanism this relied on no longer exists. Logs stopped using addnewpage/{{NEWPAGE}} entirely this session (03-templates/logs/README.md's new section): each level now has one persistent, reusable form page instead of a fresh page created per entry, so there's no longer a page-creation URL to build a button around here at all — and even before that change, the relative path below this line was itself miscounted (two ..: segments, landing at projects:logs:... instead of the intended top-level logs:... — moot now, replaced rather than fixed in place).

The corrected link goes to the student's own dashboard, where the one log-start link matching their actual level already lives (06-buttons/student-dashboard.txt):

📋 Go to your dashboard to start today's log

The student still picks this project manually from the struct Page-type picker on the log form once there — that choice was already decided as deliberately two-step, reasoning unchanged from before this correction (see below).

Decided: two-step, not one-click. A genuine one-click mechanism exists (bureaucracy's _handlePreload(), reading a GET param named @log_entry_project@) but wiring it up needs a custom HTML/JS block per project page — several new, untested assumptions stacked at once. Weighed against that: one extra manual selection on the log form, zero new risk. Chosen deliberately — not a placeholder awaiting a better fix. If a one-click experience becomes worth the complexity later, @log_entry_project@ is the confirmed starting point — not addnewpage's own query string, which was tested and conclusively does not carry arbitrary params through.