docs: accept A01 visual baseline
This commit is contained in:
+7
-9
@@ -3,18 +3,16 @@
|
||||
- Source visual truth: `docs/design/screens/A01-启动登录引导-栅格验收-412x915.png`
|
||||
- Target state: `412 × 915`, agreement unchecked.
|
||||
- Static contract: passed on 2026-07-13.
|
||||
- Runtime screenshot: first capture reviewed on 2026-07-13; second capture pending after the ornamental-asset calibration.
|
||||
- Runtime screenshot: current `412 × 915` capture accepted by the user on 2026-07-13 as the A-01 visual baseline.
|
||||
|
||||
## Evidence
|
||||
|
||||
- The first `412 × 915` runtime capture confirms that the red-header height, divider width, both button frames and registration-entry height are close to the reference.
|
||||
- The same capture shows the seal too high, title clouds too wide, both button content groups too far right, and an agreement row that is too wide and high.
|
||||
- The second calibration replaces the incorrect shared cloud artwork with three dedicated transparent assets: button corner flourish, divider center knot and title-side cloud. It also aligns the agreement checkbox and copy on one non-wrapping center line.
|
||||
- The accepted `412 × 915` capture preserves a continuous paper-and-ink background, complete button frames, the intended entry hierarchy and a single-line agreement row.
|
||||
- The user explicitly accepted this capture as the current A-01 visual baseline; no additional visual tuning is authorized in this phase.
|
||||
|
||||
## Remaining runtime evidence
|
||||
## Accepted scope
|
||||
|
||||
- [P1] Capture the unchecked A-01 page at `412 × 915` in HBuilderX or Android, without browser chrome, after the ornamental-asset calibration and compare it against the source at the same scale.
|
||||
- [P1] Capture `320 × 568` after scrolling to confirm the agreement row and safe area are not clipped.
|
||||
- Confirm that selecting the agreement enables only the existing A-02 login route; the other entries remain local prepared-state prompts.
|
||||
- This result accepts A-01's current visual baseline only.
|
||||
- Existing local behavior remains unchanged: agreement selection enables the A-02 login route; other entries remain local prepared-state prompts.
|
||||
|
||||
final result: runtime evidence pending
|
||||
final result: passed
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
# A-01 启动 / 登录引导设计记录
|
||||
|
||||
> 状态:A-01 文字注册入口方案、四尺寸静态验收与本地 UI 已完成;A-02 双标签本地 UI 已完成。协议页去向、A-03 至 A-06 的设计、认证接口与 Android 运行时验收仍未完成,D2 继续进行中。
|
||||
> 状态:A-01 文字注册入口方案、四尺寸静态验收、本地 UI 与 412 × 915 运行时视觉基准已完成并获用户验收;A-02 双标签本地 UI 已完成。协议页去向、A-03 至 A-06 的设计、认证接口与 Android 全尺寸回归验收仍未完成,D2 继续进行中。
|
||||
>
|
||||
> 本页设计事实的唯一归档位置为本文件。旧的 `2026-07-13-a01-login-guide-design.md` 与 `2026-07-13-a01-login-guide.md` 仅保留为失效历史,不可作为实现或推进下一页的依据。
|
||||
|
||||
@@ -71,12 +71,12 @@
|
||||
- 静态设计验收已覆盖 320 × 568、360 × 640、360 × 800、412 × 915;四个尺寸均保持两个大按钮与单行文字注册入口。`412 × 915` 图是 A-01 协议未勾选状态的运行时像素基准;A-01 本地页以真实 DOM 还原其层级和比例,运行时仍须截图对比,不得以整图页面替代。
|
||||
- 归档文件:[320 × 568](screens/A01-启动登录引导-栅格验收-320x568.png)、[360 × 640](screens/A01-启动登录引导-栅格验收-360x640.png)、[360 × 800](screens/A01-启动登录引导-栅格验收-360x800.png)、[412 × 915](screens/A01-启动登录引导-栅格验收-412x915.png)。
|
||||
- 此结论只验证设计稿与固定栅格,不替代 uni-app 页面实现后的 Android 运行时验收。
|
||||
- 仍未确定《家谱用户协议》与《隐私政策》的最终页面去向及返回路径;在这两页完成设计前,A-01 不得标记为完整设计完成。
|
||||
- 2026-07-13 用户已验收当前连续背景、完整按钮边框与单行协议区的 `412 × 915` 运行截图,A-01 当前视觉基准标记为完成;本轮不再授权继续微调视觉细节。
|
||||
- 页面实现阶段仍须按本记录在 Android 实机或同等运行环境复核四个尺寸的安全区、滚动与文字折行。
|
||||
- 2026-07-13 已按 412 × 915 参考图完成第二轮子元素校准:已补齐按钮四角透明角花、分隔线中心中结、标题独立祥云,并将协议复选框与文案改为单行居中对齐。未取得第二轮同尺寸运行时截图确认前不得标记 A-01 完成。
|
||||
- A-01 的协议最终页面去向及 A-03 至 A-06 的设计仍未完成;这些后续范围不影响当前 A-01 视觉基准的验收结论。
|
||||
|
||||
## 5. 推进约束
|
||||
|
||||
- `A-01` 与 `A-02` 的本地 UI 已按本记录及实现合同落地;A-02 的最终效果稿与 Android 运行时验收仍待补齐,不能据此推进 A-03。
|
||||
- 只有确定协议页面的最终去向,并完成本文件第 4 节所述的运行时验收后,A-01 才能进入“设计完成”状态。
|
||||
- 当前 A-01 视觉基准已完成;后续只在协议页面、认证接口或新页面范围获得明确授权后继续推进。
|
||||
- 用户已于 2026-07-13 授权落地 A-01 欢迎入口与 A-02 双标签登录页的本地 UI;仍不接接口、不执行真实登录、不改 Android 打包配置。实现细节的唯一所有者见 `docs/superpowers/specs/2026-07-13-a01-a02-static-ui-implementation-design.md`。
|
||||
|
||||
Reference in New Issue
Block a user