-
Forte Board Memory-Safe Thread Loading Step 3 Development Plan
docs/plans/forte_board_memory_safe_thread_loading/forte_board_memory_safe_thread_loading_step3_development_plan.md Plans Plans and history
-
Forte Board Memory-Safe Thread Loading Step 4 Implementation Summary
docs/plans/forte_board_memory_safe_thread_loading/forte_board_memory_safe_thread_loading_step4_implementation_summary.md Plans Plans and history
-
forte_dark_theme_step1_solution_assessment.md
I want the Forte interface to respect the user's dark mode settings.
docs/plans/forte_dark_theme/forte_dark_theme_step1_solution_assessment.md Plans Plans and history
-
forte_dark_theme_step2_feature_description.md
Forte always renders in a fixed light palette, ignoring both the viewer's OS dark mode and the theme they chose on the site.
docs/plans/forte_dark_theme/forte_dark_theme_step2_feature_description.md Plans Plans and history
-
forte_dark_theme_step3_development_plan.md
docs/plans/forte_dark_theme/forte_dark_theme_step3_development_plan.md Plans Plans and history
-
forte_dark_theme_step4_implementation_summary.md
docs/plans/forte_dark_theme/forte_dark_theme_step4_implementation_summary.md Plans Plans and history
-
Forte — FDP Cycle Backlog
Exhaustive, ordered list of every Feature Development Process cycle needed to close the gaps identified in forteroadmap.md Section A.
docs/plans/forte_fdp_cycles.md Plans Plans and history
-
Step 1: Solution Assessment — Forte Mobile-Friendliness
The paned three-column views (Users, Board, Activity) and the rest of Forte rely on ad hoc, per-component breakpoints (site.css has 5 separate @media blocks, n…
docs/plans/forte_mobile_friendly/forte_mobile_friendly_step1_solution_assessment.md Plans Plans and history
-
Forte Mobile Stacked Panes — Step 1: Solution Assessment
On mobile views (narrow screens), I want the Forte view to stack all 3 panes vertically, so that it is usable.
docs/plans/forte_mobile_stacked_panes/forte_mobile_stacked_panes_step1_solution_assessment.md Plans Plans and history
-
Forte Mobile Stacked Panes — Step 2: Feature Description
At narrow viewport widths, Forte retains its desktop side-by-side pane layout, making the list and content panes too narrow to use.
docs/plans/forte_mobile_stacked_panes/forte_mobile_stacked_panes_step2_feature_description.md Plans Plans and history
-
Forte Mobile Stacked Panes — Step 3: Development Plan
docs/plans/forte_mobile_stacked_panes/forte_mobile_stacked_panes_step3_development_plan.md Plans Plans and history
-
Forte Mobile Stacked Panes — Step 4: Implementation Summary
docs/plans/forte_mobile_stacked_panes/forte_mobile_stacked_panes_step4_implementation_summary.md Plans Plans and history
-
Forte Reply Likes — Step 1: Solution Assessment
Forte lets readers Like a top-level thread and Flag any post, but its comments and nested replies lack a Like control.
docs/plans/forte_reply_likes/forte_reply_likes_step1_solution_assessment.md Plans Plans and history
-
Forte Reply Likes — Step 2: Feature Description
Forte renders Flag for every comment and nested reply but not Like, unlike the classic post interface.
docs/plans/forte_reply_likes/forte_reply_likes_step2_feature_description.md Plans Plans and history
-
Forte Reply Likes — Step 3: Development Plan
Reply Approved Step 3 to begin implementation.
docs/plans/forte_reply_likes/forte_reply_likes_step3_development_plan.md Plans Plans and history
-
Forte Reply Likes — Step 4: Implementation Summary
docs/plans/forte_reply_likes/forte_reply_likes_step4_implementation_summary.md Plans Plans and history
-
Forte Interface — Feature Roadmap
Consolidated backlog of what's still missing, deliberately excluded, or rough around the edges in Forte, based on a gap analysis against the classic UI's full…
docs/plans/forte_roadmap.md Plans Plans and history
-
Forte Unauthenticated Vote Identity Setup — Step 1: Solution Assessment
For a Forte visitor without a prepared browser identity, a vote can fail with a generic reload instruction instead of loading identity setup or explaining why…
docs/plans/forte_unauthenticated_vote_identity_setup/forte_unauthenticated_vote_identity_setup_step1_solution_assessment.md Plans Plans and history
-
Forte Unauthenticated Vote Identity Setup — Step 2: Feature Description
An unsigned Forte visitor who votes before preparing a browser identity can receive a generic reload message that conceals the failed prerequisite and leaves t…
docs/plans/forte_unauthenticated_vote_identity_setup/forte_unauthenticated_vote_identity_setup_step2_feature_description.md Plans Plans and history
-
Forte Unauthenticated Vote Identity Setup — Step 3: Development Plan
docs/plans/forte_unauthenticated_vote_identity_setup/forte_unauthenticated_vote_identity_setup_step3_development_plan.md Plans Plans and history
-
Forte Unauthenticated Vote Identity Setup — Step 4: Implementation Summary
docs/plans/forte_unauthenticated_vote_identity_setup/forte_unauthenticated_vote_identity_setup_step4_implementation_summary.md Plans Plans and history
-
Lessons from Building Forte Users → Carry Back to Board/Activity
Findings from implementing the Users three-pane view (docs/plans/archive/forteusersthreepanestep4implementationsummary.md) that are relevant to Board and Activ…
docs/plans/forte_users_lessons_for_board_activity.md Plans Plans and history
-
gpg_agent_leak debug log
docs/plans/gpg_agent_leak/gpg_agent_leak_debug_log.md Plans Plans and history
-
Step 2: Feature Description – GPG agent leak
Debug mode: enabled (project default via .railspikedebugon)
docs/plans/gpg_agent_leak/gpg_agent_leak_step2_feature_description.md Plans Plans and history
-
Step 3: Development Plan – GPG agent leak
docs/plans/gpg_agent_leak/gpg_agent_leak_step3_development_plan.md Plans Plans and history
-
Step 4: Implementation Summary – GPG agent leak
docs/plans/gpg_agent_leak/gpg_agent_leak_step4_implementation_summary.md Plans Plans and history
-
Future Feature Note: Guest Keypair + Proof-of-Work Voting
Not scheduled yet.
docs/plans/guest_identity_proof_of_work_voting.md Plans Plans and history
-
guided_php_setup_fallback_step1_solution_assessment.md
Please write Step 1 of docs/fdp/FEATUREDEVELOPMENTPROCESS.md for the more comprehensive no-PHP fallback we discussed before.
docs/plans/guided_php_setup_fallback/guided_php_setup_fallback_step1_solution_assessment.md Plans Plans and history
-
guided_php_setup_fallback_step2_feature_description.md
The existing missing-PHP fallback points to general setup documentation, leaving users to find instructions for their environment.
docs/plans/guided_php_setup_fallback/guided_php_setup_fallback_step2_feature_description.md Plans Plans and history
-
guided_php_setup_fallback_step3_development_plan.md
docs/plans/guided_php_setup_fallback/guided_php_setup_fallback_step3_development_plan.md Plans Plans and history
-
guided_php_setup_fallback_step4_implementation_summary.md
docs/plans/guided_php_setup_fallback/guided_php_setup_fallback_step4_implementation_summary.md Plans Plans and history
-
Hide Messages new-message form — Railspike debug log
docs/plans/hide_messages_new_message_form/hide_messages_new_message_form_debug_log.md Plans Plans and history
-
hide_messages_new_message_form_step1_solution_assessment.md
A user found the "New message" form on the /messages/ page confusing, thinking it is a registration form.
docs/plans/hide_messages_new_message_form/hide_messages_new_message_form_step1_solution_assessment.md Plans Plans and history
-
hide_messages_new_message_form_step2_feature_description.md
The “New message” recipient form on /messages/ can be mistaken for registration.
docs/plans/hide_messages_new_message_form/hide_messages_new_message_form_step2_feature_description.md Plans Plans and history
-
hide_messages_new_message_form_step3_development_plan.md
docs/plans/hide_messages_new_message_form/hide_messages_new_message_form_step3_development_plan.md Plans Plans and history
-
hide_messages_new_message_form_step4_implementation_summary.md
docs/plans/hide_messages_new_message_form/hide_messages_new_message_form_step4_implementation_summary.md Plans Plans and history
-
High-traffic absent retractions — Railspike debug log
No supported findings.
docs/plans/high_traffic_absent_retractions/high_traffic_absent_retractions_debug_log.md Plans Plans and history
-
high_traffic_absent_retractions_step1_solution_assessment.md
Effort study: railspike-effort, cycle v3/hightrafficabsentretractions; host ledger, standing enrollment R1/P2.
docs/plans/high_traffic_absent_retractions/high_traffic_absent_retractions_step1_solution_assessment.md Plans Plans and history
-
high_traffic_absent_retractions_step2_feature_description.md
Effort study: railspike-effort, cycle v3/hightrafficabsentretractions; host ledger, R1/P2.
docs/plans/high_traffic_absent_retractions/high_traffic_absent_retractions_step2_feature_description.md Plans Plans and history
-
high_traffic_absent_retractions_step3_development_plan.md
Effort study: railspike-effort, cycle v3/hightrafficabsentretractions; host ledger, R1/P2.
docs/plans/high_traffic_absent_retractions/high_traffic_absent_retractions_step3_development_plan.md Plans Plans and history