[rustjava-claude-md-prune] docs: prune autonomous-sop, add self-report limits + Goal/Constraints/DoD - #8
Merged
Merged
Conversation
Jun025
pushed a commit
that referenced
this pull request
Aug 15, 2026
…open-PR count (0→2, #8 stranded), verifier axis, sibling null-guard set
Jun025
added a commit
that referenced
this pull request
Aug 15, 2026
…pstream gap (9/32) and cut stale leftovers 4→2 (#9) * [rustjava-lane-restart-upstream-sync-precondition] docs: re-measure upstream gap (9/32), cut stale leftovers 4→2 * [rustjava-lane-restart-upstream-sync-precondition-fix] docs: correct open-PR count (0→2, #8 stranded), verifier axis, sibling null-guard set --------- Co-authored-by: jun0 <junyoung.choi.a@miraeasset.com>
This was referenced Aug 16, 2026
…oal/Constraints/DoD 감사(audit-agent-instructions-2026-08-05) §3-2·§3-3·§6 이행. 지침 파일만 변경 — 소스·빌드·CI 무접촉. C1 autonomous-sop 정리: 4 repo 동일 사본 중 현세대 잉여 1줄 삭제(세션 시작 시 STATE.md·git status 읽기 / 진행분 자율 이어받기 — 둘 다 harness·상위 헌장 기본값). "STATE.md 없으면 생성한다"도 함께 제거 — STATE.md·REPORT.md 는 실재하고 최근 3커밋에서 갱신돼 왔으므로 사문(死文)이다. 나머지 4줄(STATE 갱신·REPORT append·클라우드 금지· 체크포인트/force-push 금지)은 repo 고유 제약이라 보존. C2 「티켓 없는 착수 금지」: 문장은 유지하고 qts 판본의 한계 서술을 이식 — 이 규율은 자기신고형이고 티켓 파일에 provenance 가 없어 검증기로 막을 수 없다(1차 방어이며 최종 방어는 diff 검토). 홈 헌장 포인터로의 대체는 orch 레인 동결 해제 후 후속 몫. C3 구조: Goal/Constraints/DoD 골격 도입. Goal 에 연방 경계 2건을 명시 — RustJava 는 wie 의 비벤더 upstream 의존성이라 플랫폼이 직접 손대지 않는다(정본 = otterpebble .claude/rules/repo-boundaries.md #4), 그리고 이 repo 는 dlunch/RustJava 의 포크라 upstream 발신은 티켓 명시 허가 시에만 하고 gh 호출에 -R Jun025/RustJava 를 붙인다 (2026-07-22 오발행 사고). 둘 다 지금까지 지침에 없어 티켓마다 재기술돼 왔다. AGENTS.md 는 무접촉 — §Git Workflow 의 `-D` 강제 이유 보존. 연방 고유 내용을 CLAUDE.md 쪽에만 둔 것은 의도적이다: AGENTS.md 는 upstream 도 유지·편집하는 파일이라 (upstream 이 dlunch#180 에서 §Testing Boundaries 를 추가했다) 로컬 내용을 넣으면 동기화 충돌면이 넓어진다. 검증: cargo fmt --check rc=0 · cargo clippy --workspace --all-targets rc=0(경고 0) · cargo test --workspace rc=0(148 passed, 0 failed). Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Jun025
force-pushed
the
feat/rustjava-claude-md-prune
branch
from
August 18, 2026 19:07
7e73a1c to
342ba8e
Compare
Jun025
added a commit
that referenced
this pull request
Aug 26, 2026
…m-sync-s3] * Bump bytemuck from 1.25.0 to 1.25.1 (dlunch#173) Bumps [bytemuck](https://github.com/Lokathor/bytemuck) from 1.25.0 to 1.25.1. - [Changelog](https://github.com/Lokathor/bytemuck/blob/main/changelog.md) - [Commits](Lokathor/bytemuck@v1.25.0...v1.25.1) --- updated-dependencies: - dependency-name: bytemuck dependency-version: 1.25.1 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> * Replace runtime panics with the matching Java exceptions (dlunch#174) * Replace runtime panics with the matching Java exceptions An unwrap audit found panics reachable from ordinary Java code: - File.length() returns 0 for a missing file; isDirectory/isFile lose their guard-then-unwrap shape - FileImpl (native runtime) maps open/read/write/seek failures to IOError instead of panicking, so FileInputStream and RandomAccessFile guards actually produce FileNotFoundException; FileOutputStream gains the same guard - File I/O operations (read/write/seek/available/length/setLength) throw java.io.IOException on failure via a shared helper - Class.forName resolves the class and throws ClassNotFoundException (new runtime class) instead of panicking on any not-yet-loaded name - StringBuffer.append(char)/append(char[]) keep exact UTF-16 units so unpaired surrogates no longer panic and pairs built char by char survive; String.valueOf(char) builds through [C for the same reason - PrintStream.println(char) replaces an unpaired surrogate with '?' like the JDK charset encoder - ZipFile validates the archive in its constructor and throws java.util.zip.ZipException (new runtime class) for a malformed archive; getInputStream returns null for a missing entry Expected outputs for the new fixtures are generated by a real JVM. Remaining unwraps are invariants (interpreter stack discipline, thread attach), guarded lookups, or documented gaps (lenient calendar normalization, ClassFormatError plumbing). * Inline the IOException conversion at each I/O call site * Return the same Thread object from Thread.currentThread() (dlunch#175) Every attached thread now owns its java/lang/Thread instance: attach takes the instance for threads started via Thread.start (so currentThread() inside run() is the started Thread object) and creates one otherwise (bootstrap, external attachers). currentThread() returns the stored instance, and the GC roots it per thread. Also parse unrecognized classfile attributes as an opaque Unknown variant instead of failing — JVMS 4.7.1 requires silently ignoring them, and the anonymous-class fixture carries EnclosingMethod and Signature attributes the parser rejected. Expected output for the fixture is generated by a real JVM. * Add Java primitive wrapper classes (dlunch#176) * Add Java primitive wrapper classes * Use Character digit semantics for numeric parsing * Bump tokio from 1.52.3 to 1.52.4 (dlunch#179) Bumps [tokio](https://github.com/tokio-rs/tokio) from 1.52.3 to 1.52.4. - [Release notes](https://github.com/tokio-rs/tokio/releases) - [Commits](tokio-rs/tokio@tokio-1.52.3...tokio-1.52.4) --- updated-dependencies: - dependency-name: tokio dependency-version: 1.52.4 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> * Add CLDC 1.1 core API compatibility (dlunch#177) * Add CLDC 1.1 core API compatibility * Fix CI lint and improve CLDC coverage * Fix array assignability and reader progress * Harden JVM runtime correctness (dlunch#180) * Harden JVM runtime correctness * Address classfile review findings * Move class initialization tests to Java fixture * Separate classfile validation from JVM verification * Remove ClassFileError re-export * [rustjava-upstream-sync-s2] docs: record S2 landing (cut af4f6f8, conflicts 5, ancestry restore) * [rustjava-upstream-sync-s3] docs: record S3 landing (cut 822504b, conflicts 11) + refresh STATE 「다음」 STATE.md ③-0 pointed at rustjava-pr8-claude-md-prune-disposition as top priority on the grounds that its review.md was missing and gate 2 had stalled. Both are false now: PR #8 is MERGED (2026-08-18T19:26:08Z -> 00bddf3) and the review reports exist. Item closed, list renumbered, ⑤ operating notes re-measured (open PRs 2 -> 1, dead branch row dropped). * [rustjava-upstream-sync-s3] docs: record S2 landing (11ef501) and correct the ancestry-axis prediction --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Inseok Lee <git@dlun.ch> Co-authored-by: jun0 <junyoung.choi.a@miraeasset.com>
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
1 participant
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.
감사
~/orchestrator/reports/audit-agent-instructions-2026-08-05.md§3-2·§3-3·§6 이행.지침 파일 1개(
CLAUDE.md)만 변경 — 소스·빌드·CI 무접촉.C1. autonomous-sop 정리 (감사 §3-2)
4개 repo 에 동일 복제된 블록에서 현세대 잉여 1줄을 삭제했다:
git status/git log --oneline -5를 읽고" — 세션 시작 컨텍스트 파악은 기본 동작STATE.md(3,737B)·REPORT.md(6,922B) 둘 다 tracked 이고 최근 3커밋에서 갱신돼 왔다.나머지 4줄(STATE 갱신 · REPORT append · 클라우드 표면 금지 · 체크포인트/force-push 금지)은
repo 고유 제약이라 보존.
C2. 「티켓 없는 착수 금지」 (감사 §3-3)
문장은 유지하고(홈 헌장 포인터 대체는 orch 레인 동결 해제 후 후속 몫) qts 판본의
한계 서술을 이식해 정직성을 맞췄다 — 이 규율은 자기신고형이고 티켓 파일에 provenance 가
없어(발권 주체 필드도
bin/queue-lint출신 검사도 없다) 검증기로 막을 수 없다.1차 방어일 뿐이며 최종 방어는 diff 검토다.
C3. 구조 (감사 §6)
Goal/Constraints/DoD 골격 도입. Goal 에 연방 경계 2건을 명시했다 — 둘 다 지금까지
지침에 없어 티켓마다 재기술돼 온 사실이다:
(정본 = otterpebble
.claude/rules/repo-boundaries.md[rustjava-tracing-attributes-pin-removal] fix: unfreeze tracing family by replacing the sole #[instrument] with a manual span #4).dlunch/RustJava의 포크다 — upstream 발신은 티켓 명시 허가 시에만,gh호출엔-R Jun025/RustJava(2026-07-22 오발행 사고).★**
AGENTS.md는 무접촉** — §Git Workflow 의-D강제 이유 보존. 연방 고유 내용을CLAUDE.md쪽에만 둔 것은 의도적이다:AGENTS.md는 upstream 도 유지·편집하는 파일이라(upstream 이 dlunch#180 에서 §Testing Boundaries 를 추가했다) 로컬 내용을 넣으면 동기화 충돌면이 넓어진다.
반면 upstream 의
CLAUDE.md는@AGENTS.md1줄뿐이라 우리 델타와 겹치지 않는다.분량
CLAUDE.md16줄/1,138B → 29줄/2,417B. 예산(12KB) 대비 20%. 증가분은 전부Contract 가 요구한 신규 내용(C2 한계 3줄 · C3 연방 경계 6줄 · 절 머리글 3줄)이고,
기존 문장 중 늘어난 것은 없다.
검증
cargo fmt --checkcargo clippy --workspace --all-targetscargo test --workspaceplan mode 시뮬레이션 2건(ⓐ
java_runtime/클래스 추가 · ⓑ 머지된 브랜치 정리) 결과와보류한 삭제 후보 목록은 회신
~/orchestrator/reports/rustjava-claude-md-prune.done.md참조.★완주 지점 = 이 PR 오픈. 머지는 게이트② approve 후 별도
-merge티켓 몫.