-
Testing self-approval — Railspike debug log
No supported findings.
docs/plans/testing_self_approval/testing_self_approval_debug_log.md Plans Plans and history
-
testing_self_approval_step1_solution_assessment.md
As a maintainer who often runs new temporary localhost instances, I want an easy, one-click, "approve current account" button that I can use only during testin…
docs/plans/testing_self_approval/testing_self_approval_step1_solution_assessment.md Plans Plans and history
-
testing_self_approval_step2_feature_description.md
Maintainers repeatedly need to approve their browser account on temporary localhost instances.
docs/plans/testing_self_approval/testing_self_approval_step2_feature_description.md Plans Plans and history
-
testing_self_approval_step3_development_plan.md
Deliver the approved marker-gated Account Key action: create ignored .test-self-approval, start localhost normally, authenticate the browser account, click onc…
docs/plans/testing_self_approval/testing_self_approval_step3_development_plan.md Plans Plans and history
-
testing_self_approval_step4_implementation_summary.md
docs/plans/testing_self_approval/testing_self_approval_step4_implementation_summary.md Plans Plans and history
-
test_runner_elapsed_time_step1_solution_assessment.md
I want the test runner to output the elapsed time with each line so that it's easier for me to track, please.
docs/plans/test_runner_elapsed_time/test_runner_elapsed_time_step1_solution_assessment.md Plans Plans and history
-
test_runner_elapsed_time_step2_feature_description.md
Test results currently show no timing until the later slow-test report, making it difficult to follow overall progress or identify the cost of each completed t…
docs/plans/test_runner_elapsed_time/test_runner_elapsed_time_step2_feature_description.md Plans Plans and history
-
test_runner_elapsed_time_step3_development_plan.md
docs/plans/test_runner_elapsed_time/test_runner_elapsed_time_step3_development_plan.md Plans Plans and history
-
test_runner_elapsed_time_step4_implementation_summary.md
docs/plans/test_runner_elapsed_time/test_runner_elapsed_time_step4_implementation_summary.md Plans Plans and history
-
Test run history retention
log table) and retention size (X runs / Y days / both)
docs/plans/test_run_history_retention_plan_v1.md Plans Plans and history
-
Step 1: Solution Assessment — Test Run Summary Report
tests/run.php currently prints per-test PASS/FAIL lines and a slow-test report, but gives no run summary (pass/fail counts) and no way to tell which failures a…
docs/plans/test_run_summary_report/test_run_summary_report_step1_solution_assessment.md Plans Plans and history
-
Step 2: Feature Description — Test Run Summary Report
tests/run.php prints per-test PASS/FAIL lines and a slow-test list, but no run summary — you can't see totals at a glance, or whether a failure is new or has b…
docs/plans/test_run_summary_report/test_run_summary_report_step2_feature_description.md Plans Plans and history
-
Step 3: Development Plan — Test Run Summary Report
docs/plans/test_run_summary_report/test_run_summary_report_step3_development_plan.md Plans Plans and history
-
Step 4: Implementation Summary — Test Run Summary Report
docs/plans/test_run_summary_report/test_run_summary_report_step4_implementation_summary.md Plans Plans and history
-
Text backup start latency — Railspike diagnostics
Debug mode: enabled; inherited from project marker for this new cycle
docs/plans/text_backup_start_latency_debug_log.md Plans Plans and history
-
text_backup_start_latency_step1_solution_assessment.md
Effort study: railspike-effort / v3/textbackupstartlatency; ledger; standing P2 enrollment
docs/plans/text_backup_start_latency_step1_solution_assessment.md Plans Plans and history
-
Thread List Card: Duplicate Preview Line — Step 1 Solution Assessment
On the board/tag listing pages, each thread's preview line is literally the body's first line (strtok($body, "\n")), so it repeats the title whenever a poster'…
docs/plans/thread_card_remove_preview/thread_card_remove_preview_step1_solution_assessment.md Plans Plans and history
-
Step 2: Feature Description — Omit Duplicate Preview Line from Thread List Card
On the board and tag listing pages, each thread's preview line is the body's first line, so it repeats the title whenever a poster's first body line matches th…
docs/plans/thread_card_remove_preview/thread_card_remove_preview_step2_feature_description.md Plans Plans and history
-
Step 3: Development Plan — Omit Duplicate Preview Line from Thread List Card
Reply Approved Step 3 to create the feature branch and begin Step 4.
docs/plans/thread_card_remove_preview/thread_card_remove_preview_step3_development_plan.md Plans Plans and history
-
Step 4: Implementation Summary — Omit Duplicate Preview Line from Thread List Card
docs/plans/thread_card_remove_preview/thread_card_remove_preview_step4_implementation_summary.md Plans Plans and history
-
Compact view for thread listings
Users currently see thread lists (board/tag pages) as full cards: title, meta line, full body-preview text, and reply count, with generous spacing between card…
docs/plans/thread_compact_view/thread_compact_view_plan_v1.md Plans Plans and history
-
Thread Compact View Step 3 Development Plan
Plus toggle-button styling consistent with .theme-toggle.
docs/plans/thread_compact_view/thread_compact_view_step3_development_plan.md Plans Plans and history
-
Addendum: Move the merged-run byline to the last post, not the first
Follows on from the original continuation-merge feature docs:
docs/plans/thread_continuation_merge/thread_continuation_merge_meta_position_addendum_v1.md Plans Plans and history
-
Step 1: Solution Assessment — Merge Same-Author Reply Chains on Thread Pages
Quick same-author replies within a short window each render as a full, separately-bordered post-card with repeated byline/actions, so one continuous piece of w…
docs/plans/thread_continuation_merge/thread_continuation_merge_step1_solution_assessment.md Plans Plans and history
-
Step 2: Feature Description — Merge Same-Author Reply Chains on Thread Pages
On thread pages, a burst of quick same-author replies each renders as its own full card (repeated byline, repeated action row), so one continuous piece of writ…
docs/plans/thread_continuation_merge/thread_continuation_merge_step2_feature_description.md Plans Plans and history
-
Step 3: Development Plan — Merge Same-Author Reply Chains on Thread Pages
docs/plans/thread_continuation_merge/thread_continuation_merge_step3_development_plan.md Plans Plans and history
-
Step 4: Implementation Summary — Merge Same-Author Reply Chains on Thread Pages
docs/plans/thread_continuation_merge/thread_continuation_merge_step4_implementation_summary.md Plans Plans and history
-
Thread Inline Reply Form Plan V1
Add a compact reply composer directly on thread pages so a reader can start replying without leaving the thread.
docs/plans/thread_inline_reply_form_plan_v1.md Plans Plans and history
-
Thread-like Activity — Railspike debug log
No supported findings.
docs/plans/thread_like_activity/thread_like_activity_debug_log.md Plans Plans and history
-
thread_like_activity_step1_solution_assessment.md
Effort study: railspike-effort, cycle v3/threadlikeactivity; standing P2 enrollment; ledger.
docs/plans/thread_like_activity/thread_like_activity_step1_solution_assessment.md Plans Plans and history
-
thread_like_activity_step2_feature_description.md
Effort study: railspike-effort, cycle v3/threadlikeactivity; standing P2 enrollment; ledger.
docs/plans/thread_like_activity/thread_like_activity_step2_feature_description.md Plans Plans and history
-
thread_like_activity_step3_development_plan.md
Effort study: railspike-effort, cycle v3/threadlikeactivity; ledger.
docs/plans/thread_like_activity/thread_like_activity_step3_development_plan.md Plans Plans and history
-
thread_like_activity_step4_implementation_summary.md
Effort study: railspike-effort, v3/threadlikeactivity; ledger.
docs/plans/thread_like_activity/thread_like_activity_step4_implementation_summary.md Plans Plans and history
-
Thread Root Card Consolidation Plan v1
The thread page currently renders two adjacent cards for the root post:
docs/plans/thread_root_card_consolidation_plan_v1.md Plans Plans and history
-
Thread Root Card: Omit Duplicate Title Line — Step 1 Solution Assessment
When a thread's title matches the first line of its root post body, the thread page shows that line twice — once as the <h1> and again as the first line of the…
docs/plans/thread_root_card_dedupe_title_first_line/thread_root_card_dedupe_title_first_line_step1_solution_assessment.md Plans Plans and history
-
Step 2: Feature Description — Omit Duplicate Title Line from Thread Root Card
When a thread's title is identical to the first line of its root post body, the thread page shows that line twice: once as the <h1> title and again as the firs…
docs/plans/thread_root_card_dedupe_title_first_line/thread_root_card_dedupe_title_first_line_step2_feature_description.md Plans Plans and history
-
Step 3: Development Plan — Omit Duplicate Title Line from Thread Root Card
Reply Approved Step 3 to create the feature branch and begin Step 4.
docs/plans/thread_root_card_dedupe_title_first_line/thread_root_card_dedupe_title_first_line_step3_development_plan.md Plans Plans and history
-
Step 4: Implementation Summary — Omit Duplicate Title Line from Thread Root Card
docs/plans/thread_root_card_dedupe_title_first_line/thread_root_card_dedupe_title_first_line_step4_implementation_summary.md Plans Plans and history
-
Step 2: Feature Description — Thread Root Card Meta Reorder
On the thread page, the root post's byline, labels, and reply count sit between the title and the body, pushing the body away from the title it belongs to and…
docs/plans/thread_root_card_meta_reorder/thread_root_card_meta_reorder_step2_feature_description.md Plans Plans and history
-
Step 3: Development Plan — Thread Root Card Meta Reorder
Reply Approved Step 3 to create the feature branch and begin Step 4.
docs/plans/thread_root_card_meta_reorder/thread_root_card_meta_reorder_step3_development_plan.md Plans Plans and history