cesnimda
7.0 KiB
AUTO-00: repository, prompt and CLI audit
Audited 29 October 2026. This is orchestrator construction, not roadmap authorization.
Source identity and isolation
The primary checkout was on planning/int-global-jobs-00 at 0ec9f98, with unrelated local AGENTS, ignore, Docker, skills and graph files. Those files were preserved. A managed worktree was created at C:\Users\Connor\.codex\worktrees\autonomous-roadmap-01\Job tracker, based on the actual local 5032ccb and using branch codex/autonomous-roadmap-01.
The ongoing pre-Phase-10 branch occupies C:\Users\Connor\.codex\worktrees\pre-p10-ux\Job tracker. It was not checked out, edited, tested, reset or published by this task. A fresh git ls-remote --heads origin refs/heads/test/pre-phase10-ux-acceptance returned 994bf8f8bbf0df3c53111ca7f66af97fe0680013. The local branch pointed to 5032ccb, two commits ahead of that ref. Remote connectivity worked for this read; publication of the pending commits had not succeeded. Publishing this orchestrator's branch does not update that pre-Phase-10 ref.
The new manifest records the full locally resolved baseline SHA. It does not assume main contains the accepted redesign. Final source acceptance may move while this work is underway: the owner must nominate the finished accepted baseline before enabling real execution.
Actual source prompt mapping
Root: E:\Storage\Projects\Active\temp docs\final. automation/SOURCE_INVENTORY.json records filenames, byte sizes and SHA256. Imported files retain original bytes, including stop/approval instructions. The manifest imposes the owner's requested execution sequence, independently of source filename numbers.
| Sequence | ID | Actual source | Checkpoints |
|---|---|---|---|
| 05 | PHASE-10 | Prompt 5 — Phase 10.txt |
P10-00 through P10-05 |
| 06 | PRODUCT-REVIEW-01 | Prompt 6 — PRODUCT-REVIEW-01.txt |
independent assessment, ranked roadmap |
| 07 | INT-GLOBAL-JOBS-01 | done/Prompt 7 — INT-GLOBAL-JOBS-01.txt plus repository docs/planning/global-jobs-prompts/ |
GJ-01 through GJ-08 |
| 08 | I18N-01 | owner-supplied I18N/00_MASTER_ORCHESTRATOR.md and all nine stage prompts |
I18N-00 through I18N-08 |
| 09 | LAUNCH-SITE-01 | Prompt 10 - homepage.txt |
research, four concepts, approved implementation, qualification |
| 10 | SECURITY-AUDIT-01 | owner-supplied jobjakt-security/MASTER_PROMPT.md, detailed prompts, resources, templates and skill |
SEC-00 through SEC-16 |
| 11 | RELEASE-READINESS-01 | prompt 11 - release readiness.txt |
inventory, qualification, recommendation |
The initially empty Prompt 8 - security audit.txt is not the source for the security stage. The owner's later directory resolves it. done is a file location, not evidence that GJ-01–08 have run. GJ-00's planning-only restriction and security's DO NOT START THIS NOW! remain intact; explicit later signed entry approval is necessary to authorize those implementation scopes. The UI 9.1–9.6 files are also preserved, unassigned, for Product Review scope reconciliation; they are not silently executed as translations or dropped from the inventory.
Per checkpoint, the runner sends the complete master prompt, complete applicable detailed prompt, common resources, prior authority, stored results, blockers and verified owner decisions. Duplicate all-phase compilations and unrelated detailed checkpoint prompts are preserved on disk without repeatedly expanding the entire roadmap into every session.
Overlaps and integration ownership
GJ owns provider rights, search, taxonomy/geography IDs, saved searches and advertisement language. I18N reuses those owners and independently qualifies locale registry/preferences, message coverage, notifications, profession terminology, document languages, scripts/fonts and native review. Country, UI locale, ad language and CV/letter language remain distinct. GJ-01 preferences/i18n work does not satisfy the full I18N programme. I18N-05 must consume accepted GJ contracts, retaining its own tests and review.
I18N-07 owns marketing locale/SEO contracts and fixtures; LAUNCH-SITE owns visual concepts and the final homepage. The homepage still requires four high-fidelity concepts and a human design choice. Release qualification reruns relevant acceptance instead of treating earlier security or localisation completion as production approval. Remaining AI qualification and optional product initiatives must be explicitly ranked in Product Review, never implicitly activated by these stages.
One serial branch per workstream is the shipped default, with each detailed stage as a bounded checkpoint. Some packs prefer separate substage branches or one branch per finding. Those preferences are preserved in the prompts and must be resolved explicitly in the signed workstream scope before execution; the model must block conflicting instructions. No concurrent Git edits are allowed in one worker checkout. The integration ref fast-forwards through accepted published stage commits; no merge operation exists.
Official CLI and local capability
Installed: codex-cli 0.163.0. Local codex exec --help confirms stdin prompts (-), --json, --output-schema, --output-last-message, --ignore-user-config, --sandbox workspace-write, --cd and independent sessions. The implementation uses these supported switches and does not use the removed --full-auto or unrestricted execution. Account authentication is reused through an auth-only dedicated CODEX_HOME; no production key variables are inherited by child build/test jobs.
Official references: non-interactive execution, CLI reference, Windows sandbox. The native Windows 0.163.0 codex sandbox --help exposes commands directly, without a windows subcommand. This platform grammar is used by independent test execution.
The attempted sandbox invocation failed with CryptUnprotectData failed: 2148073483. No unrestricted fallback was attempted. PowerShell 7, Python 3.12 and Git are installed. A real model-backed worker session and native sandbox enforcement have not been qualified on this host. Synthetic subprocess protocol tests are separate evidence, not a native-sandbox certification.
Deliberate deployment gates
The controller is implemented, but installing source code is not granting execution. The initial manifest has executionEnabled: false. The stage qualification adapter is deliberately marked unconfigured: provider/browser/Python/PDF/security/preservation commands and exact suite membership must be qualified against the final accepted runtime and host. Guessing those commands from historical test counts would manufacture acceptance. This is an operator setup/entry condition, never a bypass or a passing result.
No live MariaDB, Docker, Ollama, model, production filesystem, main branch, external paid provider, notification service or real backlog stage was operated. The only external access was authorized official documentation and scoped Git publication/read checks.