Refresh guide: x

[walker-tx]

The x guide drifted from its lockfile. A draft run today would redo work.

• slug: x
• last locked: 2026-07-27T16:55:17Z
• runtime: cursor-sdk

What drifted

• doctrine/personas/it-admin.md changed. (invalidates draft, review.achievability)
• doctrine/roles/fidelity.md changed. (invalidates review.fidelity)
• doctrine/roles/review.md changed. (invalidates review.achievability)
• doctrine/roles/technical-research.md changed. (invalidates research)
• doctrine/roles/writer.md changed. (invalidates draft)
• doctrine/speakeasy-setup.md changed. (invalidates research)
• meta.yaml changed since this lock was written. (invalidates research, draft, review.fidelity, review.achievability)
• research.md changed since this lock was written. (invalidates research, draft, review.fidelity, review.achievability)
• speakeasy.md changed since this lock was written. (invalidates draft, review.fidelity, review.achievability)
• Locked against model gpt-5.6-sol; the next run uses openrouter/openai/gpt-5.6-sol. (invalidates research, draft, review.fidelity, review.achievability)
• The prompt templates changed. (invalidates research, draft, review.fidelity, review.achievability)
• Locked under the retired cursor-sdk runtime, not pi.

To refresh

Add the guide:draft label to this issue. The factory reads the slug from
this body, drafts on a new branch, and opens a pull request for review.

This ticket does not start a run on its own.

[walker-tx]

Resolved as x (X), persona it-admin.

Notes handed to the pipeline:

Refresh the existing X guide due to lockfile drift; rerun research, draft, fidelity review, and achievability review using the pi runtime.

Starting draft-guide…

[walker-tx]

Pipeline review (x)

Outcome: Reviewers passed after 2 round(s). Still skim the open questions below before merging.

Draft PR: #130

Open questions (2)

Research could not prove these from public docs. Check the boxes by replying with answers, or say “unknown / omit”. Silence + an existing hedge in the guide usually means omit / keep hedge — not a console capture.

• X's public Developer Console documentation does not publish the exact field labels or final submission label in the first-time developer enrollment flow.
• X's public documentation names the app name, description, and use-case inputs but does not publish their exact field labels or the final create-button label.

How to retry

1. Reply on this issue using the Decision N: … lines above (render fixes: apply / override; scope gaps: verified / drop / hedge) and answer open questions.
2. Re-add the guide:draft label. Distill reads the issue body and comments into pipeline notes.
3. If a factory draft PR already exists (guide/issue-<N>-*), the next run resumes on that branch and revises prior research/setup instead of starting blank. Late setup-file fidelity misses get one automatic salvage revise at finalization before surfacing here.

Source: run-record.json