Commit Graph
6 Commits
Author SHA1 Message Date
DongHyeonka c524a21463 test(browser): 다운로드 시험이 브라우저가 파일을 받은 뒤 런타임을 정리한다
이 시험은 BOUNDED_OBJECT_URL 다운로드로 Blob을 앵커에 넘기고, 브라우저의
download 이벤트를 기다린다. 그런데 deliver()가 handoff를 마치자마자
.finally(() => runtime.dispose())가 돈다. dispose()는 살아 있는 object URL을
즉시 해제한다(평소에는 30초 유예를 두지만 dispose는 정리라서 예외다).
WebKit은 앵커 클릭 뒤 다운로드를 비동기로 시작하므로, URL이 먼저 해제되면
다운로드가 시작되지 않는다. 그러면 download 이벤트 없이 30초 시험 제한으로
떨어진다. 2026-11-12 capability 실행 4번 중 1번 WebKit에서 이렇게 떨어졌다.

런타임을 전역에 두고, 다운로드 내용을 다 읽은 뒤 페이지에서 dispose한다.
제품의 해제 규칙(30초 유예, dispose 즉시 해제)은 바꾸지 않는다. 실제
화면에서 런타임은 다운로드 직후 버려지지 않는다.

검증: WebKit에서 --repeat-each=20으로 20회 모두 통과. 고치기 전 같은
조건 10회에서는 이 시험이 실패하지 않아 재현율은 낮다. 근거는 위 실패
로그와 dispose의 즉시 해제 코드(download-delivery-adapter.ts)다.
2026-11-12 18:38:30 +09:00
DongHyeonka 84afff4d75 test(browser): 막힌 IndexedDB 업그레이드 시험이 지나간 BLOCKED 상태도 본다
이 시험은 다른 탭이 v1을 연 채로 v2를 열게 하고, 런타임 상태가
BLOCKED가 되는지 본다. BLOCKED는 blockedTimeoutMs(500 ms) 동안만
있다가 CLOSED/NOT_OPENED로 바뀐다. 시험은 getStatus()를 바깥에서
expect.poll로 묻는데, poll 간격이 100·250·500·1000 ms로 벌어진다.
blocked 이벤트가 늦게 오면 그 500 ms가 두 번의 물음 사이에 지나가고,
시험은 뒤따른 CLOSED만 보다가 5초 뒤 떨어진다. WebKit에서 이 시험
하나가 10회 중 1회 이렇게 떨어졌다.

런타임의 subscribeStatus로 페이지 안에서 상태가 바뀔 때마다 기록하고,
그 기록에 BLOCKED가 있는지 본다. 재시도나 timeout을 늘려 덮지 않는다.
나머지 검증(열기 실패의 BLOCKED 오류, 막은 탭이 닫힌 뒤 늦은 연결을
닫음, 삭제)은 그대로다.

검증: WebKit에서 --repeat-each로 고치기 전 10회 중 1회 실패. 고친 뒤
20회 모두 통과(같은 실행의 다운로드 시험 20회 포함 40건).
2026-11-12 18:38:30 +09:00
DongHyeonka c80320dfc7 chore: sync the frontend template from ebea300 to af3d8e6
Carries 359 template commits, tag v0.2.0 plus one documentation commit: the
generator-built feature index with its app, bounded-context and feature
declarations, the src/platform kernel and scale tooling, the 2026-09-24 src
review fixes, and the 2026-09-25 maturity review round with its CHANGELOG
[보안]/[계약] rows. 691 of the 824 template paths are applied, 85 of them
merged with product changes; 127 are not carried.

Product identity is unchanged: name, version 0.1.0, routes, design and the
TechLog domain.

Three decisions worth naming. TechLog stays composed directly, as the last
two syncs recorded; its directory carries a NOT_INSTALLED marker that says so,
and every installed-* composer takes the template's projection with TechLog
added on top. The reference sample is no longer installed: the template now
installs a feature only through feature-module.ts and context-routes.ts,
which load the screens this product deleted, so its three operations, six
schemas and one topic leave the registries, recorded as registry change
evidence. And AppRouter mounts the platform and TechLog routes only; the
template's bounded-context route gateway waits for a generator-installed
feature.

Required fixes: readSubject on the BFF session owner (without it every HTTP
Studio session would close as integration-failed), zod through the facade in
nine TechLog files, noUnusedLocals, and public/config.json written out to
match the local profile. Derived baselines were recomputed after reproducing
both sides' values: CI contract 101 commands / 106 references / 141
artifacts, gate shape c9adcf85; registry approval 2dc6c3a3; the runtime
config schema baseline equals the schema at 8210d48.

Verified here: types, lint, architecture, adapter inventory, CI contract,
i18n, design system, diagnostics, browser security, dev release manifest,
TechLog contract and build pass; 220 component, 155 integration, 15
contract, 418 TechLog, 43 reference-feature, 18 recipe and 46
release-coherence tests pass, and 2381 of 2383 unit tests. Reproduced at
8210d48 first and unchanged: check:registries (byte-identical),
test:runtime-schema, verify:documentation. Brought by the template and
escalated rather than suppressed: check:request-fanout on TechLog's cursor
pagination, check:remediation-ledger (fails upstream too), the shared-chunk
hash test, and the registry-dependent sample removal and second-feature
tests. Playwright suites were not run.

Full record, the five open questions and the follow-ups in
docs/operations/template-sync-2026-09-29.md.

(cherry picked from commit b2170cf265dea45dc9cc05d3c61e627e97f31cdb)
2026-11-12 08:28:54 +09:00
DongHyeonkaandClaude Opus 5 afde2b1da1 chore: sync the frontend template from 5434760 to ebea300
Carries 21 template commits: the shared IndexedDB connection/transaction
kernel and the four runtimes moved onto it, the adapter barrel boundary and
the architecture rule that enforces it, the feature adapter contribution
model, `feature-http-binding`, the split of several oversized test files,
and the release identity now derived from the package name.

Product identity is unchanged. The three hard-coded `tech-log-frontend/…`
verifier ids are gone because the template derives them from the package
name and this package is `tech-log-frontend`.

Two decisions worth naming. The platform HTTP executor is the template's
verbatim — it now takes the installed contract so a feature's types flow
through the binding — and TechLog's four gateways, which address operations
by id, reach it through one adapter at the composition root instead of being
rewritten here. And the three derived CI baselines were recomputed from the
merged `config/ci/gates.json` rather than taken from either side: 94 command
definitions, 106 references, 141 artifacts, gate shape `629e5898…`. The
method was checked by first reproducing the pre-merge values from the
pre-merge file.

Verified here: types, lint, architecture, adapter inventory, CI contract,
design system, diagnostics, remediation ledger, browser security and build
all pass; 1789 unit, 152 component, 415 TechLog, 102 integration, 19
reference-feature, 17 recipe and 7 contract tests pass. Five gates stay
red and every one was reproduced at b297d65 first: `check:i18n`,
`check:registries`, `test:runtime-schema`, `verify:documentation` and
`test:sample-removal`.

Full decision record, including what was deliberately not carried and the
five open follow-ups, in `docs/operations/template-sync-2026-09-21.md`.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-09-21 16:31:05 +09:00
DongHyeonkaandClaude Opus 5 bdee07a93b chore: sync the frontend template from a0fbafb to 5434760
Carries eight template commits: the provider sandbox actually running, release
admission to a named environment, the product feature manifest with its runtime
kill switch, architecture and documentation rules that match what is enforced,
the removability fixtures, and the browser, visual and performance evidence.

Product identity is unchanged. `package.json` keeps `tech-log-frontend` and the
catalog keeps the Tech Log naming; the home page was not in the delta. The
visual baselines are this product's own — the template's were excluded from the
transplant and these were regenerated here, where the only difference is the
platform overview's new product-feature section.

What this repository gains operationally: `config/runtime/{local,development,
staging,production}.json` with `FE-GATE-027` refusing an artifact whose runtime
document does not match the environment it is being admitted to, and
`FEATURE_OVERRIDES` for taking an installed feature out of service without a
rebuild.

Verified here: eight gates green, build green, visual 5/5, and 1,858 of 1,859
tests in the suites that do not need a sandbox — the one failure passes in
isolation and is a jsdom lazy-chunk timeout under parallel load. The provider
suites cannot run on this machine at all: `kernel.apparmor_restrict_unprivileged
_userns=1` makes `bwrap --unshare-net` fail, reproducible without any code from
either repository.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-15 21:34:19 +09:00
DongHyeonka 40107eec84 chore: initialize from frontend template 4dc033c 2026-08-13 18:23:26 +09:00