Commit Graph
22 Commits
Author SHA1 Message Date
DongHyeonka bdc32b6198 docs: PRODUCT.md의 예제 제거 주장을 드릴 범위에 맞춘다 (14-04)
PRODUCT.md가 "예제 기능과 라우트는 지울 수 있고, 예제 화면에만 있는
디자인은 남지 않는다"고 적었다. 실제 제거 드릴(test:sample-removal)은
참조 기능만 지운다. 예제 라우트 4개와 홈은 기본 구성이라 남는다. 이
주장을 믿고 예제 화면에 디자인을 넣으면 제품 빌드에 그대로 남는다.

PRODUCT.md를 드릴 범위대로 고쳤다. 접근성 수동 검토의 근거를 지워도
되는 SPEC.md에서 docs/accessibility/manual-checklist.md로 바꿨다.
README의 "복사 뒤 지워도 되는 파일" 표에 PRODUCT.md를 CLAUDE.md처럼
"제품 것으로 바꾼다"로 넣었다. 예제 화면을 지울 수 있게 만드는 일은
별도 선택이라 하지 않았다(0929/14-03).

위험: 문서만 바뀐다.
검증: deletable-history-documents 테스트 통과, verify:documentation
PASS_SCOPED.
2026-11-01 18:56:56 +09:00
donghyeon-kaandClaude Opus 5.5 70f4ff8717 fix(scale): keep the ceiling rationale next to the baseline, not in a review document (11-04, 00-02, 14-05)
The growth test read docs/reviews/, which the removal fixtures do not copy and
README lets a project delete, so three removal checks failed with ENOENT. The
rationale now lives in config/scale/feature-shape-ceilings.json and a guard
test keeps code from reading the deletable history documents.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-27 14:03:03 +09:00
donghyeon-kaandClaude Opus 5.5 81d2b84c7b docs: correct drifted counts and state what verify:documentation checks (14-07)
The gate count and the reference-feature LOC table were hand-typed and
drifted from the code, so they are removed; the LOC table now names the
files and the command that measures them. .env.example pointed to
layers.md for runtime profiles, which never described them; it now points
to the README section that does. ci-quality-gates.md lists the three
things DOCUMENTATION_READY checks, so the gate name is not read as a
general documentation-accuracy guarantee. The route list (③) and the
README config location (④) were already fixed by 14-03 and 13-15.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-27 13:34:53 +09:00
DongHyeonkaandClaude Opus 5.5 6ddb08e0b6 docs: index docs/ by current contract, target design and history (14-05)
Current contracts, target designs and work history shared one tree with no
index. docs/README.md sorts them, names the files gates read, and marks the
history folders; README lists what a copy can delete. SPEC.md and tasks/ stay
in place because this round still uses them (D-16).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-26 00:07:58 +09:00
DongHyeonkaandClaude Opus 5.5 2cb3838367 docs(readme): add the support scope table and status word map (14-06)
What is default, optional, experimental or unsupported (SSR among them) was
spread over the recipe catalog and the capability ledger, each with its own
status words. README now has one tier table, a map from every status word to
a tier, and the browser versions the build targets and the tests run on.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-26 00:07:58 +09:00
DongHyeonkaandClaude Opus 5.5 1cb09e4210 docs(template): add a CHANGELOG and the copied-project update procedure (14-04)
A copy had no way to learn that a fix shipped or which files to take. The
CHANGELOG marks security and contract changes with their paths; README says
where to record the origin commit, how to cherry-pick or diff a fix and who
classifies a template defect. The v0.2.0 tag is added after integration.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-26 00:07:49 +09:00
DongHyeonkaandClaude Opus 5.5 edf44a2253 fix(config): keep public/config.json equal to the local profile (F-5, 13-15)
public/config.json is the copy dev serves and nothing compared it with
config/runtime/local.json. A unit test now requires it to equal what a local
build writes, and sample removal drops the feature override from it too.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-26 00:05:06 +09:00
DongHyeonkaandClaude Opus 5.5 5810461256 fix(docs): check README runtime variables in verify:documentation (13-15)
The unit test read README.md, which removal fixtures do not copy, so
test:sample-removal failed. verify:documentation now requires README to name
every build and deploy variable the generator and admission read.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-25 23:35:11 +09:00
DongHyeonkaandClaude Opus 5.5 2ba880c7e2 docs(config): document runtime profiles, deploy variables and precedence in README (13-15)
README said runtime settings live in public/config.json, which the build
replaces with config/runtime/<profile>.json, and named none of APP_PROFILE,
RUNTIME_*, VITE_BUILD_ID, RELEASE_ID or RELEASE_TARGET. A unit test now
requires README to name every variable the generator and admission read.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-25 23:26:20 +09:00
DongHyeonkaandClaude Opus 5.5 a263d8cc4a fix(release): run the hosting header gate on the deployed release, fixture is UNVERIFIED (13-05)
FE-GATE-019 ran before the release existed and passed by comparing the declared
headers with a copy of themselves. The fixture result is now UNVERIFIED, the
gate runs in the production stage after deployment, and the live probe
requests the entry script the served index.html names (D-14).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-25 23:03:23 +09:00
DongHyeonkaandClaude Opus 5.5 7f889a6d83 fix(release): record unobserved runbook drill verdicts as UNVERIFIED (11-01, 13-03)
Drills held constant true verdicts and read public/ placeholders, so they
passed with no build or with JS assets deleted. They now check the local dist,
mark boot, live traffic and provider steps UNVERIFIED (exit 3), and FE-GATE-016
is retired because it repeated FE-GATE-025's FE-RB-005 drill.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-25 22:15:59 +09:00
DongHyeonkaandClaude Opus 5.5 7298275271 ci: move the signed manual a11y review to release gate FE-GATE-028 (08-06)
The signed review is per release candidate, so the merge gate could never pass.
FE-GATE-009 now checks only the record format; the checked-in records are
source-controlled evidence, not command output.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-25 22:07:53 +09:00
DongHyeonkaandClaude Opus 5.5 b8cc5d4995 ci: run the workflow on pushes to main and state the local merge check (12-01)
The push trigger listed only develop, while main is the integration
branch. README now says the host may not run Actions and gives the local
loop over the 13 merge gates. Enabling Actions and required checks on the
host stays with the repository owner (U-1).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-09-25 21:38:22 +09:00
donghyeon-ka 5cc41467ae refactor: 프론트 템플릿 리펙토링 2026-09-18 15:16:58 +09:00
DongHyeonkaandClaude Opus 5 3ea3397691 fix: make the architecture and documentation rules say what is actually true
Three boundaries the layer contract declares had no executable rule behind
them, so the code drifted across all three while every gate stayed green.

