-
Post Public Key Link Step 2 Feature Description
Users viewing a signed post need a direct way to inspect the author’s public key file.
docs/plans/archive/post_public_key_link_step2_feature_description.md Plans Plans and history
-
Post Public Key Link Step 3 Development Plan
docs/plans/archive/post_public_key_link_step3_development_plan.md Plans Plans and history
-
Post Public Key Link Step 4 Implementation Summary
docs/plans/archive/post_public_key_link_step4_implementation_summary.md Plans Plans and history
-
Public-Key Bootstrap Integrity Step 1 Solution Assessment
Automatically created bootstrap posts are unsigned and hidden, which makes identity association, authorship verification, account completeness, and repeated se…
docs/plans/archive/public_key_bootstrap_integrity_step1_solution_assessment.md Plans Plans and history
-
Public-Key Bootstrap Integrity Step 2 Feature Description
New accounts receive a hidden bootstrap post that is linked to their public key but is not signed, so visitors cannot distinguish identity association from cry…
docs/plans/archive/public_key_bootstrap_integrity_step2_feature_description.md Plans Plans and history
-
Public-Key Bootstrap Integrity Step 3 Development Plan
docs/plans/archive/public_key_bootstrap_integrity_step3_development_plan.md Plans Plans and history
-
Public-Key Bootstrap Integrity Step 4 Implementation Summary
docs/plans/archive/public_key_bootstrap_integrity_step4_implementation_summary.md Plans Plans and history
-
Public Key Visibility Step 1 Solution Assessment
Visitors should be able to view a user’s public key(s) from an approved profile, an unapproved profile, or that profile’s bootstrap post.
docs/plans/archive/public_key_visibility_step1_solution_assessment.md Plans Plans and history
-
Public Key Visibility Step 2 Feature Description
Approved and unapproved profile pages already expose a user’s public key under advanced technical details, but a visitor viewing the user’s bootstrap post has…
docs/plans/archive/public_key_visibility_step2_feature_description.md Plans Plans and history
-
Public Key Visibility Step 3 Development Plan
docs/plans/archive/public_key_visibility_step3_development_plan.md Plans Plans and history
-
Public Key Visibility Step 4 Implementation Summary
docs/plans/archive/public_key_visibility_step4_implementation_summary.md Plans Plans and history
-
QDB Disabled Vote Button Appearance – Solution Assessment
For the qdb theme/site, when a voting button becomes disabled, I want it to change appearance to a gray color / less activatable looking color.
docs/plans/archive/qdb_disabled_vote_button_appearance_step1_solution_assessment.md Plans Plans and history
-
Reliable Page Delivery: Step 1 Solution Assessment
Cold mobile loads can visibly render before CSS arrives or wait behind the large OpenPGP bundle before basic controls work, while the current production static…
docs/plans/archive/reliable_page_delivery_step1_solution_assessment.md Plans Plans and history
-
Reliable Page Delivery: Step 2 Feature Description
Cold mobile visits can show an unstyled page and delay basic controls behind OpenPGP loading; deployment can also expose mismatched cached page resources or st…
docs/plans/archive/reliable_page_delivery_step2_feature_description.md Plans Plans and history
-
Reliable Page Delivery: Step 3 Development Plan
docs/plans/archive/reliable_page_delivery_step3_development_plan.md Plans Plans and history
-
Reliable Page Delivery: Step 4 Implementation Summary
docs/plans/archive/reliable_page_delivery_step4_implementation_summary.md Plans Plans and history
-
Earlier directory-cleanup workflow
These files preserve the local cleanup workflow completed on branch
docs/plans/archive/repository_directory_cleanup_first_run/README.md Plans Plans and history
-
Repository directory cleanup — Railspike debug log
Final handoff evidence: all seven relocated files are byte-identical to planning baseline 6af9d3ad; README discovery reaches every destination; added local lin…
docs/plans/archive/repository_directory_cleanup_first_run/repository_directory_cleanup_debug_log.md Plans Plans and history
-
repository_directory_cleanup_step1_solution_assessment.md
As developer and maintainer, I want to clean up the project's top-level directory, and perhaps second-level.
docs/plans/archive/repository_directory_cleanup_first_run/repository_directory_cleanup_step1_solution_assessment.md Plans Plans and history
-
repository_directory_cleanup_step2_feature_description.md
Loose specifications, product copy, and planning notes obscure the root's essential project files.
docs/plans/archive/repository_directory_cleanup_first_run/repository_directory_cleanup_step2_feature_description.md Plans Plans and history
-
repository_directory_cleanup_step3_development_plan.md
All paths are relative to the repository root; existing categories supply the homes.
docs/plans/archive/repository_directory_cleanup_first_run/repository_directory_cleanup_step3_development_plan.md Plans Plans and history
-
repository_directory_cleanup_step4_implementation_summary.md
docs/plans/archive/repository_directory_cleanup_first_run/repository_directory_cleanup_step4_implementation_summary.md Plans Plans and history
-
Session Reauthentication: Step 1 Solution Assessment
An expired PHP session sends approved members to Lobby or a non-recovering access page and loses the URL they intended to visit.
docs/plans/archive/session_reauthentication_step1_solution_assessment.md Plans Plans and history
-
Session Reauthentication: Step 2 Feature Description
When the server loses an approved member's PHP session, protected navigation sends them to Lobby or an unrecoverable access page before the browser can silentl…
docs/plans/archive/session_reauthentication_step2_feature_description.md Plans Plans and history
-
Session Reauthentication: Step 3 Development Plan
docs/plans/archive/session_reauthentication_step3_development_plan.md Plans Plans and history
-
Session Reauthentication: Step 4 Implementation Summary
docs/plans/archive/session_reauthentication_step4_implementation_summary.md Plans Plans and history
-
Signed User-to-User Approvals — Step 1: Solution Assessment
User-to-user approval records currently claim an approver identity but lack a detached signature proving that the approver authorized the approval.
docs/plans/archive/signed_user_approvals_step1_solution_assessment.md Plans Plans and history
-
Signed User-to-User Approvals — Step 2: Feature Description
Approval replies identify an approver but currently have no cryptographic proof that the approver authorized the record.
docs/plans/archive/signed_user_approvals_step2_feature_description.md Plans Plans and history
-
Signed User-to-User Approvals — Step 3: Development Plan
Reply Approved Step 3 to begin implementation.
docs/plans/archive/signed_user_approvals_step3_development_plan.md Plans Plans and history
-
Signed User-to-User Approvals — Step 4: Implementation Summary
docs/plans/archive/signed_user_approvals_step4_implementation_summary.md Plans Plans and history
-
Site Profile and Instance State Decoupling: Step 1 Solution Assessment
Selecting the Chouse site profile currently switches local repositories, approval state, and read-model databases even though presentation choices should not d…
docs/plans/archive/site_profile_instance_state_decoupling_step1_solution_assessment.md Plans Plans and history
-
Site Profile and Instance State Decoupling: Step 2 Feature Description
Changing the local site profile currently changes the repository, approval state, and read-model database.
docs/plans/archive/site_profile_instance_state_decoupling_step2_feature_description.md Plans Plans and history
-
Site Profile and Instance State Decoupling: Step 3 Development Plan
docs/plans/archive/site_profile_instance_state_decoupling_step3_development_plan.md Plans Plans and history
-
Site Profile and Instance State Decoupling: Step 4 Implementation Summary
docs/plans/archive/site_profile_instance_state_decoupling_step4_implementation_summary.md Plans Plans and history
-
SQLite Viewer Effective Query Step 1 Solution Assessment
The viewer executes user SQL through local pagination and record-count wrappers, but users cannot see the exact SQL being evaluated, making debugging and repro…
docs/plans/archive/sqlite_download_with_query_webui_effective_query_step1_solution_assessment.md Plans Plans and history
-
SQLite Viewer Effective Query Step 2 Feature Description
The Run query tool wraps user SQL for local record counts and paginated data retrieval, but the executed statements are invisible.
docs/plans/archive/sqlite_download_with_query_webui_effective_query_step2_feature_description.md Plans Plans and history
-
SQLite Viewer Effective Query Step 3 Development Plan
docs/plans/archive/sqlite_download_with_query_webui_effective_query_step3_development_plan.md Plans Plans and history
-
SQLite Viewer Effective Query Step 4 Implementation Summary
docs/plans/archive/sqlite_download_with_query_webui_effective_query_step4_implementation_summary.md Plans Plans and history
-
SQLite Viewer Pagination Step 1 Solution Assessment
The SQLite viewer currently shows only bounded result previews, so users need a way to move through larger table and query-result datasets without loading or d…
docs/plans/archive/sqlite_download_with_query_webui_pagination_step1_solution_assessment.md Plans Plans and history
-
SQLite Viewer Pagination Step 2 Feature Description
The SQLite viewer currently exposes only a bounded preview of table rows and query results.
docs/plans/archive/sqlite_download_with_query_webui_pagination_step2_feature_description.md Plans Plans and history