Backlog: cross-reference the Automate Surveys tab's repo-only limit - #25
Merged
Conversation
Final sweep before end-of-session shutdown: confirmed every finding from today's work is actually recorded in Backlog.md (not just a commit message) — security_features's 4th state, Curate's remaining three candidates, _COCHANGE_MAX_FILES, and the DB/FS native-survey direction were all already there. One gap: the Automate 📋 Surveys tab's repo-only hardcoding (fixed to be correct-but-still-repo-only in c2dd682) wasn't cross-referenced from "Unify survey launching", so someone reading only that entry wouldn't know the tab is a second, smaller piece blocked on the same native-survey work rather than something separate to chase. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011tEc1hLba3p63ZaqcSWAPv Signed-off-by: Dan Wolfson <dan.wolfson@pdr-associates.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The last unmerged commit on any branch. One file, 9 added lines, documentation only.
re/survey-flowswas left 46 commits behindmainafter everything else merged, holding a single backlog note that never made it into #24's range.What it records
Automate's 📋 Surveys sub-tab — schedule a whole Survey Definition on a cadence — is hardcoded to repo end to end: the frontend requires a selected repo before rendering, and
_saveSurveyScheduleposts to/api/schedules/repo/...unconditionally.The backend is already ready.
list_definitions()'sresource_typewas fixed on 2026-08-30 to be read per document rather than hardcoded"repo". What is missing is anything to show: database and filesystem Survey Definitions do not exist yet, and they are expected to arrive by the native-survey route (other_engine_handlers) rather than as new RE-authored definitions.So it is two small pieces once that path is proven, not one — the definitions themselves, and generalising the tab's resource selector. Recorded rather than guessed at, and cross-referenced from the entry that tracks the database/filesystem survey-unification gap.
Why it is worth a PR of its own
It closes out the branch. With this merged, every branch in the repo is either
mainor fully contained in it.Also worth stating because the shape recurs in this repo:
git diff origin/main..origin/re/survey-flowsreports 81 files, +1174/−1920, which reads as a catastrophic revert. That is a two-dot diff comparing tips — it shows everythingmainhas that this branch lacks as deletions, because the branch is 46 commits behind. The merge base tells the truth:git diff $(git merge-base ...)..origin/re/survey-flowsis one file, 9 lines. A merge brings the second, not the first.🤖 Generated with Claude Code