`src/contracts` reached back up into `src/application` for the shared `Result`
carrier and the compatibility predicate. Neither package owned the shared
vocabulary and the dependency pointed both ways. Both now live in contracts —
the lower package — and application re-exports them, so no caller moves.

A concrete adapter was not supposed to depend on another concrete adapter, but
only adapter-to-presentation was enforced, and `diagnostics` imported a guard
out of `telemetry`. The guard belongs to neither, so it moved to the adapter
kernel. Stating the rule needed the checker to resolve `$1` in a `to` pattern
against the importing module's own directory; the alternative is one rule per
adapter group, which silently stops covering a group the moment one is added.

Product assembly leaks out of bootstrap: generic presentation reads the
installed-feature registries. That is a real refactor, so the rule freezes the
exact set of modules doing it today rather than pretending it is fixed — a new
edge fails. The two remaining open edges are named in the config, not silent.

Each rule was verified by introducing the violation it forbids and confirming
the gate rejects it.

The documentation drifted the same way. README and the manual accessibility
checklist both said six routes while ten were registered, which left the
platform overview and three reference-resource screens outside the declared
manual review scope without anyone deciding they should be. The scope is now
derived from the route registry by `verify:documentation`, so the sentence
cannot outlive the registry again. The review ledger also named a canonical
path that does not exist in this tree; it is upstream provenance, and it now
says so instead of looking like a broken repository reference.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-15 17:23:10 +09:00
DongHyeonka c6da03369c refactor: 리펙토링 2026-08-01 19:39:59 +09:00
donghyeon-ka 6c52cdb916 feat: 기능 추가 과정중 2026-07-30 15:58:20 +09:00
donghyeon-ka 0fed35586a feat: establish TypeScript-aware frontend tooling 2026-07-26 13:41:23 +09:00
donghyeon-ka 68342e25ce docs: audit frontend platform capabilities 2026-07-26 02:09:06 +09:00
donghyeon-ka 236909be64 test: harden starter experience quality contract 2026-07-26 00:28:09 +09:00
donghyeon-ka c5e218d37a feat: orchestrate blocking frontend quality gates 2026-07-25 21:39:04 +09:00
donghyeon.kang 91ae42a2a7 Initial commit 2026-07-23 04:11:08 +00:00