-
post_retraction_sweep_debug_log.md
Final stage commit: 8a1d73da.
docs/plans/post_retraction_sweep/post_retraction_sweep_debug_log.md Plans Plans and history
-
post_retraction_sweep_step1_solution_assessment.md
We have implemented basic post retraction, but the content still stays in multiple places.
docs/plans/post_retraction_sweep/post_retraction_sweep_step1_solution_assessment.md Plans Plans and history
-
post_retraction_sweep_step2_feature_description.md
Retraction hides content, but retained local payloads and interrupted artifact cleanup remain.
docs/plans/post_retraction_sweep/post_retraction_sweep_step2_feature_description.md Plans Plans and history
-
post_retraction_sweep_step3_development_plan.md
docs/plans/post_retraction_sweep/post_retraction_sweep_step3_development_plan.md Plans Plans and history
-
post_retraction_sweep_step4_implementation_summary.md
Planning commit: 6c6683f2.
docs/plans/post_retraction_sweep/post_retraction_sweep_step4_implementation_summary.md Plans Plans and history
-
Post Summary and Thread Context for Agent Replies Plan V1
Add a neutral one-sentence postsummary to stored post analysis, then use each thread comment's postsummary and full body text as context when deciding/generate…
docs/plans/post_summary_thread_context_agent_reply_plan_v1.md Plans Plans and history
-
preexisting_test_failures Railspike debug log
docs/plans/preexisting_test_failures/preexisting_test_failures_debug_log.md Plans Plans and history
-
preexisting_test_failures_one_shot.md
Cycle: v3/preexistingtestfailures; Mode: one-shot; Record/index: this file, plans index; related: fastdefaulttestsoutliers, parked fastdefaulttests Step 1
docs/plans/preexisting_test_failures/preexisting_test_failures_one_shot.md Plans Plans and history
-
prepared_thread_event_fields_step2_feature_description.md
The signed "Create thread" submit path (used by any identity-authenticated member, as opposed to "Create thread anonymously") silently drops eventdate/eventtim…
docs/plans/prepared_thread_event_fields/prepared_thread_event_fields_step2_feature_description.md Plans Plans and history
-
prepared_thread_event_fields_step3_development_plan.md
Waiting for "Approved Step 3" before branching and starting Step 4.
docs/plans/prepared_thread_event_fields/prepared_thread_event_fields_step3_development_plan.md Plans Plans and history
-
prepared_thread_event_fields_step4_implementation_summary.md
docs/plans/prepared_thread_event_fields/prepared_thread_event_fields_step4_implementation_summary.md Plans Plans and history
-
Private message chat refinement Step 1 solution assessment
Looks good, please merge into main and write Step 1 of the next one.
docs/plans/private_message_chat_refinement/private_message_chat_refinement_step1_solution_assessment.md Plans Plans and history
-
Private message chat refinement Step 2 feature description
Tall message cards and a large composer make conversations cumbersome.
docs/plans/private_message_chat_refinement/private_message_chat_refinement_step2_feature_description.md Plans Plans and history
-
Private message chat refinement Step 3 development plan
docs/plans/private_message_chat_refinement/private_message_chat_refinement_step3_development_plan.md Plans Plans and history
-
Private message chat refinement Step 4 implementation summary
docs/plans/private_message_chat_refinement/private_message_chat_refinement_step4_implementation_summary.md Plans Plans and history
-
Private Message Composite-User Composer: Step 1 Solution Assessment
We want private messages to be encrypted for every approved key in a composed profile, and we want the private message form to be available on the /user/xyz pa…
docs/plans/private_message_composite_user_composer/private_message_composite_user_composer_step1_solution_assessment.md Plans Plans and history
-
Private Message Composite-User Composer: Step 2 Feature Description
/user/<username> represents an approved composite user but does not offer the private-message form available from an individual approved profile.
docs/plans/private_message_composite_user_composer/private_message_composite_user_composer_step2_feature_description.md Plans Plans and history
-
Private Message Composite-User Composer: Step 3 Development Plan
docs/plans/private_message_composite_user_composer/private_message_composite_user_composer_step3_development_plan.md Plans Plans and history
-
Private Message Composite-User Composer: Step 4 Implementation Summary
docs/plans/private_message_composite_user_composer/private_message_composite_user_composer_step4_implementation_summary.md Plans Plans and history
-
Private Message Conversations: Step 1 Solution Assessment
Great job!
docs/plans/private_message_conversations/private_message_conversations_step1_solution_assessment.md Plans Plans and history
-
Private Message Conversations: Step 2 Feature Description
Inbox and Sent divide a two-party exchange into separate lists, preventing members from reading the exchange or replying in context.
docs/plans/private_message_conversations/private_message_conversations_step2_feature_description.md Plans Plans and history
-
Private Message Conversations: Step 3 Development Plan
docs/plans/private_message_conversations/private_message_conversations_step3_development_plan.md Plans Plans and history
-
Private Message Conversations: Step 4 Implementation Summary
docs/plans/private_message_conversations/private_message_conversations_step4_implementation_summary.md Plans Plans and history
-
Private message conversation list Step 1 solution assessment
Please go ahead.
docs/plans/private_message_conversation_list/private_message_conversation_list_step1_solution_assessment.md Plans Plans and history
-
Private message conversation list Step 2 feature description
Inbox and Sent repeat messages, hide older counterparts, and lack a New message action.
docs/plans/private_message_conversation_list/private_message_conversation_list_step2_feature_description.md Plans Plans and history
-
Private message conversation list Step 3 development plan
docs/plans/private_message_conversation_list/private_message_conversation_list_step3_development_plan.md Plans Plans and history
-
Private message conversation list Step 4 implementation summary
docs/plans/private_message_conversation_list/private_message_conversation_list_step4_implementation_summary.md Plans Plans and history
-
Private message history Step 2 feature description
Conversations expose only their newest 25 messages, leaving older history unreachable.
docs/plans/private_message_history/private_message_history_step2_feature_description.md Plans Plans and history
-
Private message history Step 3 development plan
docs/plans/private_message_history/private_message_history_step3_development_plan.md Plans Plans and history
-
Private message history Step 4 implementation summary
docs/plans/private_message_history/private_message_history_step4_implementation_summary.md Plans Plans and history
-
browser_journey_results.json
docs/plans/private_message_history_sync/evidence/browser_journey_results.json Plans Plans and history
-
lock_probe_results.json
docs/plans/private_message_history_sync/evidence/lock_probe_results.json Plans Plans and history
-
release_verification_results.json
docs/plans/private_message_history_sync/evidence/release_verification_results.json Plans Plans and history
-
storage_challenge_assessment.json
docs/plans/private_message_history_sync/evidence/storage_challenge_assessment.json Plans Plans and history
-
Private message history sync: how it works and how to operate it
Related: requirements · plan · implementation and evidence · storage findings · sender-assistance implementation.
docs/plans/private_message_history_sync/private_message_history_sync_rollout.md Plans Plans and history
-
Private message history synchronization Step 1 solution assessment
Storage and synchronization findings record the infrastructure review and local lock probe.
docs/plans/private_message_history_sync/private_message_history_sync_step1_solution_assessment.md Plans Plans and history
-
Private message history synchronization Step 2 feature description
Storage and synchronization findings record the infrastructure review and local lock probe.
docs/plans/private_message_history_sync/private_message_history_sync_step2_feature_description.md Plans Plans and history
-
Private message history synchronization Step 3 development plan
Storage and synchronization findings record the infrastructure review and local lock probe.
docs/plans/private_message_history_sync/private_message_history_sync_step3_development_plan.md Plans Plans and history
-
Private message history synchronization Step 4 implementation summary
Branch: feature/private-message-history-sync.
docs/plans/private_message_history_sync/private_message_history_sync_step4_implementation_summary.md Plans Plans and history
-
Private message history synchronization storage findings
The user selected a separate private database for history-sync transfers and metadata after reviewing the storage choices.
docs/plans/private_message_history_sync/private_message_history_sync_storage_findings.md Plans Plans and history