Require proactive process-problem reporting and owned improvement disposition in board development #4733

Owner: Programme/root owns full acceptance, native/PR integration and serialized shared outputs. Original feature author /root/intake_process_fix retains feedback4733-source20261020-01 on routine/proactive-process-feedback-4733-20261020. Independent reviewer coord_observer_design is reviewing the exact integrated source; all prior owners and reservations remain.

Done when:

• Canonical work-board requires executing agents to proactively report material process problems and improvement proposals during ordinary development; work-board-coord inherits the requirement.
• Agents report promptly when a process problem blocks progress, risks incorrect effects or acceptance, or causes substantial avoidable work. Existing worker returns, review completion and handoff boundaries include a check for unreported process problems; agents need not invent findings or repeat unchanged ones.
• Reports distinguish observation from hypothesis and include evidence, delivery impact, workaround used and a proposed improvement when known. A missing solution does not suppress a valid problem report.
• The root integrator ensures every material report receives a reasoned disposition: repair within current scope, attach to existing work, route a distinct improvement through canonical intake, investigate, defer or decline. Existing independent-review disposition rights remain intact. Unresolved findings retain an accountable owner, next action and reconsideration condition.
• Findings and decisions live in existing owning issues/PRs; semantic deduplication precedes new filing. No separate reporting workers, mandatory packets, duplicate ledger, automatic issue creation, new measurement campaign or recurring unchanged reports are introduced.
• Accepted improvements define proportionate verification of the intended effect. Reusable verified lessons are captured through Atlas, retaining a capture gap and owner when necessary. Source delivery and any applicable published/installed instruction adoption are verified separately before active-use claims.
• Canonical lifecycle/host guidance and the worker execution/return guidance agree; applicable mirrors, generated guidance and registries are updated through their maintained sources. show-progress summarizes owned findings and decisions. One independent review and applicable required CI pass; a bounded ordinary coordination example demonstrates reporting, disposition and durable ownership without changing underlying operation authority.
• Reporting or disposition grants no dispatch, reservation release, retry of uncertain effects, Status write, weaker acceptance or closure authority. Existing full promises and ongoing owners/operations remain preserved.

Current deliverable: Complete scoped acceptance established: canonical proactive reporting/root disposition guidance merged by PR4735 exact5340c356 into protected11a9d683491ff19e944fed71bc7a6bee29d7b33e; source/mirrors/generated/Atlas, required CI and applicable actual root instruction adoption verified.

Next action: No remaining action in this scoped guidance Delivery. Root retains the separate Prepare-refusal diagnostic investigation already recorded below: investigate sanitized two-path journal proposal before the next maintained migration CLI change, or earlier if another refusal prevents correctness; use canonical intake before any distinct implementation.

Blocked on: None for this scoped guidance acceptance. Other Deliveries and original effects keep their own holds.

Acceptance evidence: Explicit user request in the 2026-10-20 side conversation: require standard agent reporting of process problems/improvement proposals, then create an item and add it to Coordination. Read-only inspection found host-loop.md preserves findings once reported and show-progress/SKILL.md asks for process problems, but the standard execution lifecycle lacks an explicit proactive reporting boundary. Atlas search for process improvement findings returned no match; no global absence is asserted. Bounded native searches covered current open .github issues, process/report matches and exact process-problems matches. Related #4701 is completed lifecycle work; #4730/#4731 concern deterministic coordination/observation, and historical #2691/#2687/#2737 cover prior finding machinery. This is a distinct follow-on reporting/disposition requirement and does not revive retired packet/register requirements.

Relevant source is recorded in .agents/skills/work-board/SKILL.md; work-board/references/lifecycle-contract.md, host-loop.md and intake.md; .agents/skills/work-board-coord/SKILL.md; .agents/skills/pnext-item/SKILL.md and references/findings-and-filing.md; .agents/skills/show-progress/SKILL.md; applicable maintained mirrors/generators.

Protected enrollment prerequisite accepted through PR #4734 delivered exact0cc0a35b as protected15d5b0e0. Genuine physically verified installed109 completed all44selected/attempted/items/memberships with no gaps and zero mutations. This establishes enrollment/read coverage only, not feedback implementation or full acceptance.

Ordinary coordination reporting and root disposition recorded2026-10-20 during this existing work. These are actual observations, without a new findings ledger or reporting actor.

• The Status Prepare command twice returned a generic refusal before any Status send and retained no failure classification. A project timestamp changed during one window, supporting instability as a hypothesis; the exact rejecting predicate is unproved. Impact was loss of diagnostic precision. Root preserved both originals and reconciled current independent work through separately admitted fresh native preimages/readback. Disposition is investigate a sanitized bounded Prepare failure journal as distinct follow-on scope, not silently add it to this guidance Delivery. Programme/root owns review of the identified two-path proposal before accepting4733; reconsider immediately if another such refusal blocks correctness, or at the next maintained migration-CLI change. No blind original-effect retry or weaker snapshot guard is authorized.

• The retained-recovery wrapper rejected genuine Status evidence because it read the fifth native issue token as a body hash; the maintained token is state. Its earlier fixture derived both expected values from that same wrong assumption. Root repaired this within existing4723 preparation by binding the independent full native issue body and replaying the genuine eighteen-file guard custody. Actual protected preimages, full reported preservation and readback passed before the supported recovery ran. Disposition is accepted for this guard mismatch only; earlier synthetic green controls remain limited and the full matrix still has21passed/twoheld/onefailed. Programme/root retains matrix acceptance and all original evidence.

• The maintained registry writer refused a pre-existing dated skills-changelog entry above the Entries heading. Root repaired the current carrier by moving that exact historical entry under the heading before older entries, preserving every byte of its content, then used the maintained writer and complete generation/check successfully. Disposition is repaired in4cc55de5; final exact-headCI remains required. This is an ordinary source-integration example, not a runtime or fleet-adoption claim.

Accepted2026-10-20 after exact5340c356 independent repair review, final required CI and ordinary protected delivery to11a9d683. Actual root canonical host/worker/show-progress files read back byte-equal to reviewed source; applicable worker instructions were supplied during real returns. Bounded ordinary examples above retain observed facts, hypotheses, repair/investigation decisions, owner/next/reconsideration. Existing Ready/Status wrapper, changelog and canonical-custody CI problems were repaired proportionately without weakened guards; Prepare generic refusal remains explicitly root-owned investigation. Atlas github/proactive-process-findings-and-disposition captured with preserved predecessor history. No package/fleet publication or underlying operation authority is inferred.