zenmemes Platform Docs

Documents

• Folder: docs ×
• Clear all

1,712 documents

Search unavailable. Retry or refresh the library.

1. v3_terminal_operator_ui_step2_feature_description.md

   The growing ./v3 command surface makes routine status checks and safe private-configuration changes hard to discover, while configuration source and secret han…

   docs/plans/backlog/v3_terminal_operator_ui_step2_feature_description.md Plans Plans and history

2. v3_terminal_operator_ui_step3_development_plan.md

   docs/plans/backlog/v3_terminal_operator_ui_step3_development_plan.md Plans Plans and history

3. v3_terminal_operator_ui_step4_implementation_summary.md

   docs/plans/backlog/v3_terminal_operator_ui_step4_implementation_summary.md Plans Plans and history

4. Backup feature flags — Railspike debug log

   Debug mode: enabled; host root marker file present; no workflow override.

   docs/plans/backup_feature_flags/backup_feature_flags_debug_log.md Plans Plans and history

5. backup_feature_flags_step1_solution_assessment.md

   Effort study: railspike-effort / v3/backupfeatureflags; host ledger

   docs/plans/backup_feature_flags/backup_feature_flags_step1_solution_assessment.md Plans Plans and history

6. backup_feature_flags_step2_feature_description.md

   Effort study: railspike-effort / v3/backupfeatureflags; host ledger

   docs/plans/backup_feature_flags/backup_feature_flags_step2_feature_description.md Plans Plans and history

7. backup_feature_flags_step3_development_plan.md

   Effort study: railspike-effort / v3/backupfeatureflags; host ledger

   docs/plans/backup_feature_flags/backup_feature_flags_step3_development_plan.md Plans Plans and history

8. backup_feature_flags_step4_implementation_summary.md

   Effort study: railspike-effort / v3/backupfeatureflags; ledger

   docs/plans/backup_feature_flags/backup_feature_flags_step4_implementation_summary.md Plans Plans and history

9. Railspike debug log — backup_page_redesign

   Mode source: .railspikedebugon present at project root (new workflow default).

   docs/plans/backup_page_redesign/backup_page_redesign_debug_log.md Plans Plans and history

10. Step 1: Solution Assessment — Backup Page Redesign

    We need to redesign the backup page to have images as a separate thing.

    docs/plans/backup_page_redesign/backup_page_redesign_step1_solution_assessment.md Plans Plans and history

11. Step 2: Feature Description — Backup Page Redesign

    Approved direction: Step 1 Option A (two sections by backup type) with a download table in each section.

    docs/plans/backup_page_redesign/backup_page_redesign_step2_feature_description.md Plans Plans and history

12. Step 3: Development Plan — Backup Page Redesign

    Reply Approved Step 3 to start implementation on a feature branch.

    docs/plans/backup_page_redesign/backup_page_redesign_step3_development_plan.md Plans Plans and history

13. backup_page_redesign_step4_implementation_summary.md

    Branch: feature/backuppageredesign, based on feature/featureflagchangepages (unmerged; it also changes instance.php).

    docs/plans/backup_page_redesign/backup_page_redesign_step4_implementation_summary.md Plans Plans and history

14. Board Filters And Sorts Plan v1

    Add Activity-style sections to the Board page so users can switch between useful thread subsets and sort orders without leaving /.

    docs/plans/board_filters_and_sorts_plan_v1.md Plans Plans and history

15. bookmarklets_page_redesign_step1_solution_assessment.md

    Please review bookmarkletsdesign.txt and also imagine you're a UX/UI designer at Apple, Airbnb, or Stripe, and you're tasked with redesigning this page accordi…

    docs/plans/bookmarklets_page_redesign/bookmarklets_page_redesign_step1_solution_assessment.md Plans Plans and history

16. bookmarklets_page_redesign_step2_feature_description.md

    /tools/bookmarklets/ shows draggable links styled like empty input fields, with a mismatched copy button, descriptions that visually attach to the wrong button…

    docs/plans/bookmarklets_page_redesign/bookmarklets_page_redesign_step2_feature_description.md Plans Plans and history

17. bookmarklets_page_redesign_step3_development_plan.md

    docs/plans/bookmarklets_page_redesign/bookmarklets_page_redesign_step3_development_plan.md Plans Plans and history

18. bookmarklets_page_redesign_step4_implementation_summary.md

    docs/plans/bookmarklets_page_redesign/bookmarklets_page_redesign_step4_implementation_summary.md Plans Plans and history

19. bookmarklet_one_line_copy_step1_solution_assessment.md

    Can you please check if this request has already been implemented:

    docs/plans/bookmarklet_one_line_copy/bookmarklet_one_line_copy_step1_solution_assessment.md Plans Plans and history

