docs: parent_id auto-discovery — executable lookup before save#8
Merged
Conversation
Replaces the passive "how to obtain the parent ID" bullet list with an executable discovery procedure: query GET /api/v1/export, match the prior contract by label or recency, and use its ID as parent_id. Adds a "resolve parent_id before saving" preamble to the session-end save step, cross-referencing the discovery procedure. Broadens the documented classifier allow rule to cover both /save and /api/v1/export so the lookup works in auto-mode. SKILL.md documentation only. Co-Authored-By: Claude Opus 4.7 (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
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.
Fixes the gap observed live this session: an agent inheriting from a prior contract that was saved to Receipts still omitted
parent_id, because the "Inheritance and lineage" section (PR #7) documented what and when but not how to find it. The lineage feature shipped dead — API supports it, frontend renders it, but the skill never performed the lookup.Changes
GET /api/v1/export, parse the contract history, match the prior contract by label or recency, and use its ID asparent_id. Includes a fallback to save the prior contract first (capturing its returned ID) if it was never saved. Tier 1 fallback (extract ID from a known permalink) preserved.parent_idbefore saving" preamble to the session-end save step (step 2), cross-referencing the discovery procedure and stating that skipping it breaks the lineage chain.…/saveonly to"Bash(curl -s * https://receipts.liminate.dev/* *)"so the newGET /api/v1/exportcall works in auto-mode (failure mode feat: session pack v1 — 3 nouns, 2 verbs (cite, verify) #1). Tightly-scoped two-rule alternative noted.Invariants
$RECEIPTS_API_KEY— no new credentials.parent_idand saves anyway.SKILL.md).🤖 Generated with Claude Code