docs(status): staging 인증 경계를 현행화 - #23
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: d122453898
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| `develop` 검증본은 OpenAI Sites의 비공개 배포와 Firebase Hosting 공개 배포로 게시합니다. | ||
| 현재 공모전 staging 번들은 소방서 선택 후 발급되는 제한 파일럿 서명 세션으로 BFF에 | ||
| 연결하고, 운영 연결 실패를 fixture로 자동 대체하지 않습니다. |
There was a problem hiding this comment.
When an operator follows this README, the new signed-session description conflicts with lines 79 and 95, which still say that staging sets VITE_ENABLE_AUTH=false and sends credentials: omit (and the runbook repeats that guidance), even though .env.staging sets the flag to true. Leaving those instructions unchanged can produce a staging build that omits the session cookie and receives 401s, so update the earlier configuration and validation sections as part of this authentication-boundary refresh.
Useful? React with 👍 / 👎.
| 서비스 `chemicheck119-fe-develop`은 예비 주소로 유지합니다. staging 번들은 인증을 | ||
| 활성화하며 물질검색·사고분석·음성 전사는 서명 세션을 거쳐 BFF의 Live 경로를 호출합니다. |
There was a problem hiding this comment.
For builds made from the checked-in .env.staging, speech does not call this Live path: that file never sets VITE_ENABLE_SPEECH_API=true, while src/api/config.ts requires the value to be exactly true, causing the control to remain hidden and transcribeIncidentAudio to reject with NOT_READY. Describe the result as a backend-only smoke, or enable the flag after the required deployment validation, rather than claiming the staging bundle currently sends speech requests.
Useful? React with 👍 / 👎.
1 participant
변경 내용
pinTag가 Backend 배포를 자동 추적하지 않는 운영 경계와 최신 pinned revision을 기록했습니다.검증
git diff --check통과pnpm check수행 예정주장 제한
Closes #22