-
`v3` Status Command — Step 4 Implementation Summary
docs/plans/v3_status_command/v3_status_command_step4_implementation_summary.md Plans Plans and history
-
viewer_nav_prepaint Railspike debug log
docs/plans/viewer_nav_prepaint/viewer_nav_prepaint_debug_log.md Plans Plans and history
-
viewer_nav_prepaint_step2_feature_description.md
Effort study: railspike-effort / v3/viewernavprepaint; ledger.
docs/plans/viewer_nav_prepaint/viewer_nav_prepaint_step2_feature_description.md Plans Plans and history
-
viewer_nav_prepaint_step3_development_plan.md
Effort study: railspike-effort / v3/viewernavprepaint; ledger.
docs/plans/viewer_nav_prepaint/viewer_nav_prepaint_step3_development_plan.md Plans Plans and history
-
viewer_nav_prepaint_step4_implementation_summary.md
Debug mode: enabled (inherited from Step 3; debug log)
docs/plans/viewer_nav_prepaint/viewer_nav_prepaint_step4_implementation_summary.md Plans Plans and history
-
viewer_tag_lookup_memoization — Railspike debug log
User requested enabling extended estimates for this cycle and updating Step 1 with them.
docs/plans/viewer_tag_lookup_memoization/viewer_tag_lookup_memoization_debug_log.md Plans Plans and history
-
viewer_tag_lookup_memoization_step1_solution_assessment.md
Effort study: railspike-effort / v3/viewertaglookupmemoization; ledger, standing enrollment P2.
docs/plans/viewer_tag_lookup_memoization/viewer_tag_lookup_memoization_step1_solution_assessment.md Plans Plans and history
-
viewer_tag_lookup_memoization_step2_feature_description.md
Effort study: railspike-effort / v3/viewertaglookupmemoization; ledger, standing enrollment P2.
docs/plans/viewer_tag_lookup_memoization/viewer_tag_lookup_memoization_step2_feature_description.md Plans Plans and history
-
viewer_tag_read_model — Railspike debug log
First cycle of a B-then-A sequence, promoted from the predecessor memoization cycle's deferred Option B.
docs/plans/viewer_tag_read_model/viewer_tag_read_model_debug_log.md Plans Plans and history
-
viewer_tag_read_model_step1_solution_assessment.md
Effort study: railspike-effort / v3/viewertagreadmodel; ledger, standing enrollment P2.
docs/plans/viewer_tag_read_model/viewer_tag_read_model_step1_solution_assessment.md Plans Plans and history
-
visitor_statistics_step1_solution_assessment.md
As an operator, I'd like to see basic stats about clients/users visiting my instance.
docs/plans/visitor_statistics/visitor_statistics_step1_solution_assessment.md Plans Plans and history
-
Step 2: Feature Description — Visitor Statistics
An operator has no consistent in-product view of the people and browser clients reaching an instance.
docs/plans/visitor_statistics/visitor_statistics_step2_feature_description.md Plans Plans and history
-
Step 3: Development Plan — Visitor Statistics
docs/plans/visitor_statistics/visitor_statistics_step3_development_plan.md Plans Plans and history
-
Step 4: Implementation Summary — Visitor Statistics
docs/plans/visitor_statistics/visitor_statistics_step4_implementation_summary.md Plans Plans and history
-
visitor_statistics_aggregate_dashboard_step1_solution_assessment.md
Sounds good, please write Step 1 of docs/fdp/FEATUREDEVELOPMENTPROCESS.md.
docs/plans/visitor_statistics_aggregate_dashboard/visitor_statistics_aggregate_dashboard_step1_solution_assessment.md Plans Plans and history
-
Step 2: Feature Description — Aggregate Visitor Statistics Dashboard
The current visitor-statistics page reports only daily aggregates in a three-row table, making its “24 hours” label inaccurate and leaving operators unable to…
docs/plans/visitor_statistics_aggregate_dashboard/visitor_statistics_aggregate_dashboard_step2_feature_description.md Plans Plans and history
-
Step 3: Development Plan — Aggregate Visitor Statistics Dashboard
docs/plans/visitor_statistics_aggregate_dashboard/visitor_statistics_aggregate_dashboard_step3_development_plan.md Plans Plans and history
-
Step 4: Implementation Summary — Aggregate Visitor Statistics Dashboard
docs/plans/visitor_statistics_aggregate_dashboard/visitor_statistics_aggregate_dashboard_step4_implementation_summary.md Plans Plans and history
-
Vote Identity Readiness — Step 1: Solution Assessment
Whenever I vote, it says "preparing identity..." first.
docs/plans/vote_identity_readiness/vote_identity_readiness_step1_solution_assessment.md Plans Plans and history
-
Vote Identity Readiness — Step 2: Feature Description
A browser that already holds a usable local identity can still perform publication, verification, or identity-hint work only after a vote is clicked.
docs/plans/vote_identity_readiness/vote_identity_readiness_step2_feature_description.md Plans Plans and history
-
Vote Identity Readiness — Step 3: Development Plan
docs/plans/vote_identity_readiness/vote_identity_readiness_step3_development_plan.md Plans Plans and history
-
Vote Identity Readiness — Step 4: Implementation Summary
docs/plans/vote_identity_readiness/vote_identity_readiness_step4_implementation_summary.md Plans Plans and history
-
web_deploy Railspike debug log
docs/plans/web_deploy/web_deploy_debug_log.md Plans Plans and history
-
web_deploy_step1_solution_assessment.md
Debug mode: enabled (.railspikedebugon present at the project root; new workflow)
docs/plans/web_deploy/web_deploy_step1_solution_assessment.md Plans Plans and history
-
web_deploy_step2_feature_description.md
Effort study: railspike-effort / v3/webdeploy (ledger); standing enrollment P2
docs/plans/web_deploy/web_deploy_step2_feature_description.md Plans Plans and history
-
web_deploy_step3_development_plan.md
Effort study: railspike-effort / v3/webdeploy (ledger); standing enrollment P2
docs/plans/web_deploy/web_deploy_step3_development_plan.md Plans Plans and history
-
web_deploy_step4_implementation_summary.md
Effort study: railspike-effort / v3/webdeploy (ledger); standing enrollment P2
docs/plans/web_deploy/web_deploy_step4_implementation_summary.md Plans Plans and history
-
Debug log — word97_chicago_disabled_and_dark
docs/plans/word97_disabled_and_dark_theme/word97_chicago_disabled_and_dark_debug_log.md Plans Plans and history
-
Step 1: Solution Assessment — Word 97 disabled buttons and dark Chicago/Word 97
From todo.txt:
docs/plans/word97_disabled_and_dark_theme/word97_chicago_disabled_and_dark_step1_solution_assessment.md Plans Plans and history
-
Step 2: Feature Description — Word 97 disabled buttons and dark Win9x theme
In the Word 97 theme, disabled buttons do not look disabled.
docs/plans/word97_disabled_and_dark_theme/word97_chicago_disabled_and_dark_step2_feature_description.md Plans Plans and history
-
Step 3: Development Plan — Word 97 disabled buttons and dark Win9x theme
Working name for the new theme: Win Dark (windark, mode dark); rename at review if preferred.
docs/plans/word97_disabled_and_dark_theme/word97_chicago_disabled_and_dark_step3_development_plan.md Plans Plans and history
-
Step 4: Implementation Summary — Word 97 disabled buttons and dark Win9x theme
docs/plans/word97_disabled_and_dark_theme/word97_chicago_disabled_and_dark_step4_implementation_summary.md Plans Plans and history
-
Word 97 Theme Improvements (round 2)
The theme-word97 branch has the base theme plus three improvement commits
docs/plans/word97_theme_improvements_plan_v1.md Plans Plans and history
-
Word 97 theme repair checklist
Status: done on branch fix/word97-theme-repair; each fix landed as its own commit, recorded on the item.
docs/plans/word97_theme_repair_checklist.md Plans Plans and history
-
work_page Railspike debug log
docs/plans/work_page_debug_log.md Plans Plans and history
-
work_page_step1_solution_assessment.md
Effort study: railspike-effort / v3/workpage; host ledger.
docs/plans/work_page_step1_solution_assessment.md Plans Plans and history
-
work_tracking Railspike debug log
docs/plans/work_tracking/work_tracking_debug_log.md Plans Plans and history
-
work_tracking_step1_solution_assessment.md
Effort study: railspike-effort / v3/worktracking; host ledger.
docs/plans/work_tracking/work_tracking_step1_solution_assessment.md Plans Plans and history
-
work_tracking_step2_feature_description.md
Effort study: railspike-effort / v3/worktracking; host ledger.
docs/plans/work_tracking/work_tracking_step2_feature_description.md Plans Plans and history
-
work_tracking_step3_development_plan.md
Effort study: railspike-effort / v3/worktracking; host ledger.
docs/plans/work_tracking/work_tracking_step3_development_plan.md Plans Plans and history