Skip to content

feat(opencode): add manufacturer-grounded mechanic agent - #119

Merged
xnoto merged 4 commits into
mainfrom
feat/mechanic-agent-v047
Sep 27, 2026
Merged

xnoto merged 4 commits into
mainfrom
feat/mechanic-agent-v047

Conversation

@xnoto

@xnoto xnoto commented Sep 27, 2026

Copy link
Copy Markdown
Contributor

Summary

Add a selectable mechanic primary agent, patterned on lawnmowerman and the current knowledge-first policy. It uses owner-confirmed vehicle identity, VIN-aware manufacturer-document applicability, photo observations separated from diagnoses, and reusable private vehicle/procedure records.

Release chart 0.4.7 (appVersion unchanged). Based on eb3b16, preserving the concurrently merged 0.4.6 knowledge-first changes. Companion knowledge scaffold: agent-knowledge #17.

Fixes: N/A — explicit owner request for a vehicle mechanic agent and its knowledge home.

Type of change

  • Feature / enhancement
  • Documentation
  • GitOps desired state (manifests, kustomize, charts, SOPS/KSOPS secrets)
  • Bug fix
  • Infrastructure (OpenTofu root or module)
  • Container image
  • CI / reusable workflow
  • Refactor / cleanup
  • Breaking change

Validation

  • Required pull-request checks pass — pending PR CI.
  • Generated or centrally distributed files were regenerated by their owning automation, not hand-edited — existing Helm globs produce ConfigMap and volume entries; templates are unchanged.

Changes are limited to seven files: new agent definition, chart version, Makefile inventory/version/package assertions, existing memory-pilot test file, and three chart documentation files. New tests check mechanic mode/model/knowledge namespace, early knowledge-first gate and role markers, automotive safety/privacy/source markers, production ConfigMap source equality, and pilot exclusion. The historical parity comparison permits exactly one new agent file, without changing the old-file transforms or skipping existing-agent/config/render checks. Model, provider, image, default agent, permissions, workflow, and infrastructure are unchanged.

Independent adversarial, infrastructure-security, DevOps-integration, and release reviews ADVANCE. QA identified the expected post-rollout behavioral gap, not a static-test success claim. No Critical/High findings remain. No local checks were run or claimed. Static CI does not prove model behavior, VIN confidentiality, OEM applicability, image delivery, or a successful repair.

Impact and rollout

  1. Authored: chart 0.4.7 and tests/docs on this branch; KB scaffold is a separate private PR. Recommend merging KB #17 first.
  2. Validation: automatic PR hygiene, Helm lint/render, contract tests, and packaging; no publication on PR.
  3. Confirmation-gated: owner must explicitly approve this chart merge and its existing automatic consequences. No merge/publication/deployment authorization has been given.
  4. Automatic after approved main merge: immutable OCI publication to ghcr.io/makeitworkcloud/charts/opencode-server, then existing automation opens/updates and enables auto-merge on the kustomize-cluster version-pin PR, gated by its required checks.
  5. Separate verification: producer artifact; consuming pin; gitops-workloads root and opencode child revisions/reconciliation; Deployment/pod health; fresh-session mechanic selection and image/VIN/source/safety/privacy acceptance. Config checksum replacement loads the agent at server startup; an existing process does not hot-reload it.

No new service, subscription, OCR/VIN API, image, dependency, background maintenance schedule, or storage is introduced. No vehicle details are stored in this public chart. Actual vehicles/manual coverage remain empty until onboarding. Rollback, if needed, is a separately approved GitOps pin to the prior known-good chart; do not delete vehicle knowledge as a runtime rollback.

Safety and secrets

  • Contains no plaintext secrets, decrypted SOPS values, state files, kubeconfigs, tokens, or private endpoints
  • No local OpenTofu init/plan/apply/destroy/import/state operations were run or claimed — plans come from pull-request checks
  • Breaking or irreversible effects are described above with rollback notes

The agent requires owner-confirmed VIN transcriptions, destination-specific consent before external VIN/photo transfers, cited applicable specifications, and professional handling of traction high-voltage and SRS work. Photos cannot establish roadworthiness; safety triage precedes retrieval. AI-assisted implementation and independent reviews.

@github-actions

Copy link
Copy Markdown

Chart CI passed

Repository hygiene and Helm validation passed. View the workflow run.

@xnoto

xnoto commented Sep 27, 2026

Copy link
Copy Markdown
Contributor Author

Validation complete

PR CI run 36300899958 completed its checks at head 5100b745d4c177a3d453b0317c3884c0460d4fae:

  • test: success — repository hygiene, Helm validation and contract tests.
  • detect: success.
  • package opencode-server: success.
  • update opencode GitOps reference: skipped as expected for a PR.

No artifact was published and no GitOps pin or runtime was changed by this PR run. Behavioral image/VIN/source/safety checks remain post-rollout work, not CI-proven outcomes. Companion private KB #17 has no validation checks configured; its reviewed head is 65c2c905c18c980aad888858d86a91f977abf68a.

Ready for owner review and explicit merge authorization. Recommend KB first; chart merge triggers existing OCI publication and required-check-gated GitOps auto-merge automation.

@xnoto
xnoto merged commit 45e027f into main Sep 27, 2026
4 checks passed
@xnoto
xnoto deleted the feat/mechanic-agent-v047 branch September 27, 2026 06:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant