Marketing Agent OS test gate · 6 Oct 2026
Marketing Agent OS: the one-skill install test did not run.
We planned a project-scoped installation of one drafting skill in a disposable target. We stopped before creating the target or running the installer. The pinned source could not be reached, and a network-denied execution boundary could not be established. There are no observed installer file effects.
Where the attempt stopped
| Required gate | Observed on 6 October | Result |
|---|---|---|
| Verified immutable source | git ls-remote for intended commit adb39acf…599 exited 128: Could not resolve host: github.com. No matching checkout was found in the workspace or /tmp. | Not met |
| Working no-network boundary | unshare -n exited 1: Operation not permitted. No alternative networkless boundary was established. | Not met |
| One selected skill and disposable target | Neither was selected or created. Pinned installer, skill files and notices were not inspected in this attempt. | Not started |
| Dry-run, install and file comparison | No installer command was run. No before/after tree, hash, mode, collision or cleanup result exists. | Not observed |
The 25 September source audit named that commit but did not install the library. The project README documents selective --skill and --dry-run; this attempt did not verify their behavior at the pin. Current main is not a replacement for an immutable test revision.
What a valid rerun would require
- Obtain a reachable checkout or archive and verify its commit or tree hash. Record a different immutable commit before testing if the intended pin changes.
- Inspect the pinned installer, imported helpers, chosen skill, references, licence and notices before executing code. Reject unexpected network, executable or write effects.
- Prove a network-denied execution boundary works, then run a clean-environment dry-run and one-skill install in an empty disposable project. Keep credentials, live content, real harness mounts and account tools absent.
- Save exact commands and exit codes, stdout and stderr, baseline and final trees, file types, modes, hashes and diff. Check paths outside the selected skill, retained snapshots, repeat installation, same-name collision and verified teardown.
If either the verified checkout or network boundary is still missing, stop again. A readable repository alone is not permission to run the installer. The dossier retains the host-control boundary.
Reader answer
One local drafting skill may be worth a fictional-data, draft-only evaluation in an approved host, but this run provides no install result or safety proof. Keep model and data transfer, tools, filesystem and network access, human review, sending, audit and cleanup under the host and operator. If the team needs an enforced approval gate, autonomous sender, scheduler, credential vault or proven host safety from the skill alone, this library is the wrong choice.