Skip to content

V33 잔여 마무리 — W-4 검증 + GA Store 준비 + 식별자 정합 + 테스트 안전망 - #34

Open
yellowhama wants to merge 242 commits into
mainfrom
feat/v33-residual-finalize
Open

V33 잔여 마무리 — W-4 검증 + GA Store 준비 + 식별자 정합 + 테스트 안전망#34
yellowhama wants to merge 242 commits into
mainfrom
feat/v33-residual-finalize

Conversation

@yellowhama

@yellowhama yellowhama commented Jun 25, 2026 •
edited
Loading

Copy link
Copy Markdown
Owner

Summary

V29~V31 reinstall resilience work and the V33 residual branch are still useful, but the current release claim must stay evidence-scoped.

Area Status
WS-1 stale Yellowhama.MUSU -> blossompark.musu identifier alignment
WS-2 version coherence gate expanded to include src-tauri\Cargo.toml
WS-3 Install-MUSU.ps1 hardened for root cert/0x800B0109/elevated error display/PSCommandPath and `irm
WS-4 Store docs aligned; scripts already follow VERSION
WS-5a fleet.rs probe/fallback integration coverage
WS-5b 3-state fleet playbook corrected: relay-display is not delegated-work relay routing
WS-6 test safety net restored: cockpit-contract, meshBearer, route CI wiring
WS-7 GA EV direct signing design queued
rc.22 follow-up public install/proof channel exposes fleet-proof.ps1; hugh_second and hugh-main physical direct proof are green

Current Evidence

  • Code/test/deploy checks are green except design-gate.
  • Live public install channel verifier passed after the fleet-proof route was published: verify-musu-pro-install-channel.ps1 -Json returned ok=true, failure_count=0.
  • hugh_second packaged rc.22 proof passed: installed package 1.15.0.22, remote-usable advertised URL http://192.168.1.154:11105, direct-only online_nodes=1 at that capture point, and brain token ACL restricted.
  • hugh-main hosted proof now passed from the public command:
    • evidence file: docs/evidence/fleet-proof/1.15.0-rc.22/hugh-main-20260627T010201Z.fleet-proof.json
    • schema musu.fleet_node_proof.v1, ok=true, fail_count=0, warn_count=0
    • package blossompark.musu_1.15.0.22_x64__f5h38pf4yt4gc, installed version 1.15.0.22
    • bridge_bind_addr=0.0.0.0:4387, advertised_public_url=http://192.168.1.192:4387
    • online_nodes=2, direct_healthy_nodes=2, expected direct peer hugh_second
    • remote_cloud_warning_count=0, brain_ingest_token_acl_restricted passing
  • Follow-up musu status --json from hugh_second shows both hugh_second and hugh-main healthy via direct routes.
  • This supports the current rc.22 two-physical-machine direct proof claim. It does not prove Store readiness or real relay transport for delegated work.

Required Before Merge / Release Claim

  1. Get explicit CEO/design approval on issue Design approval request: PR #34 fleet/install UI #35.
  2. After approval, update the design status line below and include the approval comment URL.
  3. Re-run PR checks and merge only if design-gate and the product evidence both remain green.
  4. Rerun hosted fleet-proof.ps1 if the package, installer route, node identity, or release claim changes.

Docs

  • docs/PRODUCT_PURPOSE_AND_IMPLEMENTATION_GATE_2026_06_27.md
  • docs/MUSU_PRODUCT_READINESS_CODE_AUDIT_2026_06_27.md
  • docs/FLEET_NODE_PROOF_RUNBOOK_2026_06_27.md
  • docs/evidence/fleet-proof/1.15.0-rc.22/hugh-main-20260627T010201Z.fleet-proof.json
  • docs/PR34_RC22_TWO_PC_PROOF_CODE_AUDIT_NEXT_STEPS_2026_06_27.md
  • docs/RELEASE_1_15_0_RC22_INSTALL_CHANNEL_AUDIT_NEXT_STEPS_2026_06_27.md

Design Gate Status

Design: Pending

Design brief issue: #35
Design artifacts:

yellowhama added 21 commits June 26, 2026 02:22
@yellowhama
docs(handoff): W-4 2머신 실증 + DPAPI retroactive 갭 갱신
06d7bca
@yellowhama
fix(identity,docs): WS-1 stale Yellowhama.MUSU→blossompark.musu 정합 + …
91af880 
…WS-5b/7 docs

WS-1: runtime detection 4스크립트 blossompark-first OR-compat, canonical artifact 3 hard-replace,
fixture 6(test-release-evidence) 교체(presence-only+current-package sibling 근거). 호환 audit 5파일 보존.
WS-5b: E2E 3-state 플레이북 'transited:true relay forward' 모순 정정(표시 flip≠relay 라우팅, V34 큐잉).
WS-7: GA EV 직접서명 설계 문서 큐잉(Store 메인, EV 대안 트랙).
@yellowhama
fix(build): WS-2 버전 일관성 게이트에 src-tauri\Cargo.toml 추가
d7a337d 
Assert-VersionSourcesCoherent가 3소스(musu-rs Cargo/tauri.conf/publicRelease)만 검사하던 사각지대 →
src-tauri\Cargo.toml(4번째) 추가. dry-run 실증: 현재 rc.20 통과 + 기대버전 변조 시 src-tauri가
mismatch 목록에 잡힘. Edit 도구로만 수정(인코딩 안전).
@yellowhama
docs(store): WS-4 Store blocker 체크리스트 현재 사실로 갱신(rc.20)
c902b55 
실측: prepare-store-submission-bundle.ps1은 버전 하드코딩 없음 — build-msix.ps1 호출(VERSION 추종)+
Find-LatestMsixArtifact로 현재 산출물 집음. 1.13.0.0은 옛 디스크 산출물이지 스크립트 결함 아님.
남은 Store blocker는 전부 외부/operator 게이트(Partner Center 제출/MS 인증/restricted-capability 리뷰).
코드/스크립트 측 준비 정합 완료.
@yellowhama
fix(install,fleet): WS-3 Install-MUSU 견고화 4종 + WS-5a probe→fallback 테스트
b16060b 
WS-3: install-msix.ps1 견고화 4종 이식 — (a)Root에도 cert 추가(thumbprint 핀 검증 AFTER),
(b)0x800B0109 try/catch+actionable+rethrow, (c)elevated 자식창 trap+Read-Host(비대화형/-NoLaunch 가드),
(d)로컬파일 $PSCommandPath -File 재사용 vs irm|iex scriptblock 분기. 부수 버그: irm|iex param() 재선언이
$NoLaunch 리셋하던 latent 버그를 scriptblock 바인딩으로 수정. thumbprint 핀(65F5926…) byte-identical 보존.
WS-5a: probe 응답→FleetNodeStatus 변환을 순수함수 map_probe_response(ProbeOutcome enum)로 추출, 클로저는
HTTP→ProbeOutcome만. MED-2 direct-override+last_seen-insert(0 커버리지였음) 테스트 2개. cargo 519/519.
@yellowhama
test(ci): WS-6 테스트 안전망 복구 — cockpit-contract RED 3 + meshBearer/route…
1fb6d56 
… CI 연결

audit 발견 test-wiring 2 구멍 봉합:
(1) cockpit-contract RED 3개는 전부 테스트 drift(코드 회귀 아님, 기능 실존)였음 — 의미 기반으로 갱신:
  #12 3-state nodeFleetState/fleetState/targetable(relay 보존), #39 fleetState===online + ProbeOutcome
  + peer_last_seen(no-fabrication), #53 U-C 주석 reword 반영 + cloud_deregister_self positive 단언.
  #53 보안 단언 7종(exact-phrase/no-injection/-File/no-DownloadString/no-remove-self) 전부 보존.
(2) test:tauri-shell을 CI(test.yml)에 연결(PR#30 jargon 가드가 비로소 작동). meshBearer.test.ts→test:p2p,
  신규 mesh-bearer/route.test.ts(auth-denied/503/success+owner-binding)→test:routes.
검증: cockpit 53/53, route 4/4, meshBearer 7/7, test:routes 40/40, test:p2p 124/124, fail 0.
@yellowhama
docs(closure): WS-Scribe V33 closure(HTML) + 다음단계(V34) + 핸드오프 갱신
fb3b102 
V33 closure HTML(8 WS + Auditor SHIP 0H/0M + 검증 519/53/4). NEXT_STEPS_V34(relay transport/Store 제출/
EV/DPAPI retroactive 큐잉). 핸드오프에 V33 섹션 + Auditor SHIP 반영.
@yellowhama
docs(spec): FLEET 3-state 계약에 V33 정정 — 표시 레이어≠relay 라우팅
4d957de 
FLEET_RETRY_AND_LAST_SEEN_CONTRACT의 relay state 기술이 'delegated work routes over the relay'로
코드(router.rs:170 relay 미선택, transport 미구현)와 모순됐음. 표시/판정 레이어임을 명문화 +
실제 relay forward는 V34 후속(relay transport)이어야 참이 됨을 명시.
@yellowhama
docs(handoff): V33 인덱싱/스펙정정/PR#34 상태 반영
707cfd9
@yellowhama
docs(v34): 발견/stale 재설계 thesis 확정 (Phase -1 YELLOW reshape 수용)
029d318 
세 리서치(P2P 발견/musu 코드/stale 청소) + business-panel 4인 전략게이트 결과. self-advertise 단일주소
폐기→후보집합+observed-IP(additive)+mDNS 코디네이터독립 1순위+서버 TTL prune+reconcile. Taleb F2(서버=진실은
같은LAN 오프라인 SPOF) reshape 수용, Kim&M F5(진짜 차별점=재설치 자가치유) co-equal scope. 다음 세션 마스터 플랜 입력.
@yellowhama
docs(wiki): 에이전트용 musu.pro 사이트 배포 매뉴얼 (Vercel CLI)
c1c50f8 
다른 에이전트가 musu.pro 사이트를 배포할 수 있는 매뉴얼. Vercel CLI(pull/build/deploy)가
메인 엔진, push는 CI가 같은 CLI를 자동 실행하는 래퍼. 실제 deploy-musu-bee.yml 명령과 일치.
토큰은 yellow.txt vercel 섹션 위치만 참조(실값 미포함). WIKI_INDEX 등록.

scripts/codex-deploy.md(bridge 배포)의 사이트 배포 짝.
@yellowhama
fix(fleet): harden rc21 registry and brain sidecar bonding
21d39ee
@yellowhama
chore(brain): advance sidecar pin to clean recall chip
9b998e6
@yellowhama
feat(fleet): publish additive route candidates
c2bc7b8
@yellowhama
feat(registry): add observed source route candidate
d5c6d11
@yellowhama
feat(fleet): publish all LAN route candidates
7fb843d
@yellowhama
feat(fleet): preflight route candidates before forward
05149e4
@yellowhama
feat(registry): hide stale heartbeat rows from presence
ff99622
@yellowhama
feat(site): add production health endpoint
d938d62
@yellowhama
docs(fleet): record continuation audit state
9ddaf74
@yellowhama
docs(design): prepare PR34 approval packet
b6fa93a
@yellowhama yellowhama mentioned this pull request Jun 26, 2026
Open
yellowhama added 30 commits July 1, 2026 11:54
@yellowhama
docs: add final product spec closeout audit
92e947c
@yellowhama
docs: record remote file share audit
80585bd
@yellowhama
fix: latch shell task cancellation
6aa8072
@yellowhama
docs: record shell cancel no-go status
5c33e57
@yellowhama
test: refresh local packaged release evidence
0b082dd
@yellowhama
docs: record local package evidence refresh
92f5143
@yellowhama
docs: record clean go no go after evidence refresh
9ce134b
@yellowhama
docs: refresh current second pc kit handoff
deb718d
@yellowhama
fix: fail closed release relay payload proof without runtime
58b7314
@yellowhama
test: refresh p2p store-forward relay audit coverage
011bf42
@yellowhama
docs: record p2p store-forward audit clean gate
3d181a9
@yellowhama
fix: surface public metadata dns repair path
062a3bf
@yellowhama
fix: add release relay transport design gate
cbc1658
@yellowhama
test: refresh single-machine release evidence
2d929ec
@yellowhama
test: refresh process and startup evidence
2611705
@yellowhama
test: refresh desktop single-instance evidence
99b6566
@yellowhama
docs: record local packaged evidence refresh
db4fbfe
@yellowhama
fix: retry hidden brain sidecar autostart
7789f8d
@yellowhama
docs: record brain retry and local CPU evidence
f322f41
@yellowhama
fix: keep self-target routes local
a0b115a
@yellowhama
docs: record post-route go-no-go status
b04ee11
@yellowhama
chore: update brain sidecar pin
47f1f1b
@yellowhama
test: capture local package refresh evidence
d7206e2
@yellowhama
test: refresh clean idle cpu evidence
1b53e2a
@yellowhama
test: capture clean runtime cpu matrix evidence
e133441
@yellowhama
test: include node helper budget in idle cpu evidence
ee597c7
@yellowhama
docs: record brain pin package refresh
86bd6a2
@yellowhama
docs: refresh current second pc kit handoff
b346e93
@yellowhama
docs: record product spec stop point audit
25f04f7
@yellowhama
fix: terminalize cancelled writer tasks
cb16789
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@yellowhama