-
read_model_schema_version_integrity_step4_implementation_summary.md
docs/plans/read_model_schema_version_integrity/read_model_schema_version_integrity_step4_implementation_summary.md Plans
-
rebuild_availability debug log
docs/plans/rebuild_availability/rebuild_availability_debug_log.md Plans
-
rebuild_availability_step1_solution_assessment.md
Debug mode: enabled (debug log)
docs/plans/rebuild_availability/rebuild_availability_step1_solution_assessment.md Plans
-
rebuild_availability_step2_feature_description.md
Debug mode: enabled (debug log)
docs/plans/rebuild_availability/rebuild_availability_step2_feature_description.md Plans
-
rebuild_availability_step3_development_plan.md
Debug mode: enabled (debug log)
docs/plans/rebuild_availability/rebuild_availability_step3_development_plan.md Plans
-
rebuild_availability_step4_implementation_summary.md
Debug mode: enabled (debug log)
docs/plans/rebuild_availability/rebuild_availability_step4_implementation_summary.md Plans
-
rebuild_memory_bound_debug_log.md
Source: Step 1 option comparison, shared-contract reuse and normal-entry recovery.
docs/plans/rebuild_memory_bound_debug_log.md Plans
-
rebuild_memory_bound_step1_solution_assessment.md
Effort study: railspike-effort / v3/rebuildmemorybound; P2 ledger
docs/plans/rebuild_memory_bound_step1_solution_assessment.md Plans
-
Rebuild thread-label stall — Railspike debug log
Debug mode: enabled by the user's explicit request, recorded in the Step 1 artifact.
docs/plans/rebuild_thread_label_stall/rebuild_thread_label_stall_debug_log.md Plans
-
rebuild_thread_label_stall_step1_solution_assessment.md
On production, ./v3 rebuild appears to stall after this step:
docs/plans/rebuild_thread_label_stall/rebuild_thread_label_stall_step1_solution_assessment.md Plans
-
rebuild_thread_label_stall_step2_feature_description.md
./v3 rebuild appears stalled when parsing reaches its total but silent indexing continues.
docs/plans/rebuild_thread_label_stall/rebuild_thread_label_stall_step2_feature_description.md Plans
-
rebuild_thread_label_stall_step3_development_plan.md
Normal ./v3 rebuild batches all three provenance families and reports work through validated promotion/snapshot readiness.
docs/plans/rebuild_thread_label_stall/rebuild_thread_label_stall_step3_development_plan.md Plans
-
rebuild_thread_label_stall_step4_implementation_summary.md
Planning commit: 686d8766.
docs/plans/rebuild_thread_label_stall/rebuild_thread_label_stall_step4_implementation_summary.md Plans
-
What still triggers a full read-model rebuild
Inventory of main at 8a189ab (2026-11-09), after rebuild availability and retraction speed.
docs/plans/rebuild_triggers_checklist.md Plans
-
Recent activity — Railspike debug log
Mode: enabled by the host-root .railspikedebugon file; extended estimates enabled under standing P2 enrollment.
docs/plans/recent_activity/recent_activity_debug_log.md Plans
-
recent_activity_step1_solution_assessment.md
Effort study: railspike-effort / v3/recentactivity; ledger, standing P2 enrollment
docs/plans/recent_activity/recent_activity_step1_solution_assessment.md Plans
-
recent_activity_step2_feature_description.md
Effort study: railspike-effort / v3/recentactivity; ledger, standing P2 enrollment
docs/plans/recent_activity/recent_activity_step2_feature_description.md Plans
-
recent_activity_step3_development_plan.md
Effort study: railspike-effort / v3/recentactivity; ledger, P2
docs/plans/recent_activity/recent_activity_step3_development_plan.md Plans
-
recent_activity_step4_implementation_summary.md
Effort study: railspike-effort / v3/recentactivity; ledger
docs/plans/recent_activity/recent_activity_step4_implementation_summary.md Plans
-
Related Content Relevance Gate Plan v1
Suggested relatedcontentassessment shape:
docs/plans/related_content_relevance_gate_plan_v1.md Plans
-
rename_windark_to_midnight debug log
Debug mode: enabled (project marker .railspikedebugon).
docs/plans/rename_windark_to_midnight/rename_windark_to_midnight_debug_log.md Plans
-
Rename the windark theme to midnight: Step 1 solution assessment
Is midnight theme still called windark internally?
docs/plans/rename_windark_to_midnight/rename_windark_to_midnight_step1_solution_assessment.md Plans
-
Rename the windark theme to midnight: Step 2 feature description
The theme labelled "Midnight" is still windark in code, files, selectors, tests and AGENTS.md.
docs/plans/rename_windark_to_midnight/rename_windark_to_midnight_step2_feature_description.md Plans
-
Rename the windark theme to midnight: Step 3 development plan
docs/plans/rename_windark_to_midnight/rename_windark_to_midnight_step3_development_plan.md Plans
-
Rename the windark theme to midnight: Step 4 implementation summary
Branch: renamewindarktomidnight (from main).
docs/plans/rename_windark_to_midnight/rename_windark_to_midnight_step4_implementation_summary.md Plans
-
Reply bare card — Railspike debug log
docs/plans/reply_bare_card/reply_bare_card_debug_log.md Plans
-
reply_bare_card_one_shot.md
Cycle: v3/replybarecard; Mode: one-shot; Record: this file; Index: plans index
docs/plans/reply_bare_card/reply_bare_card_one_shot.md Plans
-
Reply composer focus/layout — Railspike debug log
No supported findings.
docs/plans/reply_composer_focus_layout/reply_composer_focus_layout_debug_log.md Plans
-
reply_composer_focus_layout_step1_solution_assessment.md
Can you please check the inline reply form for similar behavior, and it also for some reason features a floating post button that covers up the textarea...
docs/plans/reply_composer_focus_layout/reply_composer_focus_layout_step1_solution_assessment.md Plans
-
reply_composer_focus_layout_step2_feature_description.md
Inline reply switches focus between two textareas, and the floating Post row can cover the editor.
docs/plans/reply_composer_focus_layout/reply_composer_focus_layout_step2_feature_description.md Plans
-
reply_composer_focus_layout_step3_development_plan.md
From ordinary thread Reply or dedicated reply entry, submit exactly one reply or retain the draft with visible correction/retry.
docs/plans/reply_composer_focus_layout/reply_composer_focus_layout_step3_development_plan.md Plans
-
reply_composer_focus_layout_step4_implementation_summary.md
Effort study: railspike-effort / v3/replycomposerfocuslayout · Host ledger
docs/plans/reply_composer_focus_layout/reply_composer_focus_layout_step4_implementation_summary.md Plans
-
Reply continuation — Railspike diagnostics
No supported findings.
docs/plans/reply_continuation/reply_continuation_debug_log.md Plans
-
reply_continuation_step1_solution_assessment.md
Effort study: railspike-effort / v3/replycontinuation · P2 ledger.
docs/plans/reply_continuation/reply_continuation_step1_solution_assessment.md Plans
-
reply_continuation_step2_feature_description.md
Effort study: railspike-effort / v3/replycontinuation · P2 ledger.
docs/plans/reply_continuation/reply_continuation_step2_feature_description.md Plans
-
reply_continuation_step3_development_plan.md
Effort study: railspike-effort / v3/replycontinuation · P2 ledger.
docs/plans/reply_continuation/reply_continuation_step3_development_plan.md Plans
-
reply_continuation_step4_implementation_summary.md
Effort study: railspike-effort / v3/replycontinuation · Ledger.
docs/plans/reply_continuation/reply_continuation_step4_implementation_summary.md Plans
-
Reply title directive — Railspike debug log
Debug mode: enabled (project marker .railspikedebugon).
docs/plans/reply_title_directive/reply_title_directive_debug_log.md Plans
-
Reply title directive — Step 1: Solution Assessment
Debug mode: enabled (project marker .railspikedebugon present at workflow start; snapshot 2026-11-03T05:19:48Z)
docs/plans/reply_title_directive/reply_title_directive_step1_solution_assessment.md Plans
-
Reply title directive — Step 2: Feature Description
Effort study: railspike-effort / v3/replytitledirective — host ledger; standing enrollment under protocol P2
docs/plans/reply_title_directive/reply_title_directive_step2_feature_description.md Plans