chore: propagate skill-lib #128 operational snapshot

[erinepshovel-code]

Scope and exact identities

Consume canonical The-Interdependency/skill-lib 321e721fb660e0fea5bb8c37d943611963039a57 (merged #128) in The-Interdependency/stack, starting from Stack 07f327e1d49d3fce2fa58dcdda1a89f9041e132a. This is operational maintenance only; no research graduation, runtime deployment, or merge authority.

• Root skill-lib/: exact 62-file producer delta from 023ae12bb19ced1a4f2494ed6507fc31285a5b8e, all 255 resulting files match canonical paths, modes, and blobs. Snapshot tree: e34f55936651a53154420c0f1f2ad7c3273d0e56.
• Separate .agents/skills/stack-update/SKILL.md: exact canonical blob 9ec21b07d01a099021778a0c8774b810c2619d63, with README and provenance updated together after canonical propagation-helper dry-run/apply.
• Operational projections: root machine/human manifests, root README, backend fresh-making provenance and README, VM_SETUP current-snapshot label, and AHBG current consumed-snapshot declaration.
• Work-graph digest: f4acf6c40732f486388ed43df896d6e21590f1bf567310a0f45814c56d506268.
• Canonical generated skill-lib_msdmd.ts is copied verbatim, not regenerated as Stack evidence. No target-local doctrine divergence is introduced.

Preserved boundaries

All 41 research-participant identities, research files, canonical libs pins, scientific baselines, EPAC release evidence, receipts and historical source identities remain unchanged. No stopped repair is touched.

backend/deploy/VM_CONTACT.md retains its separately pinned 023ae12 vm-mcp bootstrap and acceptance evidence. The current operational source snapshot and this historical deployment/runbook identity serve different purposes. This PR does not deploy or requalify the VM.

Old open/conflicting #82 is untouched. Merged #83 explicitly superseded it and supplies this PR's current-main baseline; no branch history or changes from #82 are imported. This batch remains pinned to approved #128 even if later producer changes merge.

Validation and usage

Run from the Stack root:

python tools/check_stack_consistency.py
PYTHONDONTWRITEBYTECODE=1 python3 -W error::ResourceWarning -m unittest discover -s backend/tests -t . -v
python3 -m compileall -q backend frontend
bash -n backend/ops/*.sh
python skill-lib/interdependent-work-graph/portfolio_plan.py docs/work-graphs/repository-plan-report.json --output /tmp/stack-portfolio-validation.json

Observed locally:

• Stack consistency: pass, 7 repositories / 41 research participant identities.
• Backend suite: 54 run, 52 pass, 2 PostgreSQL integration checks skipped because no explicitly disposable database is configured.
• Python compilation, shell syntax, portfolio validation/source ancestry, municipal handoff SHA-256, and whitespace checks: pass.
• Vendored canonical drift and compliance: pass, zero errors/warnings.
• Cross-boundary source identity: exact root snapshot and separate skill blob; old/new msdmd/ trees identical. Backend generator identity is identical across old/new snapshots under the same Python 3.13 / Node 24.19.0 / TypeScript 5.8.3 runtime (0372b744d778faa33ee19d96233db8fb65c91af3edad81cc6425848199a02322).
• Independent diff review caught the stale backend README doctrine claim; it is corrected. Independent final review approved exact tree fcd2ac4c3e4ceac34806c3dbd1f22e598394c49c with no remaining substantive findings; reviewed diff SHA-256 7d767fba53b13fb0914acffb833dcad0cc9080c927ebbd3c4b24fb6a709aa5f8.

hmmm: PostgreSQL and real-VM acceptance remain deployment gates, not passes. Generic manifest generation is inapplicable here because the snapshot has no pyproject.toml; the owning Stack consistency/source-identity gates are used. No new Stack-wide MSDMD collection or scientific replay is claimed. A transient cloud execution disconnect recovered; the final backend rerun again passed 52 tests with the same 2 PostgreSQL skips. Consistency and whitespace checks also passed after the final README correction. Remote candidate tree fcd2ac4c3e4ceac34806c3dbd1f22e598394c49c exactly matches the locally verified tree.

Standing: draft for review; do not merge or deploy.

Exact-head completion (2026-10-14 03:30 UTC)

Published head 068ec653c8e50e52151e53916cd618d568ad45e6 was fetched and matched the verified candidate tree exactly. All 16 check runs succeeded for this head, including Stack consistency, backend tests, immutable EPAC release replay, UCHC full-corpus input integration, and CodeQL. Independent exact-tree review is clean. No hosted review submission or comment is present; no external review was requested. The PR remains a mergeable draft, unmerged and undeployed.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-14T04:05:27.219296Z	068ec65	Draft marked ready

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.