-
site_favicons_step1_solution_assessment.md
Our default favicon is a letter Z, which is kind of appropriate for zenmemes, but very inappropriate for other sites.
docs/plans/site_favicons/site_favicons_step1_solution_assessment.md Plans
-
site_favicons_step2_feature_description.md
chouse and qdb show the zenmemes "Z" favicon in browser tabs, bookmarks and the installed-app icon.
docs/plans/site_favicons/site_favicons_step2_feature_description.md Plans
-
site_favicons_step3_development_plan.md
Waiting for "Approved Step 3" before starting Step 4.
docs/plans/site_favicons/site_favicons_step3_development_plan.md Plans
-
site_favicons_step4_implementation_summary.md
docs/plans/site_favicons/site_favicons_step4_implementation_summary.md Plans
-
Site Feature Flags Slices V1
This document outlines an atomic implementation plan for making site feature flags visible, auditable, and eventually mutable through the site while preserving…
docs/plans/site_feature_flags_slices_v1.md Plans
-
site_operations_page Railspike debug log
docs/plans/site_operations_page/site_operations_page_debug_log.md Plans
-
site_operations_page_step2_feature_description.md
Effort study: railspike-effort / v3/siteoperationspage; ledger.
docs/plans/site_operations_page/site_operations_page_step2_feature_description.md Plans
-
site_operations_page_step3_development_plan.md
Effort study: railspike-effort / v3/siteoperationspage; ledger.
docs/plans/site_operations_page/site_operations_page_step3_development_plan.md Plans
-
site_operations_page_step4_implementation_summary.md
Effort study: railspike-effort / v3/siteoperationspage; ledger.
docs/plans/site_operations_page/site_operations_page_step4_implementation_summary.md Plans
-
Site Text Search Step 1 Solution Assessment
Users need a site search path that lets them enter text and find matching visible forum content without leaving the application.
docs/plans/site_text_search/site_text_search_step1_solution_assessment.md Plans
-
Site-Wide Reaction State — Step 1: Solution Assessment
As a user, I want to know which quotes I've already voted on and see the
docs/plans/site_wide_reaction_state/site_wide_reaction_state_step1_solution_assessment.md Plans
-
Site-Wide Reaction State — Step 2: Feature Description
QDB already enforces one vote per identity and quote, but renders partial,
docs/plans/site_wide_reaction_state/site_wide_reaction_state_step2_feature_description.md Plans
-
Site-Wide Reaction State — Step 3: Development Plan
successful action remains disabled on matching controls on later pages for
docs/plans/site_wide_reaction_state/site_wide_reaction_state_step3_development_plan.md Plans
-
Site-Wide Reaction State — Step 4: Implementation Summary
permalink components so both caption controls render disabled together.
docs/plans/site_wide_reaction_state/site_wide_reaction_state_step4_implementation_summary.md Plans
-
SQLite Viewer Query Catalog Candidates
This is a follow-up list of useful presets to add to the SQLite viewer.
docs/plans/sqlite_download_with_query_webui_query_catalog_candidates.md Plans
-
Standard Activity page size fix
The local /activity/ response measured 88.5 MB for 100 entries.
docs/plans/standard_activity_manifest_size_fix_outline.md Plans
-
starfield_key_backup_step1_solution_assessment.md
now that we have a private messages feature, it becomes more relevant for users to back up their keys
docs/plans/starfield_key_backup/starfield_key_backup_step1_solution_assessment.md Plans
-
starfield_key_backup_step2_feature_description.md
Private messages are unreadable if the browser-held private key is lost, and users today can only copy raw key text from /account/key/, with no durable backup…
docs/plans/starfield_key_backup/starfield_key_backup_step2_feature_description.md Plans
-
starfield_key_backup_step3_development_plan.md
docs/plans/starfield_key_backup/starfield_key_backup_step3_development_plan.md Plans
-
starfield_key_backup_step4_implementation_summary.md
docs/plans/starfield_key_backup/starfield_key_backup_step4_implementation_summary.md Plans
-
acceptance_evidence.json
docs/plans/startup_dependency_recovery/acceptance_evidence.json Plans
-
Startup dependency recovery acceptance
Verified on 2026-10-13.
docs/plans/startup_dependency_recovery/acceptance_evidence.md Plans
-
Startup dependency recovery Railspike debug log
Debug mode: enabled, carried forward from the user's explicit enable request in this continuing dependency-recovery work.
docs/plans/startup_dependency_recovery/startup_dependency_recovery_debug_log.md Plans
-
startup_dependency_recovery_step1_solution_assessment.md
Please write Step 1 for the section titled "Fix the discovered guidance gaps".
docs/plans/startup_dependency_recovery/startup_dependency_recovery_step1_solution_assessment.md Plans
-
startup_dependency_recovery_step2_feature_description.md
The user's Ubuntu 22.04 startup failures identify missing PHP/extensions but leave recovery vague.
docs/plans/startup_dependency_recovery/startup_dependency_recovery_step2_feature_description.md Plans
-
startup_dependency_recovery_step3_development_plan.md
docs/plans/startup_dependency_recovery/startup_dependency_recovery_step3_development_plan.md Plans
-
startup_dependency_recovery_step4_implementation_summary.md
All five stages implemented and verified on feat/startup-dependency-recovery.
docs/plans/startup_dependency_recovery/startup_dependency_recovery_step4_implementation_summary.md Plans
-
Status frontend target — Railspike debug log
docs/plans/status_frontend_target/status_frontend_target_debug_log.md Plans
-
Status frontend target — Step 1 solution assessment
This test usually fails for one of two reasons:
docs/plans/status_frontend_target/status_frontend_target_step1_solution_assessment.md Plans
-
Status frontend target — Step 2 feature description
Plain ./v3 status can report a healthy frontend as unreachable because it assumes port 8000.
docs/plans/status_frontend_target/status_frontend_target_step2_feature_description.md Plans
-
Status frontend target — Step 3 development plan
docs/plans/status_frontend_target/status_frontend_target_step3_development_plan.md Plans
-
Status frontend target — implementation summary
Planning commit: 1f7e49d1.
docs/plans/status_frontend_target/status_frontend_target_step4_implementation_summary.md Plans
-
Debug log: status_frozen_frontend_diagnosis
docs/plans/status_frozen_frontend_diagnosis/status_frozen_frontend_diagnosis_debug_log.md Plans
-
Status: Frozen Frontend Diagnosis — Step 1 Solution Assessment
If I'm running ./v3 status because the frontend is frozen, this doesn't tell me anything:
docs/plans/status_frozen_frontend_diagnosis/status_frozen_frontend_diagnosis_step1_solution_assessment.md Plans
-
Status: Frozen Frontend Diagnosis — Step 2 Feature Description
./v3 status reports "No read-model recovery is currently required" even when the frontend is frozen, because it only checks read-model health.
docs/plans/status_frozen_frontend_diagnosis/status_frozen_frontend_diagnosis_step2_feature_description.md Plans
-
Status: Frozen Frontend Diagnosis — Step 3 Development Plan
docs/plans/status_frozen_frontend_diagnosis/status_frozen_frontend_diagnosis_step3_development_plan.md Plans
-
Status: Frozen Frontend Diagnosis — Step 4 Implementation Summary
Branch: feature/status-frozen-frontend-diagnosis.
docs/plans/status_frozen_frontend_diagnosis/status_frozen_frontend_diagnosis_step4_implementation_summary.md Plans
-
status_lock_wait_notice_step1_solution_assessment.md
When I run ./v3 status and there's a lock, I want it to report that it's waiting on a lock, not just stall for a while.
docs/plans/status_lock_wait_notice/status_lock_wait_notice_step1_solution_assessment.md Plans
-
status_lock_wait_notice_step2_feature_description.md
When shared protected activity can delay ./v3 status, the command emits no output until collection finishes.
docs/plans/status_lock_wait_notice/status_lock_wait_notice_step2_feature_description.md Plans
-
status_lock_wait_notice_step3_development_plan.md
docs/plans/status_lock_wait_notice/status_lock_wait_notice_step3_development_plan.md Plans