Prefer spacedock new over manual --next-id for filing entities#362
Merged
Conversation
…mic create AC-1: `status --next-id` plain-text emits a stderr hint pointing at `spacedock new` (atomic-create), leaving stdout the bare id; the --json path stays hint-free and unchanged. The hint is a native-only divergence stripped in the parity normalizer (like STATE_BACKEND); its presence is pinned by a dedicated test in internal/status. AC-2: teach `spacedock new <slug> [--folder] [--id-seed S --id-actor A]` as the blessed atomic-create path in first-officer-shared-core.md (Status Viewer, ID Styles, FO Write Scope) and claude-first-officer-runtime.md, keeping --next-id as candidate-preview only. Proven by a new `filing` shared scenario in internal/ensigncycle: empty-workflow fixture + a prompt asking the FO to file one seed, graded on the FO's tool-call stream (filed via `new`, did NOT use the --next-id + hand-write pair) for both Claude and Codex, with a Pi coverage entry so TestSharedScenarioRunnerCoverage stays green. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
clkao
added a commit
that referenced
this pull request
Jun 13, 2026
clkao
added a commit
that referenced
this pull request
Jun 13, 2026
clkao
added a commit
that referenced
this pull request
Jun 14, 2026
clkao
added a commit
that referenced
this pull request
Jun 14, 2026
clkao
added a commit
that referenced
this pull request
Jun 14, 2026
…he shared-prompt change AC-1/2/4/5/6 re-confirmed green on the rebased base (greet context 48.5k <60k, 1372 pass). Claude AC-3 fix correct (cycle-1 finding resolved). #362 fold clean, new Claude assertion sound (adversarially verified). But the fix's shared-prompt change dropped the reuse cue → Codex fresh-dispatches cycle-2 → unchanged assertCodexReviewerReuse fails (3/3 Codex runs fail; PR #302 proves Codex was green pre-j9). Prompt is NOT host-neutral as claimed. Routes back to impl. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Make
spacedock newthe blessed atomic-create path for filing entities, and point operators at it fromstatus --next-id.What changed
status --next-idemits a use-newhint on stderr; stdout stays exactly the id; the--jsonpath stays hint-freespacedock new <slug>, keeping--next-idfor candidate preview onlyfilingshared runtime scenario (Claude + Codex) grading that the FO files vianew, not--next-id+WriteEvidence
go test ./...green (1329)new, zero--next-id+Write; detached audit refuted nothing materialnd