Independently attempt to falsify one Proto UI autonomous-maintenance finding in a fresh non-mutating context. Use after pui-observe produced a candidate finding and route the result directly to remediation or closure when authority is clear.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Close one technically complete Proto UI autonomous-maintenance transition after adequate independent review and required validation. Use to synchronize the finding, remediation packet, mission, run ledger, residual-risk queue, and recorded integration decision.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Freeze one eligible Proto UI autonomous-maintenance candidate into a bounded mission packet and lease. Use before observation when a current request or governed queue supplies scope, oracle, baseline, capability, risk, budget, completion, and stop conditions. Do not observe, verify, repair, or invent a mission.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audit an already completed protected Proto UI publication and reconcile immutable external facts with Version entities, release records, and public projections. Use after publication for registry, tag, GitHub Release, asset, checksum, workflow-head, and deployment evidence. Never republish or replace immutable evidence.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Implement one governed Proto UI Adapter-profile realization slice. Use when target and runtime range, supported or omitted Module role, Host Capability fidelity, lifecycle translation, failure behavior, compatibility boundary, and evidence scope are fixed by current authority. Use pui-adapter-assess for research or readiness assessment and pui-regression first for a governed failing behavior.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Implement or revise one governed Proto UI Host Capability connecting a semantic Module to a bounded host responsibility. Use when capability identity, portable need, public shape, availability, failure, replacement, cleanup, fidelity, Adapter realization, and evidence are fixed by current authority.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Implement or extend one governed Proto UI Module semantic slice. Use when Module ownership, facade and port boundary, dependencies, resource lifetime, Host Capability plan, Runtime registration, Adapter evidence, and validation scope are fixed by current authority. Do not use to admit a new Module or decide ownership.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Release one current Proto UI work-item claim when it expired, became invalid, or the contributor stopped. Use only for the contributor's own recorded claim and only when the exact reversible GitHub mutation is authorized. Do not select replacement work, change readiness, or release another contributor's claim.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Integrate one exact-head Proto UI pull request through either the ordinary independent-review path or a separately explicit current-user connected-operation decision. Preserve source, DCO, live platform enforcement and all deferred criteria; never manufacture approval or acceptance.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Investigate a bounded Proto UI Contract, Prototype, Module, Host Capability, Adapter, schema, or ownership question and turn a genuinely unresolved direction into one semantic decision packet. Use for spec brainstorming, admission questions, competing semantic models, uncataloged behavior, or unresolved cross-layer boundaries.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
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.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Update Proto UI human documentation, localized pages, contributor guidance, demos, or package prose as a projection of governed repository facts. Use when the reader problem and source authority are known. Do not use documentation to invent semantics, hide drift, or widen a lifecycle guarantee.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.