-
mitrapclub_events_experience_step2_feature_description.md
A mitrapclub event announcement (date, location, optional link) has no structured fields and renders identically to an ordinary discussion thread — a visitor s…
docs/plans/mitrapclub_events_experience/mitrapclub_events_experience_step2_feature_description.md Plans Plans and history
-
mitrapclub_events_experience_step3_development_plan.md
Waiting for "Approved Step 3" before branching and starting Step 4.
docs/plans/mitrapclub_events_experience/mitrapclub_events_experience_step3_development_plan.md Plans Plans and history
-
mitrapclub_events_experience_step4_implementation_summary.md
docs/plans/mitrapclub_events_experience/mitrapclub_events_experience_step4_implementation_summary.md Plans Plans and history
-
mitrapclub_media_embeds_step1_solution_assessment.md
Please write Step 1 of @docs/fdp/FEATUREDEVELOPMENTPROCESS.md for the MIT Rap Club website.
docs/plans/mitrapclub_media_embeds/mitrapclub_media_embeds_step1_solution_assessment.md Plans Plans and history
-
mitrapclub_media_embeds_step2_feature_description.md
mitrapclub threads can only ever contain plain escaped text, so a YouTube or Instagram link posted by a member renders as a bare URL instead of a recognizable…
docs/plans/mitrapclub_media_embeds/mitrapclub_media_embeds_step2_feature_description.md Plans Plans and history
-
mitrapclub_media_embeds_step3_development_plan.md
docs/plans/mitrapclub_media_embeds/mitrapclub_media_embeds_step3_development_plan.md Plans Plans and history
-
mitrapclub_media_embeds_step4_implementation_summary.md
docs/plans/mitrapclub_media_embeds/mitrapclub_media_embeds_step4_implementation_summary.md Plans Plans and history
-
mitrapclub_media_embeds_fetched_titles_step1_solution_assessment.md
I think I found one issue.
docs/plans/mitrapclub_media_embeds_fetched_titles/mitrapclub_media_embeds_fetched_titles_step1_solution_assessment.md Plans Plans and history
-
mitrapclub_media_embeds_fetched_titles_step2_feature_description.md
When a mitrapclub thread has no subject and its body is a bare recognized YouTube/Instagram URL, it should show the linked content's real title and still rende…
docs/plans/mitrapclub_media_embeds_fetched_titles/mitrapclub_media_embeds_fetched_titles_step2_feature_description.md Plans Plans and history
-
mitrapclub_media_embeds_fetched_titles_step3_development_plan.md
docs/plans/mitrapclub_media_embeds_fetched_titles/mitrapclub_media_embeds_fetched_titles_step3_development_plan.md Plans Plans and history
-
mitrapclub_media_embeds_fetched_titles_step4_implementation_summary.md
docs/plans/mitrapclub_media_embeds_fetched_titles/mitrapclub_media_embeds_fetched_titles_step4_implementation_summary.md Plans Plans and history
-
mitrapclub_media_embeds_inline_player_step1_solution_assessment.md
When I post a YouTube link, I see this: "▶ YouTube https://www.youtube.com/watch?v=..." but there is no embedded video.
docs/plans/mitrapclub_media_embeds_inline_player/mitrapclub_media_embeds_inline_player_step1_solution_assessment.md Plans Plans and history
-
mitrapclub_media_embeds_inline_player_step2_feature_description.md
Cycle 5's link-preview card confirms a post contains a YouTube or Instagram link but never plays or previews it richly, so a viewer must always leave the threa…
docs/plans/mitrapclub_media_embeds_inline_player/mitrapclub_media_embeds_inline_player_step2_feature_description.md Plans Plans and history
-
mitrapclub_media_embeds_inline_player_step3_development_plan.md
docs/plans/mitrapclub_media_embeds_inline_player/mitrapclub_media_embeds_inline_player_step3_development_plan.md Plans Plans and history
-
mitrapclub_media_embeds_inline_player_step4_implementation_summary.md
docs/plans/mitrapclub_media_embeds_inline_player/mitrapclub_media_embeds_inline_player_step4_implementation_summary.md Plans Plans and history
-
mitrapclub_structural_identity_step1_solution_assessment.md
Please write Step 1 for the next change.
docs/plans/mitrapclub_structural_identity/mitrapclub_structural_identity_step1_solution_assessment.md Plans Plans and history
-
mitrapclub_structural_identity_step2_feature_description.md
The mitrapclub profile still carries three pieces of shared, not-club-specific config as-is: the generic forum nav (labels + the generic /tools/ operator page…
docs/plans/mitrapclub_structural_identity/mitrapclub_structural_identity_step2_feature_description.md Plans Plans and history
-
mitrapclub_structural_identity_step3_development_plan.md
Waiting for "Approved Step 3" before branching and starting Step 4.
docs/plans/mitrapclub_structural_identity/mitrapclub_structural_identity_step3_development_plan.md Plans Plans and history
-
mitrapclub_structural_identity_step4_implementation_summary.md
docs/plans/mitrapclub_structural_identity/mitrapclub_structural_identity_step4_implementation_summary.md Plans Plans and history
-
MIT Rap Club — de-genericize + extend checklist
Raw candidate list, not yet scoped or decided — input for the next FDP round
docs/plans/mitrapclub_theme_and_features_checklist.md Plans Plans and history
-
mit_rap_club_website_step1_solution_assessment.md
I would like to create a website for the MIT Rap Club.
docs/plans/mit_rap_club_website/mit_rap_club_website_step1_solution_assessment.md Plans Plans and history
-
mit_rap_club_website_step2_feature_description.md
MIT Rap Club has no online home; this app already supports branded community instances (chouse, qdb) but has no siteid, theme, or content configured for the cl…
docs/plans/mit_rap_club_website/mit_rap_club_website_step2_feature_description.md Plans Plans and history
-
mit_rap_club_website_step3_development_plan.md
Waiting for "Approved Step 3" before branching and starting Step 4.
docs/plans/mit_rap_club_website/mit_rap_club_website_step3_development_plan.md Plans Plans and history
-
mit_rap_club_website_step4_implementation_summary.md
docs/plans/mit_rap_club_website/mit_rap_club_website_step4_implementation_summary.md Plans Plans and history
-
mobile_compose_keyboard_step1_solution_assessment.md
Source-Thread: thread-20261031051903-0e8e7df4
docs/plans/mobile_compose_keyboard/mobile_compose_keyboard_step1_solution_assessment.md Plans Plans and history
-
mobile_compose_keyboard_step2_feature_description.md
Source-Thread: thread-20261031051903-0e8e7df4
docs/plans/mobile_compose_keyboard/mobile_compose_keyboard_step2_feature_description.md Plans Plans and history
-
mobile_compose_keyboard_step3_development_plan.md
Source-Thread: thread-20261031051903-0e8e7df4
docs/plans/mobile_compose_keyboard/mobile_compose_keyboard_step3_development_plan.md Plans Plans and history
-
mobile_compose_keyboard_step4_implementation_summary.md
Effort study: v3/mobilecomposekeyboard · ledger (standing P2 enrollment)
docs/plans/mobile_compose_keyboard/mobile_compose_keyboard_step4_implementation_summary.md Plans Plans and history
-
Multi-redemption invites — Railspike debug log
Source: docs/railspike/docs/workflow/step1solutionassessment.md, options and review gate.
docs/plans/multi_redemption_invites/multi_redemption_invites_debug_log.md Plans Plans and history
-
Superseded scope v1 — multi-redemption invites
Historical record: superseded by the user’s backend-only direction on 2026-10-31 UTC.
docs/plans/multi_redemption_invites/multi_redemption_invites_scope_v1_history.md Plans Plans and history
-
multi_redemption_invites_step1_solution_assessment.md
Effort study: railspike-effort / v3/multiredemptioninvites; P2 ledger
docs/plans/multi_redemption_invites/multi_redemption_invites_step1_solution_assessment.md Plans Plans and history
-
multi_redemption_invites_step2_feature_description.md
Effort study: railspike-effort / v3/multiredemptioninvites; P2 ledger
docs/plans/multi_redemption_invites/multi_redemption_invites_step2_feature_description.md Plans Plans and history
-
multi_redemption_invites_step3_development_plan.md
Effort study: railspike-effort / v3/multiredemptioninvites; ledger
docs/plans/multi_redemption_invites/multi_redemption_invites_step3_development_plan.md Plans Plans and history
-
multi_redemption_invites_step4_implementation_summary.md
Effort study: railspike-effort / v3/multiredemptioninvites; ledger
docs/plans/multi_redemption_invites/multi_redemption_invites_step4_implementation_summary.md Plans Plans and history
-
Multi-Site Refactor Checklist
Use this checklist to refactor Zenmemes, Chouse, and QDB into explicit site components before adding another design.
docs/plans/multi_site_refactor_checklist.md Plans Plans and history
-
Multi-Site Refactor P0 — Step 1: Solution Assessment
Please write Step 1 of docs/fdp/FEATUREDEVELOPMENTPROCESS.md for P0 of docs/plans/multisiterefactorchecklist.md.
docs/plans/multi_site_refactor_p0/multi_site_refactor_p0_step1_solution_assessment.md Plans Plans and history
-
Multi-Site Refactor P0 — Step 2: Feature Description
Profile identity is only partly declared in SiteProfileRegistry; browser/offline identifiers and the profile-specific static-output rule are duplicated elsewhe…
docs/plans/multi_site_refactor_p0/multi_site_refactor_p0_step2_feature_description.md Plans Plans and history
-
Multi-Site Refactor P0 — Step 3: Development Plan
docs/plans/multi_site_refactor_p0/multi_site_refactor_p0_step3_development_plan.md Plans Plans and history
-
Multi-Site Refactor P0 — Step 4: Implementation Summary
docs/plans/multi_site_refactor_p0/multi_site_refactor_p0_step4_implementation_summary.md Plans Plans and history
-
Multi-Site Refactor P1 — Step 1: Solution Assessment
Please update the refactor checklist, merge into main, and prepare for P1.
docs/plans/multi_site_refactor_p1/multi_site_refactor_p1_step1_solution_assessment.md Plans Plans and history