Repository navigation
Install a pinned native SpecGraph runtime for product workspaces - #813
Conversation
Spec-ID: SG-SPEC-0007 Proposal-ID: 0231 Spec-Impact: tooling Spec-Rationale: Package a fixed source snapshot and route existing product commands without changing supervisor authority.
Proposal-ID: 0231 Spec-Impact: tooling Spec-Rationale: Verify snapshot installation, product isolation and supervisor worktree/review behavior using a deterministic executor.
Proposal-ID: 0231 Spec-Impact: tooling Spec-Rationale: Distinguish run records from other JSON artifacts in the installed-runtime probe.
Proposal-ID: 0231 Spec-Impact: tooling Spec-Rationale: Verify the snapshot contents against the selected source commit.
Proposal-ID: 0231 Spec-Impact: tooling Spec-Rationale: Prevent consumer modules and Python environment variables from shadowing the installed runtime.
Proposal-ID: 0231 Spec-Impact: tooling Spec-Rationale: Preserve installed source evidence, deterministic refinement outcome and the repeat-initialization blocker.
Proposal-ID: 0231 Spec-Impact: tooling Spec-Rationale: Record the exact source revision and distinguish workspace fixture entries in repeat-init diagnostics.
Proposal-ID: 0231 Spec-Impact: tooling Spec-Rationale: Require a versioned completed installation receipt and full source commit before launching an installed runtime.
Proposal-ID: 0231 Spec-Impact: docs-only Spec-Rationale: Distinguish receipt readiness from verification of installed tree integrity.
Proposal-ID: 0231 Spec-Impact: tooling Spec-Rationale: Bind the installed runtime observation to the source containing its readiness policy.
Proposal-ID: 0231 Spec-Impact: tooling Spec-Rationale: Record individually reviewed implementation dispositions including the named readiness specification.
Proposal-ID: 0231 Spec-Impact: tooling Spec-Rationale: Keep decision evidence within the source reference size limit.
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: baa871d7d4
ℹ️ 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".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Intent Atoms · v1Scope: specification YAML in Status: complete Proposal obligations · draftStatus: complete for declared fields Informational only; this report does not gate merge readiness. |
HyperReviewЭскиз по исходникам · Состав · изменения в проекции --- before.hc
+++ after.hc
@@ -1 +1,4 @@
SpecGraph
+ NativeRuntime
+ RuntimeReadiness
+ WorkspaceRoutingВыбранные связи · после Пояснения, источники и ограниченияСуть измененияPR добавляет документированный и реализованный поток установки закреплённого снимка SpecGraph: установщик извлекает архив, создаёт venv, записывает receipt, а launcher проверяет его готовность и направляет команды в явно выбранный workspace. README и DocC вводят пользовательскую точку входа и описывают границы изоляции. Отдельная документация уточняет ограничения и открытый дефект повторной инициализации после появления .worktrees; это описание, а не исправление поведения. В неизменённых файлах нет нового изменения логики подсчёта решений или режима Product Workspace. Установка не включает Git-историю, изменения рабочего дерева или данные проектов; ASP и каноническая публикация не заявлены. Интерпретация выбранных исходников; порядок узлов не означает порядок выполнения.
Связи и основанияСвязи описаны отдельно от вложенности
Связи в Hypercode (.hcs)Это неполные выборки связей из каждой версии. Отсутствие связи в одной из выборок не устанавливает её добавление или удаление. Пустой лист означает, что связи для этой версии не выбраны. before.hcsafter.hcsОтветственности и источники
Границы анализаPR #813: Исходников в анализе: 27; пропущено: 20. Компилятор проверил структуру Hypercode и ссылки. Соответствие интерпретации коду и поведение программы этим не доказаны. Анализ ограничен предоставленными исходниками и фрагментами контекста; выполнение программы не наблюдалось.
Неизменённых файлов контекста по Git blob: 6. Их фрагменты до и после могут различаться охватом.
Точные диапазоны источников по узламSpecGraph
NativeRuntime
RuntimeReadiness
WorkspaceRouting Ок или не ок? CI · результаты проверокСнимок для Результат check-run не доказывает выполнение конкретного теста, полноту покрытия или соответствие архитектуре.
Снимок неполный: показано не более 12 проверок. Отсутствие, ожидание или сбой CI не блокируют архитектурный обзор. Review gate: review thread. |
SpecificationMetrics · diagnostic PR measurement
Collection: base
Scope: files assigned |
Proposal-ID: 0231 Spec-Impact: tooling Spec-Rationale: Preserve relative local source semantics when fetching from an isolated temporary Git repository.
Proposal-ID: 0231 Spec-Impact: tooling Spec-Rationale: Retain the review root cause and source-bound installation verification.
Proposal-ID: 0231 Spec-Impact: tooling Spec-Rationale: Bind the reviewed source changes and updated PR description to existing individual dispositions.
Summary
Install a stable, pinned full SpecGraph source snapshot and dedicated Python environment without coupling product work to the developer checkout. Proposal 0231 captures the user request, draft obligations and runtime evidence.
Motivation
Agents need to use the existing supervisor and SpecDraft in independent projects while SpecGraph development proceeds separately.
Goals
Changes
RUNTIME_READY_SPECfor the completed, versioned installation receipt; forwarding, archive extraction and environment creation remain adapters/I/O mechanics. The receipt policy is not a source-tree integrity check.Spec Evidence
Spec-ID: SG-SPEC-0007
Proposal-ID: 0231
Spec-Impact: tooling
Spec-Rationale: Preserve source attribution and supervisor authority while delivering a pinned independent runtime.
Intent-Decision-Review: tools/intent_decision_reviews/0231_native_runtime.json
Validation
Commands run:
Results:
ffcdcd9eb3a8465692e19aa4d9a12e7f322bc0bd; selected files matched Git objects. Both project workspaces initialized and ran the advisor, targeted supervisor dry-run and SpecDraft read. An injected deterministic executor ran a real Git worktree refinement:done,review_pending, no validation errors. No real model/provider was invoked. Seedocs/reviews/0231_native_runtime/verification.json.--source .now resolves the caller checkout before Git changes directory; a real install ofdf773af49d92121b9261dd5369fe0868086e5569and the two-workspace smoke passed. Seedocs/reviews/0231_native_runtime/relative-source-verification.json. URL and SSH syntax are covered by focused tests..worktreesinitializer limitation; the import-shadowing fixture adds a second expected unexpected entry. Separate existing proposal 0227 owns the workspace initialization boundary.Risks / Notes
Checklist