-
startup_dependency_recovery_step4_implementation_summary.md
All five stages implemented and verified on feat/startup-dependency-recovery.
docs/plans/startup_dependency_recovery/startup_dependency_recovery_step4_implementation_summary.md Plans
-
Status frontend target — Railspike debug log
docs/plans/status_frontend_target/status_frontend_target_debug_log.md Plans
-
Status frontend target — Step 1 solution assessment
This test usually fails for one of two reasons:
docs/plans/status_frontend_target/status_frontend_target_step1_solution_assessment.md Plans
-
Status frontend target — Step 2 feature description
Plain ./v3 status can report a healthy frontend as unreachable because it assumes port 8000.
docs/plans/status_frontend_target/status_frontend_target_step2_feature_description.md Plans
-
Status frontend target — Step 3 development plan
docs/plans/status_frontend_target/status_frontend_target_step3_development_plan.md Plans
-
Status frontend target — implementation summary
Planning commit: 1f7e49d1.
docs/plans/status_frontend_target/status_frontend_target_step4_implementation_summary.md Plans
-
Debug log: status_frozen_frontend_diagnosis
docs/plans/status_frozen_frontend_diagnosis/status_frozen_frontend_diagnosis_debug_log.md Plans
-
Status: Frozen Frontend Diagnosis — Step 1 Solution Assessment
If I'm running ./v3 status because the frontend is frozen, this doesn't tell me anything:
docs/plans/status_frozen_frontend_diagnosis/status_frozen_frontend_diagnosis_step1_solution_assessment.md Plans
-
Status: Frozen Frontend Diagnosis — Step 2 Feature Description
./v3 status reports "No read-model recovery is currently required" even when the frontend is frozen, because it only checks read-model health.
docs/plans/status_frozen_frontend_diagnosis/status_frozen_frontend_diagnosis_step2_feature_description.md Plans
-
Status: Frozen Frontend Diagnosis — Step 3 Development Plan
docs/plans/status_frozen_frontend_diagnosis/status_frozen_frontend_diagnosis_step3_development_plan.md Plans
-
Status: Frozen Frontend Diagnosis — Step 4 Implementation Summary
Branch: feature/status-frozen-frontend-diagnosis.
docs/plans/status_frozen_frontend_diagnosis/status_frozen_frontend_diagnosis_step4_implementation_summary.md Plans
-
status_lock_wait_notice_step1_solution_assessment.md
When I run ./v3 status and there's a lock, I want it to report that it's waiting on a lock, not just stall for a while.
docs/plans/status_lock_wait_notice/status_lock_wait_notice_step1_solution_assessment.md Plans
-
status_lock_wait_notice_step2_feature_description.md
When shared protected activity can delay ./v3 status, the command emits no output until collection finishes.
docs/plans/status_lock_wait_notice/status_lock_wait_notice_step2_feature_description.md Plans
-
status_lock_wait_notice_step3_development_plan.md
docs/plans/status_lock_wait_notice/status_lock_wait_notice_step3_development_plan.md Plans
-
status_lock_wait_notice_step4_implementation_summary.md
docs/plans/status_lock_wait_notice/status_lock_wait_notice_step4_implementation_summary.md Plans
-
tags_index_memory_fix.txt
docs/plans/tags_index_memory_fix.txt Plans
-
Task Queue Candidate Catalog
This catalog identifies every operational or background-style workflow found in the current application that could plausibly be run by the durable cron task qu…
docs/plans/task_queue_candidate_catalog.md Plans
-
Testing self-approval — Railspike debug log
No supported findings.
docs/plans/testing_self_approval/testing_self_approval_debug_log.md Plans
-
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
-
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
-
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
-
testing_self_approval_step4_implementation_summary.md
docs/plans/testing_self_approval/testing_self_approval_step4_implementation_summary.md Plans
-
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
-
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
-
test_runner_elapsed_time_step3_development_plan.md
docs/plans/test_runner_elapsed_time/test_runner_elapsed_time_step3_development_plan.md Plans
-
test_runner_elapsed_time_step4_implementation_summary.md
docs/plans/test_runner_elapsed_time/test_runner_elapsed_time_step4_implementation_summary.md Plans
-
Test run history retention
log table) and retention size (X runs / Y days / both)
docs/plans/test_run_history_retention_plan_v1.md Plans
-
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
-
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
-
Step 3: Development Plan — Test Run Summary Report
docs/plans/test_run_summary_report/test_run_summary_report_step3_development_plan.md Plans
-
Step 4: Implementation Summary — Test Run Summary Report
docs/plans/test_run_summary_report/test_run_summary_report_step4_implementation_summary.md Plans
-
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
-
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
-
theme_directive debug log
No supported findings.
docs/plans/theme_directive/theme_directive_debug_log.md Plans
-
theme_directive_step1_solution_assessment.md
Effort study: railspike-effort / v3/themedirective; host ledger.
docs/plans/theme_directive/theme_directive_step1_solution_assessment.md Plans
-
theme_directive_step2_feature_description.md
Effort study: railspike-effort / v3/themedirective; host ledger.
docs/plans/theme_directive/theme_directive_step2_feature_description.md Plans
-
theme_directive_step3_development_plan.md
Effort study: railspike-effort / v3/themedirective; host ledger.
docs/plans/theme_directive/theme_directive_step3_development_plan.md Plans
-
theme_directive_step4_implementation_summary.md
Effort study: railspike-effort / v3/themedirective; host ledger.
docs/plans/theme_directive/theme_directive_step4_implementation_summary.md Plans
-
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
-
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