Assess one bounded Proto UI Adapter question without changing repository or external state. Use for new-Adapter research, target compatibility, catalog readiness, reviewed Module support or omission evidence, Host Capability fidelity, lifecycle translation, dependency risk, or implementation readiness. Do not catalog, implement, repair, or approve the Adapter slice.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Proto-UI/Proto-UI☆ 362026년 10월 18일 업데이트
Measure the active Agent model with pinned offline ModelTrace sampling and return an unsigned closed-set attribution record. Use before Agent-originated commits, Issue/PR creation or material updates, comments, reviews, and current collaboration writes in either execution mode. Do not treat a fingerprint, declared model label, or record reference as authenticated identity, permission, independent review, or acceptance.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Proto-UI/Proto-UI☆ 362026년 10월 18일 업데이트
Run Proto UI's dynamic comprehension assessment and derive an unsigned local task-fit result. Use when an Agent needs review calibration or a fresh autonomous task and review ceiling. Do not use a self-result as identity, permission, or acceptance evidence.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Proto-UI/Proto-UI☆ 362026년 10월 18일 업데이트
Diagnose one bounded Proto UI Actions or CI failure from an exact workflow run and revision, then route the exact repair, validation, or recheck transition. Use to locate the owning failure and distinguish infrastructure from change failures. This leaf remains read-only.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Proto-UI/Proto-UI☆ 362026년 10월 18일 업데이트
Post one already selected Proto UI work-item claim as a reversible GitHub metadata mutation. Use after pui-select produced a current proposal and the exact claim has authorization, live permission, current readiness, and an idempotent write boundary. Do not select work, decide readiness, release claims, or widen the authorized wording.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Proto-UI/Proto-UI☆ 362026년 10월 18일 업데이트
Apply one exact-target Proto UI collaboration update through the ordinary governed primitive or an explicitly current-user connected-operation path for archive/ref recovery, Issue reopening/linking, additive carrier publication and service control. Do not manufacture review dispositions, merge, close, release or change privileged settings.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Proto-UI/Proto-UI☆ 362026년 10월 18일 업데이트
Create or update a readable Proto UI legacy-contract projection for explanation or an explicitly accepted uncataloged gap. Use for internal contract prose, migration banners, rationale, or synchronized readable projections. Do not use when an applicable spec entity already owns the rule or when semantics are unsettled.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Proto-UI/Proto-UI☆ 362026년 10월 18일 업데이트
Apply one governed bounded Proto UI dependency update after pui-deps establishes the exact manifest, lockfile, consumers, compatibility evidence, and rollback boundary. Use for ordinary package or toolchain updates whose intended compatibility is already fixed. Route unresolved public compatibility, security disclosure, publication, release, or provenance exceptions to their dedicated decision path.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Proto-UI/Proto-UI☆ 362026년 10월 18일 업데이트
Audit one bounded Proto UI deployment or publication evidence slice against an exact revision and delivery surface. Use to verify revision identity, environment result, artifacts, and observable health. Do not deploy, promote, roll back, publish, release, or change environment protection.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Proto-UI/Proto-UI☆ 362026년 10월 18일 업데이트
Assess and route one bounded Proto UI dependency drift, advisory, or update question. Use to trace manifest and lockfile identity, consumer impact, compatibility evidence, provenance, update risk, and the exact next update or no-action transition. This leaf remains read-only.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Proto-UI/Proto-UI☆ 362026년 10월 18일 업데이트
Route ordinary Proto UI development through a minimal composition of repository skills. Use when starting, continuing, or handing off feature, fix, spec, contract, Module, Host Capability, Adapter, Prototype, component, test, documentation, review, or release-preparation work. Do not use for autonomous-maintenance runs; use pui-maintain.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Proto-UI/Proto-UI☆ 362026년 10월 18일 업데이트
Publish one prepared Agent evidence packet as an additive Issue comment, including historical or closed Issues, under exact current authorization. Use after read-only Issue inspection and separately authorized evidence preparation. Do not reproduce, select work, upload assets, edit human text, claim, review, close, or change Issue metadata.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Proto-UI/Proto-UI☆ 362026년 10월 18일 업데이트
Audit one bounded Proto UI collaboration-governance slice and route policy-determined drift toward reversible correction. Use across Issues, pull requests, Discussions, labels, milestones, Project, rules, permissions, or Actions. This evidence leaf is read-only; authorized corrections continue in their registered leaves.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Proto-UI/Proto-UI☆ 362026년 10월 18일 업데이트
Establish Proto UI repository state, live contributor authority, Agent comprehension scope, task risk, and authorization before work begins. Use at the start of a development session, before autonomous task selection, after a material repository update, or when permission or assessment state may have changed.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Proto-UI/Proto-UI☆ 362026년 10월 18일 업데이트
Apply one independently reviewable numeric Proto UI package-budget increase for an already accepted capability, using canonical cost evidence and existing development authorization. Use for standalone ceiling transactions, not feature implementation, measurement-policy changes, spending limits, publication or release.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Proto-UI/Proto-UI☆ 362026년 10월 18일 업데이트
Maintain an existing Proto UI Prototype or implement a governed Base or design-language component slice. Use for governed component behavior, anatomy, inheritance, exports, CLI registration, style projection, demos, or public preview work. Do not use to admit a new semantic subject or invent Base ownership from a component name.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Proto-UI/Proto-UI☆ 362026년 10월 18일 업데이트
Record one authorized non-remediation terminal outcome in Proto UI's autonomous-maintenance state. Use after a supported no-finding result, an independently rejected finding, or a blocked mission whose terminal evidence is complete.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Proto-UI/Proto-UI☆ 362026년 10월 18일 업데이트
Reproduce and repair a bounded Proto UI regression whose expected behavior and owning layer are already governed. Use this before domain implementation skills whenever work starts from a reproducible failure, including bug fixes, drift repairs, broken exports, Runtime failures, Adapter parity defects, Prototype defects, or public-projection regressions. Do not use when expected semantics or ownership is unresolved.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Proto-UI/Proto-UI☆ 362026년 10월 18일 업데이트
Prepare a reviewed Proto UI global release candidate as repository state after current project authority has chosen the exact version and stage. Use for draft Version identity, exact package metadata, notes, bill of materials, rehearsal, and publish dry-run. Publication remains a distinct privileged operation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Proto-UI/Proto-UI☆ 362026년 10월 18일 업데이트
Independently review a Proto UI change against current authority, bounded scope, executable evidence, projections, provenance, and integration conditions. Use for pull-request review, acceptance review, pre-merge audit, or fresh-context verification. Do not use to approve one's own work.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Proto-UI/Proto-UI☆ 362026년 10월 18일 업데이트
Design or implement the smallest complete executable evidence for a governed Proto UI behavior. Use for conformance cases, regression tests, cross-layer verification, test-entity mappings, failure-path coverage, or validation-plan design. Do not use tests to decide unsettled semantics.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Proto-UI/Proto-UI☆ 362026년 10월 18일 업데이트
Trace a Proto UI change through authoritative spec lifecycle, legacy explanation, dated context, implementation, executable evidence, package surfaces, and public projections. Use before deciding scope, changing behavior, reviewing a pull request, or investigating drift.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Proto-UI/Proto-UI☆ 362026년 10월 18일 업데이트
Select, run, and report proportional Proto UI validation for a completed change. Use before review, handoff, commit, or pull request updates, and after resolving validation failures. Cover focused evidence first, then affected graph, types, docs, packaging, consumers, release, or repository checks according to risk.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Proto-UI/Proto-UI☆ 362026년 10월 18일 업데이트
Inspect one bounded Proto UI Issue queue slice and route ready governed work toward claim and implementation. Use for intake health, readiness, ownership, claim conflicts, stale state, or a candidate task search. This evidence leaf is read-only; authorized claim and implementation continue in their registered leaves.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Proto-UI/Proto-UI☆ 362026년 10월 18일 업데이트