-
theme_directive_step3_development_plan.md
Effort study: railspike-effort / v3/themedirective; host ledger.
docs/plans/theme_directive/theme_directive_step3_development_plan.md Plans Plans and history
-
theme_directive_step4_implementation_summary.md
Effort study: railspike-effort / v3/themedirective; host ledger.
docs/plans/theme_directive/theme_directive_step4_implementation_summary.md Plans Plans and history
-
Thread List Card: Duplicate Preview Line — Step 1 Solution Assessment
On the board/tag listing pages, each thread's preview line is literally the body's first line (strtok($body, "\n")), so it repeats the title whenever a poster'…
docs/plans/thread_card_remove_preview/thread_card_remove_preview_step1_solution_assessment.md Plans Plans and history
-
Step 2: Feature Description — Omit Duplicate Preview Line from Thread List Card
On the board and tag listing pages, each thread's preview line is the body's first line, so it repeats the title whenever a poster's first body line matches th…
docs/plans/thread_card_remove_preview/thread_card_remove_preview_step2_feature_description.md Plans Plans and history
-
Step 3: Development Plan — Omit Duplicate Preview Line from Thread List Card
Reply Approved Step 3 to create the feature branch and begin Step 4.
docs/plans/thread_card_remove_preview/thread_card_remove_preview_step3_development_plan.md Plans Plans and history
-
Step 4: Implementation Summary — Omit Duplicate Preview Line from Thread List Card
docs/plans/thread_card_remove_preview/thread_card_remove_preview_step4_implementation_summary.md Plans Plans and history
-
Compact view for thread listings
Users currently see thread lists (board/tag pages) as full cards: title, meta line, full body-preview text, and reply count, with generous spacing between card…
docs/plans/thread_compact_view/thread_compact_view_plan_v1.md Plans Plans and history
-
Thread Compact View Step 3 Development Plan
Plus toggle-button styling consistent with .theme-toggle.
docs/plans/thread_compact_view/thread_compact_view_step3_development_plan.md Plans Plans and history
-
Addendum: Move the merged-run byline to the last post, not the first
Follows on from the original continuation-merge feature docs:
docs/plans/thread_continuation_merge/thread_continuation_merge_meta_position_addendum_v1.md Plans Plans and history
-
Step 1: Solution Assessment — Merge Same-Author Reply Chains on Thread Pages
Quick same-author replies within a short window each render as a full, separately-bordered post-card with repeated byline/actions, so one continuous piece of w…
docs/plans/thread_continuation_merge/thread_continuation_merge_step1_solution_assessment.md Plans Plans and history
-
Step 2: Feature Description — Merge Same-Author Reply Chains on Thread Pages
On thread pages, a burst of quick same-author replies each renders as its own full card (repeated byline, repeated action row), so one continuous piece of writ…
docs/plans/thread_continuation_merge/thread_continuation_merge_step2_feature_description.md Plans Plans and history
-
Step 3: Development Plan — Merge Same-Author Reply Chains on Thread Pages
docs/plans/thread_continuation_merge/thread_continuation_merge_step3_development_plan.md Plans Plans and history
-
Step 4: Implementation Summary — Merge Same-Author Reply Chains on Thread Pages
docs/plans/thread_continuation_merge/thread_continuation_merge_step4_implementation_summary.md Plans Plans and history
-
Thread Inline Reply Form Plan V1
Add a compact reply composer directly on thread pages so a reader can start replying without leaving the thread.
docs/plans/thread_inline_reply_form_plan_v1.md Plans Plans and history
-
Thread-like Activity — Railspike debug log
No supported findings.
docs/plans/thread_like_activity/thread_like_activity_debug_log.md Plans Plans and history
-
thread_like_activity_step1_solution_assessment.md
Effort study: railspike-effort, cycle v3/threadlikeactivity; standing P2 enrollment; ledger.
docs/plans/thread_like_activity/thread_like_activity_step1_solution_assessment.md Plans Plans and history
-
thread_like_activity_step2_feature_description.md
Effort study: railspike-effort, cycle v3/threadlikeactivity; standing P2 enrollment; ledger.
docs/plans/thread_like_activity/thread_like_activity_step2_feature_description.md Plans Plans and history
-
thread_like_activity_step3_development_plan.md
Effort study: railspike-effort, cycle v3/threadlikeactivity; ledger.
docs/plans/thread_like_activity/thread_like_activity_step3_development_plan.md Plans Plans and history
-
thread_like_activity_step4_implementation_summary.md
Effort study: railspike-effort, v3/threadlikeactivity; ledger.
docs/plans/thread_like_activity/thread_like_activity_step4_implementation_summary.md Plans Plans and history
-
Thread Root Card Consolidation Plan v1
The thread page currently renders two adjacent cards for the root post:
docs/plans/thread_root_card_consolidation_plan_v1.md Plans Plans and history
-
Thread Root Card: Omit Duplicate Title Line — Step 1 Solution Assessment
When a thread's title matches the first line of its root post body, the thread page shows that line twice — once as the <h1> and again as the first line of the…
docs/plans/thread_root_card_dedupe_title_first_line/thread_root_card_dedupe_title_first_line_step1_solution_assessment.md Plans Plans and history
-
Step 2: Feature Description — Omit Duplicate Title Line from Thread Root Card
When a thread's title is identical to the first line of its root post body, the thread page shows that line twice: once as the <h1> title and again as the firs…
docs/plans/thread_root_card_dedupe_title_first_line/thread_root_card_dedupe_title_first_line_step2_feature_description.md Plans Plans and history
-
Step 3: Development Plan — Omit Duplicate Title Line from Thread Root Card
Reply Approved Step 3 to create the feature branch and begin Step 4.
docs/plans/thread_root_card_dedupe_title_first_line/thread_root_card_dedupe_title_first_line_step3_development_plan.md Plans Plans and history
-
Step 4: Implementation Summary — Omit Duplicate Title Line from Thread Root Card
docs/plans/thread_root_card_dedupe_title_first_line/thread_root_card_dedupe_title_first_line_step4_implementation_summary.md Plans Plans and history
-
Step 2: Feature Description — Thread Root Card Meta Reorder
On the thread page, the root post's byline, labels, and reply count sit between the title and the body, pushing the body away from the title it belongs to and…
docs/plans/thread_root_card_meta_reorder/thread_root_card_meta_reorder_step2_feature_description.md Plans Plans and history
-
Step 3: Development Plan — Thread Root Card Meta Reorder
Reply Approved Step 3 to create the feature branch and begin Step 4.
docs/plans/thread_root_card_meta_reorder/thread_root_card_meta_reorder_step3_development_plan.md Plans Plans and history
-
Step 4: Implementation Summary — Thread Root Card Meta Reorder
docs/plans/thread_root_card_meta_reorder/thread_root_card_meta_reorder_step4_implementation_summary.md Plans Plans and history
-
Step 2: Feature Description — Remove Reply Count from Thread Root Card
The root post's reply count (N replies/1 reply) on the thread page adds a metadata line that isn't needed there — the actual replies are visible right below on…
docs/plans/thread_root_card_remove_reply_count/thread_root_card_remove_reply_count_step2_feature_description.md Plans Plans and history
-
thread_url_cleanup_implementation.md
Scope: Small direct change requested by the maintainer
docs/plans/thread_url_cleanup_implementation.md Plans Plans and history
-
Thywill site option Railspike debug log
Debug mode: enabled.
docs/plans/thywill_site_option_debug_log.md Plans Plans and history
-
Thywill feature support and gaps in v3
Reviewed 2026-10-15.
docs/plans/thywill_site_option_review.md Plans Plans and history
-
thywill_site_option_step1_solution_assessment.md
Please review ~/thywill and write a report on which features v3 already supports and which would have to be added on in order for thywill to become a new site…
docs/plans/thywill_site_option_step1_solution_assessment.md Plans Plans and history
-
Step 1: Solution Assessment — Toolbar Identity Status Indicator
As a user of the Forte interface, I want to know what my identity status is.
docs/plans/toolbar_identity_status/toolbar_identity_status_step1_solution_assessment.md Plans Plans and history
-
Step 2: Feature Description — Toolbar Identity Status Indicator
Viewers of the Forte interface have no visual cue telling them whether they're currently recognized as a logged-in identity or browsing as a guest.
docs/plans/toolbar_identity_status/toolbar_identity_status_step2_feature_description.md Plans Plans and history
-
Step 3: Development Plan — Toolbar Identity Status Indicator
docs/plans/toolbar_identity_status/toolbar_identity_status_step3_development_plan.md Plans Plans and history
-
Step 4: Implementation Summary — Toolbar Identity Status Indicator
User mocked up a restyled indicator live in the browser during review and specified the exact markup/CSS/JS; applied as given, with two implementation details…
docs/plans/toolbar_identity_status/toolbar_identity_status_step4_implementation_summary.md Plans Plans and history
-
Tools bar at the bottom of tool pages
Cycle: v3/toolsnavbottom; Mode: one-shot; Record/index: this file, plans index
docs/plans/tools_nav_bottom/tools_nav_bottom_one_shot.md Plans Plans and history
-
top_five_media_embeds_step1_solution_assessment.md
Great job, please write a step 1 for addressing the top 5 for now
docs/plans/top_five_media_embeds/top_five_media_embeds_step1_solution_assessment.md Plans Plans and history
-
top_five_media_embeds_step2_feature_description.md
Members cannot reliably share the five prioritized media URL types within discussions.
docs/plans/top_five_media_embeds/top_five_media_embeds_step2_feature_description.md Plans Plans and history
-
top_five_media_embeds_step3_development_plan.md
Each stage targets one hour; split oversized work before implementation and replan above eight stages/one day.
docs/plans/top_five_media_embeds/top_five_media_embeds_step3_development_plan.md Plans Plans and history