chore: normalize sibling workspace orchestration - #36
Open
udgover wants to merge 12 commits into
Open
Conversation
Make development and real-stack Compose builds use the canonical sibling repositories, remove stale nested Git links, and align manual and CI bootstrap paths.
Replace the tracked runtime environment with a safe template, generate the local authentication secret idempotently, and make the production smoke check run on pull requests with deterministic cleanup.
Keep 18080 as the default while letting parallel local services select another host port. Derive the harness URL from the exported port and cover both paths with a Docker-free harness contract test plus Compose rendering assertions.
Create local and CI environment files with owner-only permissions, enforce that mode for existing files, and prevent read-only GitHub tokens from persisting in checkout metadata passed to Docker build contexts.
Keep the static frontend probe and also require Nginx to reach the API OpenAPI endpoint before the production smoke job passes.
Discard token-bearing create-user stdout while preserving stderr and failure status, emit only a non-sensitive success message, and guard the behavior with a sentinel contract assertion.
Match the current frontend accessibility contract by clicking the result list item that owns Vuetify selection, rather than the nested details control that stops propagation.
Run shell syntax, ShellCheck, integration-port, and production-environment contracts before the production smoke stack, and bound the job to thirty minutes.
Force EntitySelector retries to issue a changed search value, and navigate observables through the exact details path verified during the retry so pending table refreshes cannot detach the target before navigation.
…ce-layout # Conflicts: # integration-tests/playwright/tests/entity-indicator-link.spec.ts
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.
Summary
yetiandyeti-feeds-frontendrepositoriesValidation
INTEGRATION_FRONTEND_PORT=18081External limitation
GitHub reports the
Docker prod testworkflow (ID 77289175) asdisabled_inactivity. PR 36 therefore has no automated checks until a repository owner explicitly re-enables it; the full contract and real-stack matrix above was run locally.PowerShell syntax execution was unavailable on this host. The optional agents profile could not be fully rendered because no sibling
yeti-agents/.envcheckout is present; the core development model and profile declaration were validated.