Repository navigation
REQ 108
The engine shall generate a new pipeline JSON, VIPM TOML, and evidence report for an explicitly selected source-manifest packed-library build, with configuration validity conditional on deterministic source and schema checks plus a successful local Ollama review.
Fork and organization owners need reusable onboarding from their source without copying another owner's build intent, inventing dependencies, or treating model approval as proof of a successful native build. Implementation and adoption evidence are tracked in issue #219.
The operator supplies a local checkout, immutable Git revision, credential-free repository URL, source manifest, selected build key, local Ollama endpoint and model, and a new output directory. The .NET 10 tool parses TOML and LabVIEW XML without executing source, checks tracked source against the requested revision, checks relative paths without following links outside the checkout, and resolves exactly one existing packed-library build specification. The source manifest supplies project identity, explicit LabVIEW year and bitness, and exact declared VIPM versions; unknown values are refused rather than inferred from a developer's installed packages. The selected XML supplies the SBOM path, artifact output directory, and PPL filename; Destination[0].destName and TgtF_targetfileName must agree, and generated artifactPath names that file rather than the containing directory. Output JSON disables automatic cleanup and selects native Windows only. TOML preserves declared dependency versions and the selected build rather than enabling unrelated package builds. Provenance binds source revision, source-file digests, output paths and digests, model identity, and model review. Only HTTP(S) literal loopback endpoints are accepted, redirects are refused, model input is structured evidence rather than executable instructions, and review has bounded time and output tokens. Missing Ollama, malformed or inconclusive review, model rejection, or any deterministic failure leaves configuration validity false. Schema validation remains independently required and cannot be bypassed by model approval. Existing output directories and source files remain unchanged. Configuration validity is distinct from native-build proof, which stays false until a separately verified build. No registration, workflow dispatch, source execution, or asset cleanup is part of generation.
The initial local prototype passed 29 .NET tests. Its pinned real adoption checkout labview-benchmark-actor-plugins/dependencies at commit 6629c2cd742906161bae34993679ecc492b2592e generated schema-valid JSON/TOML, passed the existing registration validator, and received local qwen2.5:7b acceptance with no blockers. That historical generation is not a new native-build proof or a rerun under later policy inputs. artifactPath is the explicit PPL file formed from Bld_localDestDir plus agreeing Destination[0].destName and TgtF_targetfileName; mismatched or unsafe names are rejected. The integrated source-config suite now passes 91 .NET tests and Ubuntu/Windows CI; mandatory model identity, budget, privacy and lifecycle evidence is allocated to REQ-109, REQ-111, REQ-113, and REQ-114. Native build proof remains false; stable promotion and native Windows acceptance retain separate gates. See TEST-110.
High
tools/source-config/ProjectBuddy.SourceConfig.Tests/ConfigurationTests.cs (DerivesSchemaValidConfigurationAndPreservesSelectedIntent, RejectsAmbiguousOrUnsafePplArtifactNames), tools/source-config/ProjectBuddy.SourceConfig.Tests/GenerationTests.cs, .github/workflows/ci-assurance.yml job source-config, the generated projectbuddy/source-config@1 report, and the independent registration validator
tools/source-config/ProjectBuddy.SourceConfig/Program.cs (CLI and exit codes), tools/source-config/ProjectBuddy.SourceConfig/Configuration.cs (Create, WindowsPath: TOML/XML extraction, exact PPL output-file resolution, and schema checks), tools/source-config/ProjectBuddy.SourceConfig/Generation.cs (RunAsync, ReadPinned, CheckLinks: source pinning, provenance, review gate, and non-overwriting output), and tools/source-config/ProjectBuddy.SourceConfig/OllamaReview.cs (Endpoint, RunAsync, Parse: loopback-only bounded model review and model identity)
Candidate behavior integrated and regression/CI verified; historical generation evidence retained, no stable-release or native-build proof