If the same task is currently handled by tk-prep or tk-pr-respond, return the diagnostic evidence to that owner and
do not start a separate workflow. Otherwise, after checking the current request's symptoms, expected behavior, and access scope,
read the installed tk-engineering의 diagnosis.
If there is no owner or reference, or the identity differs, stop that diagnosis and guide to tk-setup-skills.
Do not substitute another installation, memory, or source checkout.
"Why is this error happening" — investigation and diagnosis requests are read-and-report only. Perform only safe reproduction and non-mutating probes within the current approval scope, and do not modify product code, configuration, or data. Modify only when there is a modification request or a valid modification approval for the same incomplete task, and only within the scope that satisfies the diagnosis document's cause and verification conditions. Reading the diagnosis reference is not installation, authentication, secret access, Git commit, or remote publishing authority.
Briefly report the symptom, cause and file:line evidence (hypothesis if unconfirmed), actual reproduction/verification results, and remaining gaps.
If modified, also include investigation results of the same type. The criteria for stopping unfounded repeated modifications are
owned by the diagnosis document. Do not create a new diagnosis ledger, central router, or automatic installation.
Maintenance source: Waza application judgment.