Repository navigation
feat(dashboard): simplify Stage-0 interview presentation - #100
Merged
Merged
Conversation
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.
Purpose
讓第一次接觸 NAL 的面試官快速理解「模擬請求 → 安全檢查 → 允許/阻擋 → 查看證據」。首頁改以正體中文、Inline SVG 四步驟流程與並排 ALLOW/REJECT 卡片呈現,原有技術證據與英文安全標籤保留於原生 details/summary。
Scope
templates/dashboard_home.html: +197 / −273.22308734af0404c79d3242fd3ae68d9b46e4ab63.0ff961f57ac247f83ca3792be94c998401c962a0.Validation
Existing local evidence for this exact candidate:
/root/flask_ui_independent_review; author/root). No unresolved material findings.These are local validation and review results. The new PR's automatic Safe CI result must be checked separately.
Safety boundary
Results remain projected from existing Stage-0 evidence and explicitly identify the Fake Adapter. The homepage remains GET-only, with no form submission or added execution controls. No Live, Provider, or real-device execution capability is added. Day95/Day96 evidence and safety rules remain unchanged.
Stage 2 remains CLOSED. FIX-04 Deployment Acceptance remains PENDING and Inactive Runtime Binding remains NOT_ESTABLISHED. Existing npm vulnerability maintenance, including Critical findings, is not resolved by this presentation change. No Stage 3, Root Activation, or Approval Signing/Placement authorization is introduced.