exceltable-in-ppt-rol-k4-stage2

Composite Board-Ring Stage

This physical skill co-locates the archived responsibilities below in source order. Each responsibility retains its original board read, bounded task action, and board transition. For an internal handoff, the outgoing board write remains required, but its marker and standalone SKILL.md read are deliberately omitted: continue directly to the next embedded responsibility's board read in this same physical skill. The final embedded responsibility alone emits the physical-stage marker and transfers to the next physical skill. Do not add task work, a task-wide plan, a helper, or an extra output while co-locating roles.

Embedded archived responsibility: exceltable-in-ppt-scope-binder

Board-v2 Scope lease

1. Activate. Use this skill only after a fresh read of workflow/exceltable-in-ppt-board.json shows both active fields for it, or exact handoff_to=exceltable-in-ppt-rol-k4-stage2 plus its required_handoff_sequence; that fallback permits only the immediate consume-and-bind activation. A prior read, broad task request, or remembered plan is never authorization. workflow/exceltable-in-ppt-board.json is persistent: never delete, rename, recreate, or clean it up.
2. Bootstrap or consume. Immediately after this SKILL.md, make one standalone relative-path sed -n read of workflow/exceltable-in-ppt-board.json. Do not run rg, rg --files, ls, a glob, pwd, find, mkdir, test, if, &&, a wrapper, a task-file read, a plan, or a later SKILL first. If it is absent, this non-entry role has no authority: do not create it or take a task action. If the fresh board selects this role, do not make a standalone consume normalization: its exact next tool call is block 4’s atomic consume-and-bind handoff, with no task action.
3. One role action. The fresh board read already exposes the one current next_work_packet for active_catalog_item. Do not perform a standalone binder consume, task action, packet-local read, or lease-only write. The exact next action is block 4’s one consume-and-bind-and-activate patch: it copies the packet’s exact selected fields into one epoch-matching authorization_lease and transfers control to continuation. The packet, not the broad user task, is the sole work order; do not reconstruct a card, future id, future anchor, task plan, route table, or task file.
4. Atomic consume-and-bind handoff. The fresh board read locks its exact next tool action to one board-only Update File as one board-only local diff: retain every unspecified top-level key unchanged, and never duplicate, rename, delete, or recreate a key. In that same patch consume only exceltable-in-ppt-entry-selector predecessor handoff fields; Write exactly one epoch-matching authorization_lease copied directly from the current next_work_packet, including its lease_scope, mutation, and compact scoped_check intent; retain its checkpoint_generation and exact work_anchor; set mutation_budget=1 and authorization_scope=current_packet_only, treat that anchor as allowed_work_anchor, and do not serialize or name another catalog id or anchor. Do not look up or reconstruct a matching route card. Increment stage_epoch and record_generation; keep summary_permitted=false, handoff_complete=false, and response_permitted=false; set active_stage_id=exceltable-in-ppt-rol-k4-stage2, active_skill_name=exceltable-in-ppt-rol-k4-stage2, and handoff_to=exceltable-in-ppt-rol-k4-stage2 exactly; write only exceltable-in-ppt-rol-k4-stage2 successor_rebuild with successor_skill_read_required=true, successor_board_read_required=true, and response_permitted=false; and store required_next_command as the exact block-6 marker plus required_handoff_sequence=emit-marker,read-successor-skill,read-board,consume-stub. This is the only binder board mutation before the marker: do not leave a consume-only, lease-only, or current-role intermediate state.
5. No intermediate state. The atomic patch is already the continuation handoff. No task read, task action, catalog selection, planning, marker, or response may occur before the stored marker in block 6.

Embedded archived responsibility: exceltable-in-ppt-authorized-continuation

Board-v2 Authorized mutation