20. bookmarklet_one_line_copy_step2_feature_description.md

    Bookmarklets currently offer drag-to-save links without a convenient way to copy their source onto one line for qutebrowser.

    docs/plans/bookmarklet_one_line_copy/bookmarklet_one_line_copy_step2_feature_description.md Plans Plans and history

21. bookmarklet_one_line_copy_step3_development_plan.md

    Each stage ends with its verification evidence and Step 4 summary update in a stage-scoped commit before further work.

    docs/plans/bookmarklet_one_line_copy/bookmarklet_one_line_copy_step3_development_plan.md Plans Plans and history

22. bookmarklet_one_line_copy_step4_implementation_summary.md

    docs/plans/bookmarklet_one_line_copy/bookmarklet_one_line_copy_step4_implementation_summary.md Plans Plans and history

23. Remove “Browser identity ready”

    Report: original comment · parent post · full thread.

    docs/plans/browser_identity_ready_minimal_triage_2026-10-21.md Plans Plans and history

24. Triage: remove “Browser identity ready”

    Date: October 21, 2026.

    docs/plans/browser_identity_ready_triage_2026-10-21.md Plans Plans and history

25. Browser Private Key Restore Step 1 Solution Assessment

    Users need a frontend path to restore a browser-held posting identity from private key material copied from another browser without sending private keys to the…

    docs/plans/browser_private_key_restore/browser_private_key_restore_step1_solution_assessment.md Plans Plans and history

26. Case insensitive tags Railspike debug log

    Debug mode enabled by the user alongside Step 2 approval; recorded in Step 2 and inherited by Step 3.

    docs/plans/case_insensitive_tags/case_insensitive_tags_debug_log.md Plans Plans and history

27. case_insensitive_tags_step1_solution_assessment.md

    As a user and admin, I want these tags to be case-insensitive.

    docs/plans/case_insensitive_tags/case_insensitive_tags_step1_solution_assessment.md Plans Plans and history

28. case_insensitive_tags_step2_feature_description.md

    Capitalization separates otherwise identical tags in /tags/ and can make linked tag pages unreachable.

    docs/plans/case_insensitive_tags/case_insensitive_tags_step2_feature_description.md Plans Plans and history

29. case_insensitive_tags_step3_development_plan.md

    Every stage includes tests and a summary in its commit before the next begins.

    docs/plans/case_insensitive_tags/case_insensitive_tags_step3_development_plan.md Plans Plans and history

30. case_insensitive_tags_step4_implementation_summary.md

    Feature branch: feature/case-insensitive-tags.

    docs/plans/case_insensitive_tags/case_insensitive_tags_step4_implementation_summary.md Plans Plans and history

31. Checkout overview debug log

    No supported findings.

    docs/plans/checkout_overview/checkout_overview_debug_log.md Plans Plans and history

32. checkout_overview_step1_solution_assessment.md

    Effort study: railspike-effort / v3/checkoutoverview; standing P2 enrollment.

    docs/plans/checkout_overview/checkout_overview_step1_solution_assessment.md Plans Plans and history

33. checkout_overview_step2_feature_description.md

    Effort study: railspike-effort / v3/checkoutoverview; standing P2 enrollment.

    docs/plans/checkout_overview/checkout_overview_step2_feature_description.md Plans Plans and history

34. checkout_overview_step3_development_plan.md

    Effort study: railspike-effort / v3/checkoutoverview; standing P2 enrollment.

    docs/plans/checkout_overview/checkout_overview_step3_development_plan.md Plans Plans and history

35. checkout_overview_step4_implementation_summary.md

    Effort study: railspike-effort / v3/checkoutoverview; ledger, v1/R1/P2, Codex single exposed rater.

    docs/plans/checkout_overview/checkout_overview_step4_implementation_summary.md Plans Plans and history

36. terminal_acceptance.txt

    docs/plans/checkout_overview/terminal_acceptance.txt Plans Plans and history

37. timing_acceptance.json

    docs/plans/checkout_overview/timing_acceptance.json Plans Plans and history

38. timing_acceptance_initial.json

    docs/plans/checkout_overview/timing_acceptance_initial.json Plans Plans and history

39. Hosting chouse.club on this framework — plan v1

    zenmemes.com as two separate communities (separate content, separate

    docs/plans/chouse_club_hosting_plan_v1.md Plans Plans and history

40. Chouse Production Release — Step 1: Solution Assessment

    The existing placeholder chouse site must be replaced by this codebase on

    docs/plans/chouse_production_readiness/chouse_production_readiness_step1_solution_assessment.md Plans Plans and history