-
Forte Session-Recovery Routes: Step 4 Implementation Summary
docs/plans/archive/forte_session_recovery_routes_step4_implementation_summary.md Plans Plans and history
-
Forte Shared Toolbar — Step 1: Solution Assessment
Forte's three paned views have inconsistent toolbars — Board has the full button set, Activity has only "Board" + a disabled "Refresh", and Users has no toolba…
docs/plans/archive/forte_shared_toolbar_step1_solution_assessment.md Plans Plans and history
-
Forte Shared Toolbar Step 2 Feature Description
Forte's three paned views render different toolbars - Board has the full button set, Activity has only "Board" + a disabled "Refresh", and Users has no toolbar…
docs/plans/archive/forte_shared_toolbar_step2_feature_description.md Plans Plans and history
-
Forte Shared Toolbar Step 3 Development Plan
docs/plans/archive/forte_shared_toolbar_step3_development_plan.md Plans Plans and history
-
Forte Shared Toolbar Step 4 Implementation Summary
docs/plans/archive/forte_shared_toolbar_step4_implementation_summary.md Plans Plans and history
-
Forte Step 1 Solution Assessment
Users want to explore a Usenet/Forte Agent-like interface using the existing forum backend and frontend capabilities.
docs/plans/archive/forte_step1_solution_assessment.md Plans Plans and history
-
Forte Step 2 Feature Description
Users want a two-pane, Forte-Agent-styled thread reader — a nested-reply title list in one pane and a content pane for the selected post in the other — built f…
docs/plans/archive/forte_step2_feature_description.md Plans Plans and history
-
Forte Step 3 Development Plan
docs/plans/archive/forte_step3_development_plan.md Plans Plans and history
-
Forte Step 4 Implementation Summary
docs/plans/archive/forte_step4_implementation_summary.md Plans Plans and history
-
Forte Thread Selection URL Sync — Step 1: Solution Assessment
Selecting a thread on Forte's board never updates the URL (only tag/sort changes do), so reloading the page loses the current thread selection.
docs/plans/archive/forte_thread_selection_url_sync_step1_solution_assessment.md Plans Plans and history
-
Forte Thread Selection URL Sync — Step 2: Feature Description
Selecting a thread on Forte's board never updates the URL — only tag/sort changes do — so reloading or sharing a link loses the current thread selection.
docs/plans/archive/forte_thread_selection_url_sync_step2_feature_description.md Plans Plans and history
-
Forte Thread Selection URL Sync — Step 3: Development Plan
docs/plans/archive/forte_thread_selection_url_sync_step3_development_plan.md Plans Plans and history
-
Forte Thread Selection URL Sync — Step 4: Implementation Summary
docs/plans/archive/forte_thread_selection_url_sync_step4_implementation_summary.md Plans Plans and history
-
Forte Users Three-Pane Layout — Step 1: Solution Assessment
The Forte Users page (/forte/users/) is a single flat list, while Board and Activity already offer a filter pane + listing pane + detail pane, and we want User…
docs/plans/archive/forte_users_three_pane_step1_solution_assessment.md Plans Plans and history
-
Forte Users Three-Pane Layout — Step 2: Feature Description
The Forte Users page is a flat list of names, unlike Board and Activity's filter + listing + detail layout, so admins can't filter or inspect a user without le…
docs/plans/archive/forte_users_three_pane_step2_feature_description.md Plans Plans and history
-
Forte Users Three-Pane Layout — Step 3: Development Plan
Supersedes the alphabetical filter (Stages 2/4/5 above) per the Step 2 addendum.
docs/plans/archive/forte_users_three_pane_step3_development_plan.md Plans Plans and history
-
Forte Users Three-Pane Layout — Step 4: Implementation Summary
Per the Step 2/Step 3 addenda, replacing the alphabetical filter with semantic categories.
docs/plans/archive/forte_users_three_pane_step4_implementation_summary.md Plans Plans and history
-
Identity Bootstrap Signature Recovery: Step 1 Solution Assessment
A newly created browser key can fail its first signed identity-bootstrap verification even though a reload successfully publishes the same key, forcing users t…
docs/plans/archive/identity_bootstrap_signature_recovery_step1_solution_assessment.md Plans Plans and history
-
Identity Bootstrap Signature Recovery: Step 2 Feature Description
First-time browser-key setup can report an identity-bootstrap signature failure even when reloading lets the same key publish successfully.
docs/plans/archive/identity_bootstrap_signature_recovery_step2_feature_description.md Plans Plans and history
-
Identity Bootstrap Signature Recovery: Step 3 Development Plan
docs/plans/archive/identity_bootstrap_signature_recovery_step3_development_plan.md Plans Plans and history
-
Identity Bootstrap Signature Recovery: Step 4 Implementation Summary
docs/plans/archive/identity_bootstrap_signature_recovery_step4_implementation_summary.md Plans Plans and history
-
Invite Destination Selector — Step 1: Solution Assessment
On the invites page, destination entry should appear only when opted in and offer a typeable choice of recently used internal locations.
docs/plans/archive/invite_destination_selector_step1_solution_assessment.md Plans Plans and history
-
Invite Destination Selector — Step 2: Feature Description
The invites page always shows a disabled destination input and makes members type every destination, even when they are repeatedly inviting people to common or…
docs/plans/archive/invite_destination_selector_step2_feature_description.md Plans Plans and history
-
Invite Destination Selector — Step 3: Development Plan
docs/plans/archive/invite_destination_selector_step3_development_plan.md Plans Plans and history
-
Invite Destination Selector — Step 4: Implementation Summary
docs/plans/archive/invite_destination_selector_step4_implementation_summary.md Plans Plans and history
-
Invite Session Authentication: Step 1 Solution Assessment
On a public instance, the Account page can show an approved browser identity and the Invite link, while the invitation route cannot read that authenticated ses…
docs/plans/archive/invite_session_authentication_step1_solution_assessment.md Plans Plans and history
-
Invite Session Authentication: Step 2 Feature Description
On a public instance, an approved member with a saved browser key is not consistently recognized after their server session expires.
docs/plans/archive/invite_session_authentication_step2_feature_description.md Plans Plans and history
-
Invite Session Authentication: Step 3 Development Plan
docs/plans/archive/invite_session_authentication_step3_development_plan.md Plans Plans and history
-
Invite Session Authentication: Step 4 Implementation Summary
docs/plans/archive/invite_session_authentication_step4_implementation_summary.md Plans Plans and history
-
iOS Users Page Cache Freshness Step 1 Solution Assessment
iOS users need the users page to show fresh state instead of stale cached content.
docs/plans/archive/ios_users_page_cache_freshness_step1_solution_assessment.md Plans Plans and history
-
iOS Users Page Cache Freshness Step 2 Feature Description
Users can see stale cached content on the approved users page after user/profile state changes, with iOS reported as the affected client.
docs/plans/archive/ios_users_page_cache_freshness_step2_feature_description.md Plans Plans and history
-
iOS Users Page Cache Freshness Step 3 Development Plan
docs/plans/archive/ios_users_page_cache_freshness_step3_development_plan.md Plans Plans and history
-
iOS Users Page Cache Freshness Step 4 Implementation Summary
docs/plans/archive/ios_users_page_cache_freshness_step4_implementation_summary.md Plans Plans and history
-
links_browser_accessibility_step1_solution_assessment.md
Status: Archived at user request on 2026-10-13; deferred, not approved or implemented.
docs/plans/archive/links_browser_accessibility_step1_solution_assessment.md Plans Plans and history
-
LLM Prompt and Response Visibility Step 1 Solution Assessment
Operators and approved users need to inspect the exact prompt sent to the LLM and the exact response received when an LLM call occurs, but the current implemen…
docs/plans/archive/llm_prompt_response_visibility_step1_solution_assessment.md Plans Plans and history
-
LLM Prompt and Response Visibility Step 2 Feature Description
LLM activity is currently only partially observable: approved users can see selected post-analysis results, and operators can inspect limited diagnostics, but…
docs/plans/archive/llm_prompt_response_visibility_step2_feature_description.md Plans Plans and history
-
LLM Prompt and Response Visibility Step 3 Development Plan
docs/plans/archive/llm_prompt_response_visibility_step3_development_plan.md Plans Plans and history
-
LLM Prompt and Response Visibility Step 4 Implementation Summary
docs/plans/archive/llm_prompt_response_visibility_step4_implementation_summary.md Plans Plans and history
-
Redeemable Board Invitations — Step 1: Solution Assessment
An approved user should be able to invite a recipient who creates a new,
docs/plans/archive/lobby_board_invite_link_step1_solution_assessment.md Plans Plans and history
-
Redeemable Board Invitations — Step 2: Feature Description
Private boards require a recipient to have an identity before an approved user
docs/plans/archive/lobby_board_invite_link_step2_feature_description.md Plans Plans and history