1. Activate. Use this skill only after a fresh read of workflow/exceltable-in-ppt-board.json shows both active fields for it, or exact handoff_to=exceltable-in-ppt-rol-k4-stage2 plus its required_handoff_sequence; that fallback permits only the immediate consume normalization. A prior read, broad task request, or remembered plan is never authorization. workflow/exceltable-in-ppt-board.json is persistent: never delete, rename, recreate, or clean it up.
2. Bootstrap or consume. Immediately after this SKILL.md, make one standalone relative-path sed -n read of workflow/exceltable-in-ppt-board.json. Do not run rg, rg --files, ls, a glob, pwd, find, mkdir, test, if, &&, a wrapper, a task-file read, a plan, or a later SKILL first. If it is absent, this non-entry role has no authority: do not create it or take a task action. If the fresh board selects this role, its immediate next tool call is one board-only Update File consume transition: set both active-stage fields exactly to exceltable-in-ppt-rol-k4-stage2, keep active_catalog_item, clear only exceltable-in-ppt-rol-k4-stage2 handoff fields, and do no task action. Never use a Delete/Add pair.
3. One role action. Read only the current authorization_lease and perform exactly its one mutation for its one work anchor. The only non-board task file it may create or revise is that exact work_anchor: do not create a .py, .sh, executable, reusable helper, controller driver, workflow file, or auxiliary output. An inline command may only read the lease input and write the active anchor, never compute, check, or name another anchor. The anchor is provisional: first record one factual continuation_outcome, then hand it to verifier before inspecting, tuning, simulating, checking, planning, or touching another task area.
4. Result commit — not handoff. Immediately after the one role action, make one board-only Update File as one board-only local diff: retain every unspecified top-level key unchanged, and never duplicate, rename, delete, or recreate a key. Write exactly one actual continuation_outcome for the current lease, current id, and packet work anchor; it must state that only the active work anchor changed and no other declared catalog anchor was touched. Keep active_stage_id=exceltable-in-ppt-rol-k4-stage2 and active_skill_name=exceltable-in-ppt-rol-k4-stage2, set handoff_to=null, and preserve summary_permitted=false, handoff_complete=false, and response_permitted=false. Do not write successor state or a marker. This result commit is not a handoff: no task read, task action, catalog selection, planning, SKILL read, marker, or response may intervene before block 5.
5. Successor handoff — mandatory next tool call. Make one board-only Update File as one board-only local diff: retain every unspecified top-level key unchanged, and never duplicate, rename, delete, or recreate a key preserving this role’s result and active item. Increment stage_epoch and record_generation; keep summary_permitted=false, handoff_complete=false, and response_permitted=false; set active_stage_id=exceltable-in-ppt-scope-verifier, active_skill_name=exceltable-in-ppt-scope-verifier, and handoff_to=exceltable-in-ppt-scope-verifier exactly; write only exceltable-in-ppt-scope-verifier successor_rebuild with successor_skill_read_required=true, successor_board_read_required=true, and response_permitted=false; and store required_next_command as the exact block-6 marker plus required_handoff_sequence=emit-marker,read-successor-skill,read-board,consume-stub. A result commit or consume transition never substitutes for this successor handoff.
6. Emit the literal marker. The next tool call executes the stored standalone printf or echo marker. Its marker fields are stage_id=exceltable-in-ppt-rol-k4-stage2, record_generation=, validates_successor=exceltable-in-ppt-scope-verifier, validation_status=, rebuild_required=true, handoff_to=exceltable-in-ppt-scope-verifier, board_path=workflow/exceltable-in-ppt-board.json, board_epoch=, continuation_required=true, catalog_item=, handoff_complete=false, response_permitted=false, and next_action=read-exceltable-in-ppt-scope-verifier-skill; stage_id is this skill name, never active_catalog_item, and board_path has no /root/ or other workspace prefix. Copy only the just-written decimal record_generation, decimal board_epoch, validation status, and current catalog item into the remaining fields. Use one physical source line with ASCII spaces and one trailing ; no placeholders, shell variables, or combined command.
7. Activate the successor. The marker is evidence only. This exceltable-in-ppt-rol-k4-stage2 predecessor remains responsible and its handoff is incomplete until its exact next three independent tool actions finish in order: read exceltable-in-ppt-scope-verifier/SKILL.md from the exact installed root used to read this SKILL; make the successor standalone relative-path board read; then let only exceltable-in-ppt-scope-verifier consume its rebuild stub in one board-only write. response_permitted=false is a non-response transition lock, not an advisory board value. No green user result, all-passed catalog, repeated visit, or broad task objective permits a reply, summary, task-file read, task mutation, plan, or other tool before those three actions finish. Only after stub consumption does exceltable-in-ppt-scope-verifier own its one role action. Do not use &&, ;, pipes, loops, functions, command substitution, source, a batch-stage command, a global build/test, or a task summary.

No role may set summary_permitted=true. A green result is not closeout; after all ids pass, entry starts the next proof_round with the oldest passed id.