Baseline 91fd3d5 matched origin/main; 5 CLI and 20 inspection tests passed. No unfinished
feature PR; unrelated Dependabot #23 left untouched. Owner authorized next iteration and reported
a manual usage reset. Branch feat/inspect-dispatch-inputs; previous plan/checkpoint edits are
owned work included with the feature. No further reset action or usage assumption was made.
Implemented scalar/mapping manual trigger declarations, distinct source-presence states, typed
input metadata/defaults, deterministic rendering and strict validation. No input binding or default
application. Pinned schema/converter boundary is recorded in the iteration.
Observed red/green: mapping support, choice options/default validation and identifier validation.
Focused green: 25 CLI inspection tests + 5 CLI regressions and two new public parser-summary tests.
cargo xtask ci, local Markdown targets and git diff --check passed. Next: finish review, push/create
feature PR, satisfy required hosted checks and merge the verified head with no unresolved findings.
Then provide the owner a DX before/after report including parser changes and evidence limits.
No execution, provider activation, action acquisition, environment lookup or repository mutation.
No dependencies/tooling/schedules changed. Canonical example workflows still have unsupported
run-name, permissions, timeout, shell/environment, action inputs and working-directory fields.
Full milestone acceptance and final audit remain pending; Java worker stays paused. Prior runner
labels delivered in PR #25 as 91fd3d5. Older checkpoint sections below are historical.
Owner authorized a one-off run of the saved workflow-inspection schedule, readiness setup and a first-beta dependency map. The recurring task remains scoped to inspection; the Java worker remains paused. See proposed beta dependencies.
Baseline: main and origin/main were both 04b4861; checkout clean, no open feature PR.
cargo xtask ci passed (format, locked all-target/all-feature compilation and Clippy, workspace
tests including the offline corpus, and strict Rustdoc). This proves development readiness,
not workflow execution support. cargo xtask doctor found rustfmt, Clippy and all seven
optional tools ready. Rust was 1.99.1, Python 3.15.2; GitHub authentication was usable.
No custom core.hooksPath was configured. No hooks, toolchain, global configuration,
dependencies or variable names were changed. Optional tools need no refresh for inspection.
Continue in the existing local checkout on feat/workflow-inspection. The uncommitted new
beta-dependencies.md and this checkpoint were created by this bootstrap, not unrelated user
work; include/update them alongside the first feature PR. No implementation or behavioral red
has been observed yet. Read the saved task’s acceptance scope and current provider decisions
before coding. Resolve whether the first useful inspection slice fits the accepted compilation
boundary without inventing a native-provider bypass. If it does, deliver that bounded CLI
behavior through red/green and CI. If not, report the exact missing decision and alternatives.
The native manual-run control is used after bootstrap; its start acknowledgement is not a completion claim. Keep the saved cadence, enabled state and prompt unchanged.
Inspected 04b4861 on feat/workflow-inspection; no open PR. Only the bootstrap documentation
is modified. wsr inspect is still a placeholder, wsr-gha is documentation-only, and the
legacy provider trait is explicitly not the accepted plugin contract. No WIT files or component
host implementation exist in the checkout. No product code, tests, dependencies or hooks changed;
no behavioral red or delivered feature is claimed.
D-007/D-009 require the host provider abstraction to delegate through versioned WIT to a signed Component. D-010 requires verified, pinned activation; its pin schema remains open. The scheduled scope explicitly forbids bypassing that architecture. Native parsing directly linked into the CLI would introduce precisely that bypass, even if labelled inspection-only.
Owner decision required before the first successful workflow-inspection slice:
Recommendation: option 1 for early inspection feedback, provided the owner accepts the temporary exception; option 2 if exercising the production plugin boundary from day one is more important. Neither option is selected by this checkpoint. Do not repeat environment preparation or substitute documentation work on subsequent runs while this decision is pending. The schedule stays unchanged.
Owner selected option 1. D-031 records the temporary built-in inspection exception; D-009 remains mandatory for the target plugin architecture. No further approval is needed for this bounded path. The beta dependency map remains a proposal outside the inspection milestone.
Implemented: the real CLI reads explicit source, invokes the pure built-in wsr-gha compiler,
and renders provider-neutral source summaries. Jobs are sorted; steps preserve source order;
runner requirements and static action references remain unresolved. Unsupported fields, expressions,
invalid shapes and duplicate identifiers fail explicitly before any stdout report. See the exact
CLI subset.
Evidence: existing CLI tests passed before product changes. The first inspection acceptance test
failed on the intended placeholder diagnostic, then passed. Additional observed red/green cycles
covered dynamic fields, invalid/empty input, and static manual-trigger inspection. All four new
CLI acceptance tests, the five existing executable contract tests, and full cargo xtask ci pass.
No hooks, global environment, product versions, registry releases or legacy type declarations changed.
No workload execution or runtime enforcement is claimed.
Delivery: preparing the first feature PR from baseline 04b4861; hosted checks and merge remain
pending. Next run must finish this PR before another slice. After merge, add step identifiers and
runner label lists with acceptance tests, then static needs graph validation, broader unsupported/
dynamic diagnostics and canonical example-workflow integration. Do not mark the entire milestone
complete or pause its schedule yet. Compiler/model-only changes do not count as delivered features.