-
Offline Snapshot Publish Step 1 Solution Assessment
Operators need a fast, safe command that refreshes everything uniquely needed
docs/plans/offline_snapshot_publish/offline_snapshot_publish_step1_solution_assessment.md Plans Plans and history
-
Offline Snapshot Publish Step 2 Feature Description
Refreshing offline reading currently requires build-static, which renders the
docs/plans/offline_snapshot_publish/offline_snapshot_publish_step2_feature_description.md Plans Plans and history
-
Offline Snapshot Publish Step 3 Development Plan
bounded offline snapshot.
docs/plans/offline_snapshot_publish/offline_snapshot_publish_step3_development_plan.md Plans Plans and history
-
Offline Snapshot Publish Step 4 Implementation Summary
builder and publishes only offline/snapshot.sqlite3 outside static
docs/plans/offline_snapshot_publish/offline_snapshot_publish_step4_implementation_summary.md Plans Plans and history
-
OpenPGP Asset and Identity Code Fixes
Make browser OpenPGP work on both supported public origins without relying on
docs/plans/openpgp_asset_and_identity_code_fixes_v1.md Plans Plans and history
-
OpenPGP Production Incident Recovery Checklist
This checklist addresses a production failure in which the browser OpenPGP
docs/plans/openpgp_production_incident_recovery_checklist_v1.md Plans Plans and history
-
operator_record_deletion_step1_solution_assessment.md
As an operator-privileged user, I want to have the ability to delete records that are not my own.
docs/plans/operator_record_deletion/operator_record_deletion_step1_solution_assessment.md Plans Plans and history
-
operator_record_deletion_step2_feature_description.md
Only authors can currently retract their posts.
docs/plans/operator_record_deletion/operator_record_deletion_step2_feature_description.md Plans Plans and history
-
operator_record_deletion_step3_development_plan.md
docs/plans/operator_record_deletion/operator_record_deletion_step3_development_plan.md Plans Plans and history
-
operator_record_deletion_step4_implementation_summary.md
docs/plans/operator_record_deletion/operator_record_deletion_step4_implementation_summary.md Plans Plans and history
-
Outbox Item Target Link — Step 2 Feature Description
Outbox entries describe their local action but do not link to the underlying
docs/plans/outbox_item_target_link/outbox_item_target_link_step2_feature_description.md Plans Plans and history
-
Outbox Item Target Link — Step 3 Development Plan
docs/plans/outbox_item_target_link/outbox_item_target_link_step3_development_plan.md Plans Plans and history
-
Outbox Item Target Link — Step 4 Implementation Summary
docs/plans/outbox_item_target_link/outbox_item_target_link_step4_implementation_summary.md Plans Plans and history
-
Non-Minification Page Asset Performance Inventory
This is the exhaustive source-level inventory for the current application.
docs/plans/page_asset_performance_inventory.md Plans Plans and history
-
Shared pagination checklist
Track a shared pagination component, its first use in standard Activity, and later migrations across the app.
docs/plans/pagination_consolidation_checklist.md Plans Plans and history
-
pending_approval_activity_order_step1_solution_assessment.md
On the Users Awaiting Approval page, the user's most recent action should come before the Approve button; otherwise, on mobile, it looks like it's part of the…
docs/plans/pending_approval_activity_order/pending_approval_activity_order_step1_solution_assessment.md Plans Plans and history
-
pending_approval_activity_order_step2_feature_description.md
On Users Awaiting Approval, each user's most recent action appears after their Approve button.
docs/plans/pending_approval_activity_order/pending_approval_activity_order_step2_feature_description.md Plans Plans and history
-
pending_approval_activity_order_step3_development_plan.md
docs/plans/pending_approval_activity_order/pending_approval_activity_order_step3_development_plan.md Plans Plans and history
-
pending_approval_activity_order_step4_implementation_summary.md
docs/plans/pending_approval_activity_order/pending_approval_activity_order_step4_implementation_summary.md Plans Plans and history
-
Step 1: Solution Assessment — Pending User Latest Activity
On the /users/pending page, I want to see one line below each user that has their most recent activity (even if it's just an account bootstrap) and a timestamp.
docs/plans/pending_user_latest_activity/pending_user_latest_activity_step1_solution_assessment.md Plans Plans and history
-
Step 2: Feature Description — Pending User Latest Activity
The approved-only /users/pending queue identifies pending profiles but gives reviewers no at-a-glance indication of what each identity most recently did or whe…
docs/plans/pending_user_latest_activity/pending_user_latest_activity_step2_feature_description.md Plans Plans and history
-
Step 3: Development Plan — Pending User Latest Activity
docs/plans/pending_user_latest_activity/pending_user_latest_activity_step3_development_plan.md Plans Plans and history
-
Step 4: Implementation Summary — Pending User Latest Activity
docs/plans/pending_user_latest_activity/pending_user_latest_activity_step4_implementation_summary.md Plans Plans and history
-
Perceived Responsiveness Related Requests Plan V1
relatedfeaturerequests.txt lists:
docs/plans/perceived_responsiveness_related_requests_plan_v1.md Plans Plans and history
-
Performance Low-Hanging Fruit
A punch-list of small, well-scoped, high-confidence performance wins found by
docs/plans/performance_low_hanging_fruit_v1.md Plans Plans and history
-
Phone Site Development — Railspike Debug Log
Debug mode: enabled, resolved from the existing consuming-project .railspikedebugon file for this new workflow.
docs/plans/phone_site_development/phone_site_development_debug_log.md Plans Plans and history
-
phone_site_development_step1_solution_assessment.md
For this one:
docs/plans/phone_site_development/phone_site_development_step1_solution_assessment.md Plans Plans and history
-
phone_site_development_step2_feature_description.md
Approved operators cannot start and review genuine enhancement assessments from their phones on zenmemes.com.
docs/plans/phone_site_development/phone_site_development_step2_feature_description.md Plans Plans and history
-
phone_site_development_step3_development_plan.md
Each stage includes its meaningful tests and summary update and is committed before the next stage; organize and commit approved plans first under Railspike's…
docs/plans/phone_site_development/phone_site_development_step3_development_plan.md Plans Plans and history
-
phone_site_development_step4_implementation_summary.md
Implementation in progress.
docs/plans/phone_site_development/phone_site_development_step4_implementation_summary.md Plans Plans and history
-
Phone Site Development — Full-Goal Progress
Companion to Step 1.
docs/plans/phone_site_development_checklist.md Plans Plans and history
-
PHP Account Bootstrap Post Auto-Creation Slices V1
This document describes the implementation slices for replacing the placeholder bootstrappostid field with automatic bootstrap-post creation during account set…
docs/plans/php_account_bootstrap_post_auto_creation_slices_v1.md Plans Plans and history
-
PHP Approval Incremental Refresh Slices V1
This document outlines the implementation slices for removing full read-model rebuilds from approval writes while preserving the current approval semantics.
docs/plans/php_approval_incremental_refresh_slices_v1.md Plans Plans and history
-
App Version Notification Feature Flag Plan V1
Add a server-side feature flag for the browser "A new version is available." notification.
docs/plans/php_app_version_notification_feature_flag_plan_v1.md Plans Plans and history
-
PHP ASCII Restrictions Current State V1
This document describes how the v3 application currently handles ASCII restrictions in April 2026.
docs/plans/php_ascii_restrictions_current_state_v1.md Plans Plans and history
-
PHP Content Metadata Display Slices V1
This document outlines the implementation slices for standardizing how content metadata is displayed across the PHP forum rewrite.
docs/plans/php_content_metadata_display_slices_v1.md Plans Plans and history
-
PHP Forum Rewrite Answered Questions
project's answers to its own early planning questions, including a v2
docs/plans/php_forum_rewrite_answered_questions.md Plans Plans and history
-
PHP Forum Rewrite Compose Identity Flow V1
This document records the agreed V1 behavior for browser keypair generation and automatic identity bootstrap on compose routes.
docs/plans/php_forum_rewrite_compose_identity_flow_v1.md Plans Plans and history
-
PHP Forum Rewrite FDP Loop Recommendation
Run 6 separate FDP loops for this project.
docs/plans/php_forum_rewrite_fdp_loop_recommendation.md Plans Plans and history
-
PHP Forum Rewrite Next Step: Git Writes and Static Invalidation
This document defines the next implementation step after Apache-friendly static artifact generation.
docs/plans/php_forum_rewrite_next_step_git_invalidation.md Plans Plans and history