-
runtime_detail_pages_step4_implementation_summary.md
docs/plans/runtime_detail_pages/runtime_detail_pages_step4_implementation_summary.md Plans Plans and history
-
Same-author collapse toggle — Railspike debug log
No supported findings.
docs/plans/same_author_collapse_toggle/same_author_collapse_toggle_debug_log.md Plans Plans and history
-
Same-author collapse toggle
Thread views automatically merge consecutive quick replies from the same author.
docs/plans/same_author_collapse_toggle/same_author_collapse_toggle_step2_feature_description.md Plans Plans and history
-
Same-author collapse toggle — development plan
docs/plans/same_author_collapse_toggle/same_author_collapse_toggle_step3_development_plan.md Plans Plans and history
-
Same-author collapse toggle — implementation
docs/plans/same_author_collapse_toggle/same_author_collapse_toggle_step4_implementation_summary.md Plans Plans and history
-
Scripture-Oriented Analysis Step 1 Solution Assessment
As a faithful user, I want another type of agentic analysis available to me:
docs/plans/scripture_oriented_analysis/scripture_oriented_analysis_step1_solution_assessment.md Plans Plans and history
-
Scripture-Oriented Analysis Step 2 Feature Description
Readers can request several kinds of agent responses but cannot select a scriptural reflection on a post.
docs/plans/scripture_oriented_analysis/scripture_oriented_analysis_step2_feature_description.md Plans Plans and history
-
Scripture-Oriented Analysis Step 3 Development Plan
docs/plans/scripture_oriented_analysis/scripture_oriented_analysis_step3_development_plan.md Plans Plans and history
-
Scripture-Oriented Analysis Step 4 Implementation Summary
docs/plans/scripture_oriented_analysis/scripture_oriented_analysis_step4_implementation_summary.md Plans Plans and history
-
Scripture response evaluation
This comparison uses the frozen cases and acceptance criteria in the approved development plan.
docs/plans/scripture_response_quality/evaluation/README.md Plans Plans and history
-
Initial comparison: no qualifying candidate
The faster configuration demonstrates a latency improvement, but neither revised candidate meets the approved quality gate.
docs/plans/scripture_response_quality/evaluation/report.md Plans Plans and history
-
results.json
docs/plans/scripture_response_quality/evaluation/results.json Plans Plans and history
-
Scripture Response Quality Railspike Debug Log
No supported findings for this revision.
docs/plans/scripture_response_quality/scripture_response_quality_debug_log.md Plans Plans and history
-
Scripture Response Quality and Latency Step 1 Solution Assessment
We've been iterating on this issue for a bit now.
docs/plans/scripture_response_quality/scripture_response_quality_step1_solution_assessment.md Plans Plans and history
-
Scripture Response Quality and Latency Step 2 Feature Description
Scripture replies can take nearly a minute yet overwhelm ordinary questions with repeated advice and loosely applied passages.
docs/plans/scripture_response_quality/scripture_response_quality_step2_feature_description.md Plans Plans and history
-
Scripture Response Quality and Latency Development Plan
docs/plans/scripture_response_quality/scripture_response_quality_step3_development_plan.md Plans Plans and history
-
Scripture Response Quality and Latency Implementation Summary
Planning commit: 075f91e7.
docs/plans/scripture_response_quality/scripture_response_quality_step4_implementation_summary.md Plans Plans and history
-
Scripture response reliability evaluation
The candidate does not qualify for release.
docs/plans/scripture_response_reliability/evaluation/report.md Plans Plans and history
-
results.json
docs/plans/scripture_response_reliability/evaluation/results.json Plans Plans and history
-
Scripture Response Reliability Railspike Debug Log
docs/plans/scripture_response_reliability/scripture_response_reliability_debug_log.md Plans Plans and history
-
Scripture Response Reliability — Solution Assessment
That would be a great answer.
docs/plans/scripture_response_reliability/scripture_response_reliability_step1_solution_assessment.md Plans Plans and history
-
Scripture Response Reliability — Feature Description
Existing scripture replies can miss the reader's decision and publish inaccurate quotations despite explicit instructions.
docs/plans/scripture_response_reliability/scripture_response_reliability_step2_feature_description.md Plans Plans and history
-
Scripture Response Reliability — Development Plan
docs/plans/scripture_response_reliability/scripture_response_reliability_step3_development_plan.md Plans Plans and history
-
Scripture Response Reliability — Implementation Summary
Status: Stages 1–6 completed; Stage 7 blocked by failed initial release gates.
docs/plans/scripture_response_reliability/scripture_response_reliability_step4_implementation_summary.md Plans Plans and history
-
Scripture reliability revision: regression stop
The repaired Sol writer passed five of six known regressions, but neither writer
docs/plans/scripture_response_reliability_revision/evaluation/report.md Plans Plans and history
-
results.json
docs/plans/scripture_response_reliability_revision/evaluation/results.json Plans Plans and history
-
Scripture Response Reliability Revision Railspike Debug Log
docs/plans/scripture_response_reliability_revision/scripture_response_reliability_revision_debug_log.md Plans Plans and history
-
Scripture Response Reliability Revision — Solution Assessment
Please go ahead.
docs/plans/scripture_response_reliability_revision/scripture_response_reliability_revision_step1_solution_assessment.md Plans Plans and history
-
Scripture Response Reliability Revision — Feature Description
The failed candidate verifies published quotations but rejects ordinary quoted language and misreads practical or pastoral concerns.
docs/plans/scripture_response_reliability_revision/scripture_response_reliability_revision_step2_feature_description.md Plans Plans and history
-
Scripture Response Reliability Revision — Development Plan
Deliver existing scripture request → complete reply → optional Expand → explicit recovery, using a scripture-only writer and verified quotations.
docs/plans/scripture_response_reliability_revision/scripture_response_reliability_revision_step3_development_plan.md Plans Plans and history
-
Scripture Response Reliability Revision — Step 3 Evaluation Protocol
This protocol is part of the Step 3 development plan and its approval scope.
docs/plans/scripture_response_reliability_revision/scripture_response_reliability_revision_step3_evaluation_protocol.md Plans Plans and history
-
Scripture Reliability Revision — Implementation Summary
Approval: user authorized the original Step 3 plan and linked protocol.
docs/plans/scripture_response_reliability_revision/scripture_response_reliability_revision_step4_implementation_summary.md Plans Plans and history
-
Collection-selection fixes
Authorization: User requested QDB welcome selection first, then offline candidate selection, in separate commits, with this ongoing checklist.
docs/plans/selection_fixes_checklist.md Plans Plans and history
-
Server cooperative content deletion debug log
docs/plans/server_cooperative_content_deletion/server_cooperative_content_deletion_debug_log.md Plans Plans and history
-
Server Cooperative Content Deletion Step 1 Solution Assessment
Explore server-cooperative content deletion.
docs/plans/server_cooperative_content_deletion/server_cooperative_content_deletion_step1_solution_assessment.md Plans Plans and history
-
Server Cooperative Content Deletion Step 2 Feature Description
Authors cannot retract their own posts; only operators can remove records, and that leaves content in Git history with no author authority.
docs/plans/server_cooperative_content_deletion/server_cooperative_content_deletion_step2_feature_description.md Plans Plans and history
-
Server Cooperative Content Deletion Step 3 Development Plan
docs/plans/server_cooperative_content_deletion/server_cooperative_content_deletion_step3_development_plan.md Plans Plans and history
-
Server Cooperative Content Deletion Step 4 Implementation Summary
docs/plans/server_cooperative_content_deletion/server_cooperative_content_deletion_step4_implementation_summary.md Plans Plans and history
-
Session Reauthentication Reference
The original report concerned requests arriving after a PHP session record expired or was cleaned up, before browser JavaScript could restore authentication.
docs/plans/session_reauthentication_reference.md Plans Plans and history
-
Decision: signing in must not quietly sign the browser out
Status: decided 2026-10-30 — option A with a 30-second grace period; implemented on fix/session-rotation-race (see Implementation).
docs/plans/session_rotation_race_decision.md Plans Plans and history