-
Step 3: Development Plan — Feature Flags Page Organization
docs/plans/feature_flags_organization/feature_flags_organization_step3_development_plan.md Plans Plans and history
-
Step 4: Implementation Summary — Feature Flags Page Organization
docs/plans/feature_flags_organization/feature_flags_organization_step4_implementation_summary.md Plans Plans and history
-
Step 1: Solution Assessment — Feature Flags Page Redesign
The /tools/feature-flags/ page uses a fixed-width table that wraps flag keys mid-word and doesn't scale past a handful of flags, and the reviewed spec (docs/fe…
docs/plans/feature_flags_redesign/feature_flags_redesign_step1_solution_assessment.md Plans Plans and history
-
Step 2: Feature Description — Feature Flags Page Redesign
The /tools/feature-flags/ page's fixed-width table wraps flag keys mid-word and shows four always-visible columns per flag, which doesn't scale as the flag cou…
docs/plans/feature_flags_redesign/feature_flags_redesign_step2_feature_description.md Plans Plans and history
-
Step 3: Development Plan — Feature Flags Page Redesign
docs/plans/feature_flags_redesign/feature_flags_redesign_step3_development_plan.md Plans Plans and history
-
Step 4: Implementation Summary — Feature Flags Page Redesign
docs/plans/feature_flags_redesign/feature_flags_redesign_step4_implementation_summary.md Plans Plans and history
-
Feature Flags security-review cleanup — Railspike debug log
No supported findings.
docs/plans/feature_flags_security_review_cleanup/feature_flags_security_review_cleanup_debug_log.md Plans Plans and history
-
index.html
docs/plans/feature_flags_security_review_cleanup/feature_flags_security_review_cleanup_mockups/index.html Plans Plans and history
-
feature_flags_security_review_cleanup_step1_solution_assessment.md
Effort study: railspike-effort / v3/featureflagssecurityreviewcleanup · Ledger
docs/plans/feature_flags_security_review_cleanup/feature_flags_security_review_cleanup_step1_solution_assessment.md Plans Plans and history
-
Access history in User Access
Effort study: railspike-effort / v3/featureflagssecurityreviewcleanup · Ledger
docs/plans/feature_flags_security_review_cleanup/feature_flags_security_review_cleanup_step2_feature_description.md Plans Plans and history
-
Access history — development plan
Effort study: railspike-effort / v3/featureflagssecurityreviewcleanup · Ledger
docs/plans/feature_flags_security_review_cleanup/feature_flags_security_review_cleanup_step3_development_plan.md Plans Plans and history
-
Access history — implementation
Effort study: railspike-effort / v3/featureflagssecurityreviewcleanup · Ledger
docs/plans/feature_flags_security_review_cleanup/feature_flags_security_review_cleanup_step4_implementation_summary.md Plans Plans and history
-
Feature flags toolbar — Railspike debug log
docs/plans/feature_flags_toolbar/feature_flags_toolbar_debug_log.md Plans Plans and history
-
Feature flags search and status toolbar
The grouped /tools/feature-flags/ page still requires scanning every flag to find a setting or inspect enabled, overridden, or locked flags.
docs/plans/feature_flags_toolbar/feature_flags_toolbar_step2_feature_description.md Plans Plans and history
-
feature_flags_toolbar_step3_development_plan.md
docs/plans/feature_flags_toolbar/feature_flags_toolbar_step3_development_plan.md Plans Plans and history
-
Implementation summary
docs/plans/feature_flags_toolbar/feature_flags_toolbar_step4_implementation_summary.md Plans Plans and history
-
Step 1: Solution Assessment — Signed Feature-Flag Changes
We need to record who changed a feature flag and sign the request.
docs/plans/feature_flag_change_attribution/feature_flag_change_attribution_step1_solution_assessment.md Plans Plans and history
-
Step 2: Feature Description — Signed Feature-Flag Changes
Feature-flag changes currently prove only that a root-approved session reached the server.
docs/plans/feature_flag_change_attribution/feature_flag_change_attribution_step2_feature_description.md Plans Plans and history
-
Step 3: Development Plan — Signed Feature-Flag Changes
docs/plans/feature_flag_change_attribution/feature_flag_change_attribution_step3_development_plan.md Plans Plans and history
-
Step 4: Implementation Summary — Signed Feature-Flag Changes
docs/plans/feature_flag_change_attribution/feature_flag_change_attribution_step4_implementation_summary.md Plans Plans and history
-
Railspike debug log — feature_flag_change_pages
Mode source: .railspikedebugon present at project root (new workflow default).
docs/plans/feature_flag_change_pages/feature_flag_change_pages_debug_log.md Plans Plans and history
-
Step 1: Solution Assessment — Feature-Flag Change Pages
OK, there's no pages for feature change items, I guess?
docs/plans/feature_flag_change_pages/feature_flag_change_pages_step1_solution_assessment.md Plans Plans and history
-
Step 2: Feature Description — Feature-Flag Change Pages
Approved direction: Step 1 Option B (dedicated change page; legacy items fall back to their commit page).
docs/plans/feature_flag_change_pages/feature_flag_change_pages_step2_feature_description.md Plans Plans and history
-
Step 3: Development Plan — Feature-Flag Change Pages
Reply Approved Step 3 to start implementation on a feature branch.
docs/plans/feature_flag_change_pages/feature_flag_change_pages_step3_development_plan.md Plans Plans and history
-
feature_flag_change_pages_step4_implementation_summary.md
Branch: feature/featureflagchangepages, based on fix/backup-page-tools-nav-order (unmerged; carries the Backup layout fix that Stage 5 depends on).
docs/plans/feature_flag_change_pages/feature_flag_change_pages_step4_implementation_summary.md Plans Plans and history
-
Step 1: Solution Assessment — Feature Flag Lock Explanation
The /tools/feature-flags/ page hides why a flag is locked in a hover-only tooltip, and conflates that data-source lock with a separate, unshown root-approval p…
docs/plans/feature_flag_lock_explanation/feature_flag_lock_explanation_step1_solution_assessment.md Plans Plans and history
-
Step 2: Feature Description — Feature Flag Lock Explanation
The feature flags page doesn't explain why a flag is locked (reason is hidden in a hover-only tooltip) and shows mutable flags as apparently editable to viewer…
docs/plans/feature_flag_lock_explanation/feature_flag_lock_explanation_step2_feature_description.md Plans Plans and history
-
Step 3: Development Plan — Feature Flag Lock Explanation
docs/plans/feature_flag_lock_explanation/feature_flag_lock_explanation_step3_development_plan.md Plans Plans and history
-
Step 4: Implementation Summary — Feature Flag Lock Explanation
docs/plans/feature_flag_lock_explanation/feature_flag_lock_explanation_step4_implementation_summary.md Plans Plans and history
-
Step 1: Solution Assessment — Feature Flag Write Triggers Spurious Read-Model Rebuild
LocalWriteService::setFeatureFlag() commits a new git SHA but never updates the read model's stored repositoryhead metadata, so the very next request to hit Ap…
docs/plans/feature_flag_readmodel_rebuild_fix/feature_flag_readmodel_rebuild_fix_step1_solution_assessment.md Plans Plans and history
-
Step 2: Feature Description — Feature Flag Write Triggers Spurious Read-Model Rebuild
Feature-flag writes commit a new canonical-record SHA to git but never update the read model's stored repositoryhead metadata, so Application::ensureReadModel(…
docs/plans/feature_flag_readmodel_rebuild_fix/feature_flag_readmodel_rebuild_fix_step2_feature_description.md Plans Plans and history
-
Step 3: Development Plan — Feature Flag Write Triggers Spurious Read-Model Rebuild
docs/plans/feature_flag_readmodel_rebuild_fix/feature_flag_readmodel_rebuild_fix_step3_development_plan.md Plans Plans and history
-
Step 4: Implementation Summary — Feature Flag Read-Model Rebuild Fix
docs/plans/feature_flag_readmodel_rebuild_fix/feature_flag_readmodel_rebuild_fix_step4_implementation_summary.md Plans Plans and history
-
Firefox Console Warnings Cause Notes
This note documents the Firefox console warnings observed while loading the local app at http://127.0.0.1:8000.
docs/plans/firefox_console_warnings_causes_v1.md Plans Plans and history
-
Forte Activity parity — Railspike debug log
Debug mode: enabled from the project marker for this new workflow.
docs/plans/forte_activity_parity/forte_activity_parity_debug_log.md Plans Plans and history
-
forte_activity_parity_step2_feature_description.md
Forte Activity and the default Activity page share activity data but differ in controls and presentation of evidence.
docs/plans/forte_activity_parity/forte_activity_parity_step2_feature_description.md Plans Plans and history
-
forte_activity_parity_step3_development_plan.md
docs/plans/forte_activity_parity/forte_activity_parity_step3_development_plan.md Plans Plans and history
-
forte_activity_parity_step4_implementation_summary.md
Status: All three implementation stages complete and locally verified.
docs/plans/forte_activity_parity/forte_activity_parity_step4_implementation_summary.md Plans Plans and history
-
Forte Board Memory-Safe Thread Loading Step 1 Solution Assessment
Please help me debug this issue with the Forte interface:
docs/plans/forte_board_memory_safe_thread_loading/forte_board_memory_safe_thread_loading_step1_solution_assessment.md Plans Plans and history
-
Forte Board Memory-Safe Thread Loading Step 2 Feature Description
The Forte board includes every thread body and reply tree in its initial, hidden content pane.
docs/plans/forte_board_memory_safe_thread_loading/forte_board_memory_safe_thread_loading_step2_feature_description.md Plans Plans and history