[kinqsradio]

Change

Use the outer Orbyn Engineering workspace for engineering policy and skills. The target application no longer carries a copied installation or public-skill pin. This follows the approved nested-only direction; existing third-party targets keep their own instructions and skills.

• Remove duplicated root agent entrypoints, generated host defaults/roles/discovery, 34 installed skill owners, lock, installation/sync helpers and the skills-upstream workflow.
• Rehome the classifier, aggregate CI gate and deployment-receipt validator to scripts/ci_scope.py, retaining the complete MIT notice. Retire the obsolete skills lane; docs/full classification, conservative unknown-path handling and deployment trust checks remain.
• Preserve all 5,018 retained source snapshot files and five gitlink pins through a project-owned integrity checker. Keep tools/rea, tools/pstack, upstream manifest and gitmodules unchanged.
• Preserve Orbyn stack, commands, disposable database, operations and UI conventions in docs/development.md, docs/operations.md and docs/design.md. Link the outer workspace from CONTRIBUTING and README; add a concise contributor template.
• Reject recognized retired installation controls (catalog, lock and old installer/sync workflow/scripts) and force-added raw research. Allow future project-owned AGENT/AGENTS/CLAUDE/Cursor guidance, local skills and host settings; do not infer ownership from filenames, matching skill names or prose. Preserve untracked private work, product connector documentation and source snapshots.

Existing work

Product documentation/MIT/contact PR #231 was reconciled, source-checked and merged first at beb060d. This branch includes that actual merged base; its product changes are not duplicated in this cleanup's diff. Five old draft application stacks remain untouched because historical checks do not establish source equivalence or merge readiness.

Checks and limits

At eec865c: 24 focused disposable CI, safe-server-preflight, source-integrity and workspace-boundary fixtures pass. Static source checks pass for 5,018 files and five gitlinks; local link targets pass for 22 current guides. Changed authored documents are formatted, Python parses and whitespace checks pass. Application/runtime/tool snapshot diff is empty.

The owning lead reviewed the initial cleanup and boundary/template delta. Following the human’s clarified future-project-guidance scope, the final guard allows target-owned instructions/skills/settings and limits rejection to known retired installation controls and raw research. Negative-ignore and bare raw-research-root safeguards remain. The owning lead approved this five-file scope correction on the exact head. The first local retry for this correction encountered seven ENOSPC environment errors; after space recovered without task deletions, all 24 fixtures passed. The failed attempt and successful retry are retained. Hosted CI must pass on this exact final head. CI changes require the full application lane. No local app build, native provider, REA engine, client/model setup or deployment ran. Dated work records retain historical paths and are excluded from current-guide link validation.

The active legacy primary checkout has not moved: live processes still use it. Its untracked audit documents, output and private configuration remain owned there. A later fresh independent nested clone can be prepared under the public workspace's ignored repo/Orbyn, with repo/orbyn-wt task worktrees; this does not transfer private files, databases or process ownership. Nesting is not a claim of live host policy/skill discovery.

Workspace

Engineering changes are coordinated between the public-workspace owner and Orbyn Builder, using the existing relevant guidance and project source. Public policy/tooling changes merged separately through PRs #19 and #20. This candidate changes only Orbyn's target boundary. The REA engine/runtime upgrade remains deferred.