zenmemes Platform Docs

Documents

• Folder: docs ×
• Clear all

2,569 documents

Search unavailable. Retry or refresh the library.

1. acceptance_evidence.json

   docs/plans/startup_dependency_recovery/acceptance_evidence.json Plans Plans and history

2. Startup dependency recovery acceptance

   Verified on 2026-10-13.

   docs/plans/startup_dependency_recovery/acceptance_evidence.md Plans Plans and history

3. 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 Plans and history

4. 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 Plans and history

5. 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 Plans and history

6. startup_dependency_recovery_step3_development_plan.md

   docs/plans/startup_dependency_recovery/startup_dependency_recovery_step3_development_plan.md Plans Plans and history

7. 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 Plans and history

8. Status frontend target — Railspike debug log

   docs/plans/status_frontend_target/status_frontend_target_debug_log.md Plans Plans and history

9. 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 Plans and history

10. 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 Plans and history

11. Status frontend target — Step 3 development plan

    docs/plans/status_frontend_target/status_frontend_target_step3_development_plan.md Plans Plans and history

12. Status frontend target — implementation summary

    Planning commit: 1f7e49d1.

    docs/plans/status_frontend_target/status_frontend_target_step4_implementation_summary.md Plans Plans and history

13. Debug log: status_frozen_frontend_diagnosis

    docs/plans/status_frozen_frontend_diagnosis/status_frozen_frontend_diagnosis_debug_log.md Plans Plans and history

14. 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 Plans and history

15. 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 Plans and history

16. Status: Frozen Frontend Diagnosis — Step 3 Development Plan

    docs/plans/status_frozen_frontend_diagnosis/status_frozen_frontend_diagnosis_step3_development_plan.md Plans Plans and history

17. 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 Plans and history

18. 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 Plans and history

19. 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 Plans and history

20. status_lock_wait_notice_step3_development_plan.md

    docs/plans/status_lock_wait_notice/status_lock_wait_notice_step3_development_plan.md Plans Plans and history

21. status_lock_wait_notice_step4_implementation_summary.md

    docs/plans/status_lock_wait_notice/status_lock_wait_notice_step4_implementation_summary.md Plans Plans and history

22. tags_index_memory_fix.txt

    docs/plans/tags_index_memory_fix.txt Plans Plans and history

23. Task Queue Candidate Catalog

    This catalog identifies every operational or background-style workflow found in the current application that could plausibly be run by the durable cron task qu…

    docs/plans/task_queue_candidate_catalog.md Plans Plans and history

24. Testing self-approval — Railspike debug log

    No supported findings.

    docs/plans/testing_self_approval/testing_self_approval_debug_log.md Plans Plans and history

25. testing_self_approval_step1_solution_assessment.md

    As a maintainer who often runs new temporary localhost instances, I want an easy, one-click, "approve current account" button that I can use only during testin…

    docs/plans/testing_self_approval/testing_self_approval_step1_solution_assessment.md Plans Plans and history

26. testing_self_approval_step2_feature_description.md

    Maintainers repeatedly need to approve their browser account on temporary localhost instances.

    docs/plans/testing_self_approval/testing_self_approval_step2_feature_description.md Plans Plans and history

27. testing_self_approval_step3_development_plan.md

    Deliver the approved marker-gated Account Key action: create ignored .test-self-approval, start localhost normally, authenticate the browser account, click onc…

    docs/plans/testing_self_approval/testing_self_approval_step3_development_plan.md Plans Plans and history

28. testing_self_approval_step4_implementation_summary.md

    docs/plans/testing_self_approval/testing_self_approval_step4_implementation_summary.md Plans Plans and history

29. test_runner_elapsed_time_step1_solution_assessment.md

    I want the test runner to output the elapsed time with each line so that it's easier for me to track, please.

    docs/plans/test_runner_elapsed_time/test_runner_elapsed_time_step1_solution_assessment.md Plans Plans and history

30. test_runner_elapsed_time_step2_feature_description.md

    Test results currently show no timing until the later slow-test report, making it difficult to follow overall progress or identify the cost of each completed t…

    docs/plans/test_runner_elapsed_time/test_runner_elapsed_time_step2_feature_description.md Plans Plans and history

31. test_runner_elapsed_time_step3_development_plan.md

    docs/plans/test_runner_elapsed_time/test_runner_elapsed_time_step3_development_plan.md Plans Plans and history

32. test_runner_elapsed_time_step4_implementation_summary.md

    docs/plans/test_runner_elapsed_time/test_runner_elapsed_time_step4_implementation_summary.md Plans Plans and history

33. Test run history retention

    log table) and retention size (X runs / Y days / both)

    docs/plans/test_run_history_retention_plan_v1.md Plans Plans and history

34. Step 1: Solution Assessment — Test Run Summary Report

    tests/run.php currently prints per-test PASS/FAIL lines and a slow-test report, but gives no run summary (pass/fail counts) and no way to tell which failures a…

    docs/plans/test_run_summary_report/test_run_summary_report_step1_solution_assessment.md Plans Plans and history

35. Step 2: Feature Description — Test Run Summary Report

    tests/run.php prints per-test PASS/FAIL lines and a slow-test list, but no run summary — you can't see totals at a glance, or whether a failure is new or has b…

    docs/plans/test_run_summary_report/test_run_summary_report_step2_feature_description.md Plans Plans and history

36. Step 3: Development Plan — Test Run Summary Report

    docs/plans/test_run_summary_report/test_run_summary_report_step3_development_plan.md Plans Plans and history

37. Step 4: Implementation Summary — Test Run Summary Report

    docs/plans/test_run_summary_report/test_run_summary_report_step4_implementation_summary.md Plans Plans and history

38. Text backup start latency — Railspike diagnostics

    Debug mode: enabled; inherited from project marker for this new cycle

    docs/plans/text_backup_start_latency_debug_log.md Plans Plans and history

39. text_backup_start_latency_step1_solution_assessment.md

    Effort study: railspike-effort / v3/textbackupstartlatency; ledger; standing P2 enrollment

    docs/plans/text_backup_start_latency_step1_solution_assessment.md Plans Plans and history

40. theme_directive debug log

    No supported findings.

    docs/plans/theme_directive/theme_directive_debug_log.md Plans Plans and history