Repository navigation
Complete goal-first workflow authoring and bounded runtime action choice - #1764
Merged
Paul Lizer (paullizer) merged 3 commits intoOct 14, 2026
Conversation
Fill every supported known workflow detail while preserving incomplete schedule drafts and strict execution validation. Separate document actions from source policy, add searchable workspace selection and authoritative Added timestamps, and retain bounded authorized runtime decisions across retries. Include regression coverage, SDK owner-runtime evidence and documentation for v0.261.333. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Integrate origin/paullizer-react-v2-ui while preserving goal-first workflow authoring and the incoming Ask AI handoff and secure identifier changes. Resolve the VERSION conflict with a patch bump, align related documentation and regression headers, and record the successful production build, browser, focused backend and complete Cosmos SDK validation. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Address CodeQL review with fresh normal/optimized real-module lifecycle and scoped-search authorization regressions. Preserve established deferred service dependencies rather than claiming local import relocation removes static graph cycles. Make pytest catalog fixture registration explicit and document the review disposition in v0.261.336. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Paul Lizer (paullizer)
merged commit Oct 14, 2026
9fba769
into
paullizer-react-v2-ui
12 checks passed
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
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.
Summary
0.261.333.Review focus: incomplete authoring drafts must not become executable schedules, and runtime decisions must never broaden source scopes or document IDs. Runtime choice is not an unrestricted planner and cannot create tasks or invoke external tools.
Linked issue
N/A. The user explicitly chose to continue without a new issue. This is a follow-up to merged #1761, not an update to its branch.
Release Notes & Latest Features
Is this visible to end users?
Is this admin-facing (Admin Settings, governance, deployment, config)?
Should this become a Latest Feature card?
Screenshot needed for the card?
Release notes remain unchanged: the coordinating parent is handling the optional release-note decision. Latest Feature card and card screenshot decisions are deferred; no card was added.
Version bump
application/single_app/config.pyVERSIONthird segment bumped, or not needed because this is docs-onlydeployers/version.txtbumped, or not needed becausedeployers/was not changedApplication version:
0.261.332->0.261.333. No deployer files changed.Testing / validation
Python checks used the isolated validation environment with the repository-pinned Cosmos SDK
4.9.0.npm --prefix application\v2_ui run build- passed, including TypeScript compilation and production Vite build. The existing large-chunk advisory remains.python .\scripts\check_cosmos_response_boundaries.py --run-contracts- passed, exit 0: 1,051 owners, 395 doubles, zero review gaps; 718 tests and 231 subtests passed with sockets/DNS blocked by the checker. Explicitly renewed 29 unchanged owner bodies/calls and replaced 14 stale source-only exemptions with owner-runtime SDK evidence. No checker or compatibility baseline was weakened.python -m pytest functional_tests\test_docs_app_surface_coverage.py functional_tests\test_docs_site_quality.py -q --disable-warnings --tb=short- 13 passed; regenerated surface inventory has no semantic changes.git --no-pager diff --cached --check- passed before committing.Previously completed focused regression runs passed 114 goal/task/structured checks, 139 authoring/action/File Sync checks, 285 result/selection/privacy/route checks plus 112 subtests, and 168 frozen-replay cases across isolated runs. The selected production-bundle browser runs passed 178 distinct cases, including actual 1280px desktop and 390px mobile workspace discovery. Bounded synthetic real-model evaluation passed 12/12 scenarios in 14 calls, with a largest output of 638 tokens; no production workflow was run.
The broader legacy matrix is not claimed to be fully green: obsolete source/version assertions, an old task-sequence golden, existing logging-tag inventory failures and one offline
route_backend_agents.enabled_requiredbootstrap failure predate this change. Details and before/after evidence are recorded in the fix documentation; these checks were not weakened or rewritten.Documentation
Updated the workflow guide, AI assistant/document selection feature contracts and logging reference. Added versioned fix documentation covering the contract diagnosis, runtime boundaries, validation and known baseline limitations. Release-note approval remains with the coordinator.
Security checklist
@swagger_route(security=get_auth_security())sanitize_settings_for_user()No new Flask routes or settings exposure paths were introduced. Source capture and resumed processing remain permission-fenced, and model-visible handles do not expose raw storage locators. Evaluation scripts, screenshots, logs and validation environments remain outside the repository.