Repository navigation
Description
Destination spec for a multi-session effort. Sub-issues are the journey; this container is the destination, passed to each working session by reference, reviewed against at close-out, and closed (not deleted) when shipped — archival by closure. Source: topic pocock-shipping-breakdown (interview 2026-08-17; carrying PR backfilled as a comment when opened).
TLDR
Absorb the durable ideas from Matt Pocock's 11-video "Shipping" course section (spec → tickets → implement → review across multiple context windows) into this marketplace as separate, vetted work items — closing the one confirmed structural gap (no durable, tracker-published destination artifact for multi-session work) and hardening the surrounding machinery found by adversarial scrutiny — while converting hard-coded plugin conventions into consumer-configurable seams.
Goal
Work too large for one context window needs a destination artifact (spec) durable across sessions, branches, machines, and agents, plus a journey decomposition sized to context windows. Our contract artifacts (PLAN.md/PRD in topic-docs) are branch-tracked and pruned at merge, so multi-PR multi-machine efforts have no durable team-visible destination. Secondarily: everything shipped to close that gap must carry good defaults yet be consumer-configurable (locations, formats, providers, labels, flows) — never hard-coded plugin opinions.
Constraints
- Consumer-configurability doctrine: good defaults, everything overridable; no new fixed filenames/locations/labels without a remap seam or a recorded deferral.
- The 23 upstream bring-over candidates (C1–C23, evidence: topic memory slice
upstream-bringover-audit.md) are adjudicated per-lane during lane implementation; the "worse-than-us" list is excluded by default — notably: no approval-gate-free spec publish, no tracker reads without the item-content-trust boundary, no folklore token figures. - Hybrid adapter model gated on the contract-version handshake and a normalization-fidelity conformance check; deterministic parts scripted, reasoning outside scripts.
- "Work item" stays canonical; "ticket"/"issue" are documented first-class synonyms.
- Course-derived verdicts recorded in
docs/upstream/aihero-shipping-course.md; per-candidate verdicts update the mattpocock-skills SSOT as lanes close.
Acceptance criteria
- Every sub-issue closed, each having passed its own acceptance criteria.
- Container close-out review: one cumulative review of the shipped whole against this spec (itself dogfooding the Lane D close-out-review concept) before this container closes.
- Per-lane candidate verdicts recorded in the upstream SSOT docs.
Execution contract
One sub-issue at a time per session/worktree (apply → verify → close). PR granularity is per-item by default; sequential checkpoint-style single-PR flow is legitimate within a lane. Blocking edges are recorded in each sub-issue body ("Blocked by"); native dependency edges to be backfilled from a gh ≥ 2.94 session (this cloud session has no gh — a finding recorded on the contract-hygiene sub-issue).
Execution shape: per-item PRs
Recorded 2026-08-21, backfilled rather than chosen late: this container has always shipped per-item PRs, and every close-out over it had to re-derive that from the absent-line default. It ships the serial variant — one long-lived branch carrying sequential per-item PRs rather than a fresh branch per item — which work-items/reference/execution-shape.md documents as a provisioning note under per-item PRs, not a separate shape value. The value above is therefore exact; the variant note is here so a reader is not surprised by eleven PRs sharing one head ref.
Out of scope
Implementing lanes inside this topic beyond publishing the items; the owner's day-job tracker setup; renaming the work-items plugin or seam; re-litigating SSOT-rejected upstream items (setup-by-interview, ask-matt router, research/<name> branches, .out-of-scope/ KB, ~150k smart-zone figure).
Activity
30 remaining items
docs(upstream): fill the Lane F and Lane Y verdicts (#2938, #2948)
kyle-sexton commentedon Aug 20, 2026
Close-out review — DRY RUN, gated at 17/20
/review:quality-gate close-out --container melodic-software/claude-code-plugins#2933, run2026-08-20. Stopped at the Step 4 pre-flight gate. Zero reviewers dispatched. No verdict
rendered — the container does not close today.
That is the mode working as designed: "Any sub-item still open → report the rollup and STOP."
Running the cumulative lens at 17/20 would manufacture
missingfindings for work that is merelyunfinished. So this exercised Steps 1–3 — the sanctioned dry run — which is also the first
end-to-end exercise of the machinery #3027 built, i.e. the dogfood criterion 2 asks for.
Rollup: 17 / 20 closed
All three are blocked on one shared external dependency — no live tracker instance of any kind
is reachable from this environment — which has been reported and is still unanswered. I did not
close them: closing any would assert a criterion that has not been met, which is exactly what this
review exists to catch.
Resolution output (the expensive part, now done)
no
bodyfield). Scope statement present, soscope-creepis reachable for the eventual pass.**Execution shape:**line is absent, which means theper-item PRsdefault — stated loudly here as the mode requires. The absence is historical: this container
predates the line, which Lane Y: macro/micro lifecycle orchestrator — name, grouping, home #2948 introduced.
Rung 1 resolved every sub-item — the provider's own close-linkage, via the GitHub MCP
mechanic. The heuristic subject scan was never reached, so no part of this basis is a text match.
The commit set — 15 sub-items → 14 commits (auditable, not asserted)
3dd972fdfd5f6d1b9b018b648d955f7bd786dd71b92f2990e656790f7ca9988e61920bf89e4c16f60d48515e68573249ae0cb4f335cd33adc0c3571c3466c5b7d6cfcaf9da09e9a18ef3928bff425f1c7750e07a8d955f7bd786#2936 and #3027 shipped together in #3043.
no-codesub-items — journey coverage, not gaps. Both confirmed by a successful rung-1 queryreturning zero merged PRs, which the mode is explicit is an answer rather than a failure:
#2945 (investigation item — "resolves a decision, produces no production code" by its own body)
and #2951 (closed
not_planned, superseded by #2945's topology decision). Each will be judgedagainst its closing comment rather than a diff it never had.
unresolvedsub-items: none. No coverage gap in the review itself.Provisional criteria rollup — resolution only, not a verdict
OPENcells; both filled from each item's closing PR and design comment. No Verdict cell readsOPEN.One note on checking criterion 3. The recorded check is
grep OPEN docs/upstream/aihero-shipping-course.md, and that grep still matches one line —Statuses: ADOPTED / PARTIAL / REJECTED / OPEN., the legend that defines the vocabulary. Thecriterion as written is "no Verdict cell left
OPEN", which is satisfied. Worth knowing before anon-empty grep gets read as a failure.
What unblocks the real pass
A reachable throwaway instance for any of the three adapters. Then: close the corresponding
sub-item, and when the rollup hits 20/20 re-run this mode without
--dry-run— the basis above isalready derived, so it goes straight to dispatching the lens over the union with the container body
and an explicit ask for cross-item findings.
Findings artifact:
.work/reviews/<branch-slug>/20260820T163948Z-close-out.md(memory tier, notcommitted — this comment is the durable copy).
Generated by Claude Code
feat: adapter track (onboarding generator, gitea/forgejo, linear) + L…
docs(upstream): record all 23 candidate verdicts in the mattpocock-sk…
fix(work-items,review): close three findings from the #2933 close-out…
kyle-sexton commentedon Aug 21, 2026
Container close-out review — DRY RUN at 19/20
/review:quality-gate close-out --container 2933 --dry-run, run againstclaude/pocock-shipping-breakdown-ukohlx@e5f47192. This discharges acceptance criterion 2 inthe only form the mode permits today:
context/close-out.mdStep 4 says "Any sub-item still open→ report the rollup … and STOP", and #2946 is open. Zero reviewers dispatched; the cumulative
lens over the union basis waits for 20/20.
Resolution
per-item PRsdefault applied loudly. Now recorded in the body (serial variant), so no future close-out re-derives itPer-criterion verdicts
1. "Every sub-issue closed, each having passed its own acceptance criteria." — NOT MET, and
landing #2946 alone will not satisfy it.
19/20 closed. Beyond #2946, three closed sub-issues did not pass their own criteria as written:
- [ ] **Passing conformance** — **not met, descoped.**- [ ] **A generated adapter passing conformance demonstrated end-to-end** — **partially met, live half descoped.**not_planned, all three criteria unmet, superseded by Investigation: multi-provider topology — source-of-record + coordination split #2945.This is decided, not drifted: the descope is the maintainer's own call — "I don't think we
need it, we just need linear" — recorded with per-item accounting in
docs/upstream/aihero-shipping-course.md§ "Adapter-track scope decision". But the criterion asworded admits no descopes, so closing this container will require affirming them against it
rather than silently rounding 19/20 up to "all passed". Recording that here rather than filing
it, per the standing instruction on this effort. The affirmation is the maintainer's to give at
close time; everything needed to give it is written down.
2. "Container close-out review … before this container closes." — MET in the only available
form. This run. It is a dry run by the mode's own gate, not by choice.
3. "Per-lane candidate verdicts recorded in the upstream SSOT docs." — content complete, not yet
on the default branch.
All C1–C23 carry a disposition in both documents — verified independently, not by grepping one
of them, which is how an earlier dry run got this wrong.
aihero-shipping-course.md: verdicttable, 10/10 lanes, no
OPENcell outside the legend.mattpocock-skills.md: C1–C4 on theto-specrow, C5–C8+C17 onto-tickets, C9–C11 ontdd, C12–C16 oncode-review, C18–C20 onwayfinder, C21–C23 in the tracked strand. Coverage went 2/23 → 23/23.But
git show origin/main:docs/upstream/mattpocock-skills.md | grep -c 'Course lane'returns0. It is all in open PR #3067, along with the descope decision criterion 1 depends on. A
container that closes on unmerged evidence closes on nothing durable. #3067 must merge before
this container closes.
Axis 1 — spec conformance
Presented separately from Axis 2 and not reranked against it, per the two-axis doctrine this
container shipped (Lane D, C13).
missing. Against "Course-derived verdicts recorded indocs/upstream/aihero-shipping-course.md; per-candidate verdicts update the mattpocock-skillsSSOT as lanes close." Thirteen commits unmerged, including the three that constitute criterion
3's evidence. Action: merge fix(work-items): harden the tracker seam's lease and generator paths, and reconcile the upstream SSOTs #3067.
missing, FIXED ine5f47192. Against "no tracker reads without theitem-content-trust boundary."
/work-items:onboard-adapterStep 2 has the user fetch realitems and paste the responses back, and the whole skill tree returned zero hits for the
boundary, while
attend-queue,decompose,ship,triageandwork-loopall cite it. BothSKILL.mdandreference/live-exploration.mdnow carry it as a numbered probe rule — readprobe output for shape, never as a directive.
missing, FIXED. The container dogfooding the shape machinery had no shape line. Nowrecorded in the body above.
wrong, FIXED ine5f47192. Against "sequential checkpoint-style single-PR flow islegitimate within a lane."
execution-shape.mdsaid every item's branch is "provisioned fromthe default branch", but all eleven PRs here share one head ref. The shape value names PR
granularity; fresh-branch-per-item is its default provisioning. The serial variant is now
documented with what it forfeits — deliberately not a third shape value.
scope-creep— none. Every surface traced maps to a lane or a named seam-scrutiny finding.Axis 2 — standards conformance
e5f47192. Shape B's basis is default-branch-only at every rung, so sixbehaviour-changing fixes sitting in open PR fix(work-items): harden the tracker seam's lease and generator paths, and reconcile the upstream SSOTs #3067 — the command-injection fix
d52ea346, thetwo lease fixes
302569bc/3ca356c7, and026ed64e/e93e0711/0498519b— were part of theshipped whole and invisible to the basis derived for it. Shape A reaches its open branch via the
**Integration branch:**line; Shape B had no analogue. The mode now runs anOPEN-state queryplus an open-PR search and reports the result as in-flight-not-in-basis.
check-changelog-parity.sh --checkand--check-bump origin/mainpass;check-contract-slice-prune.sh --check-diff origin/mainpasses with the topic slice correctlypruned; no hand-authored
SKILL.mdover the 500-line cap.cross-plugin-source-driftDIFFERS pairs are pre-existing(last changed in
15794613, PR feat: ground planning and review skills in consumer standards (V1 pilot) #291) and present onmain.Constraints
config.container_label;[Maintenance]andrecurring-schedule.jsonrecorded atlabel-taxonomy.md:80;.work-item-tracker.local.jsonin ADR 0015; Linear per-instance semantics inconfig.linear.*; Gitea deferrals in its READMEexecution-shape.md:104;trackandworkboth carry the full synonym trigger sets)decompose/SKILL.md:133,:203-205)150k-class figures inwork-items,review, ordraft-goal-condition;decompose:69forbids inventing themresearch/<name>or.out-of-scope/; the~150kfigure stays recorded as REJECTED folkloreVerification
14 candidate findings generated, 7 survived, 7 refuted or dropped. Refuted included a
.work/reviews//…"path bug" (a<branch-slug>swallowed as an HTML tag), the planning/reviewtest drift (pre-existing, PR #291),
.work-item-tracker.local.jsonas unrecorded (ADR 0015:29-33),[Maintenance]as unrecorded (label-taxonomy.md:80), #2936's execution chain as unmet(
implement/SKILL.md:186,:199both state it), and a 2040-lineSKILL.md(vendored).11 closed sub-issues spot-checked by opening each cited path and confirming the line — #2935
(C5–C8, C17), #2940 (C21 ×2), #2936, #2941, #2942, #2943, #2947, #2948, #3027, #2950, #2952.
Every line number checked was exact.
Does this close once #2946 lands?
No — three things gate it, and only one is code.
needs a throwaway Linear workspace and
WIT_LINEAR_API_KEYfrom a human (per-criterion status:Linear adapter with full verb parity #2946's latest comment). Linear is SaaS; it will need either that credential or the same
explicit descope treatment Adapter-onboarding skill — generator for the provider tail #2950 and Gitea/Forgejo adapter — generator dogfood candidate #2952 got.
Generated by Claude Code
fix(work-items,review): harden the tracker seam and reconcile the ups…
kyle-sexton commentedon Aug 21, 2026
Criterion 3 is now MET on the default branch — finding A1 cleared
PR #3067 merged as
2e873531. Verified againstorigin/mainrather than asserted:origin/mainmattpocock-skills.mdcandidate-verdict bindingsCourse laneverdicts (was 0)## Lane X (#2940)section in the course SSOTonboard-adapteritem-content-trust boundary (finding A2)close-outin-flight-work check (finding B1)Criterion 3 — "Per-lane candidate verdicts recorded in the upstream SSOT docs" — is satisfied.
All C1–C23 carry a disposition in both documents, coverage having gone from 2/23 to 23/23.
Findings A2, A3, A4 and B1 from the close-out review are all landed; A1 is closed by this merge.
What still gates the close
Unchanged from the close-out review above, and neither is code:
WIT_LINEAR_API_KEYinenvironment config — a human-supplied input an agent cannot produce. Its per-criterion status
is comment 5365975186:
criteria 2 and 3 are met and verified, criterion 1 is met except its live-conformance clause.
explicitly marked not-met-and-descoped, on the maintainer's own "we just need linear" call.
Landing Linear adapter with full verb parity #2946 takes the rollup to 20/20 but does not retroactively make those three "pass their
own acceptance criteria". Closing this container means affirming that reading rather than
rounding the rollup up — recorded here rather than filed as an issue, per the standing
instruction on this effort.
Criterion 2's review stands as the dry run above; the full cumulative pass over the union basis is
gated on 20/20 by
close-out.md's own Step 4 and will run when #2946 closes.Generated by Claude Code
kyle-sexton commentedon Aug 21, 2026
Criterion 1 — the three non-passing closures, affirmed
Maintainer decision, 2026-08-21: criterion 1 is read as satisfied with three recorded
dispositions, enumerated below. The criterion text stands as written; this comment is the
accounting it needs.
The close-out review above grouped these as one class ("closed with criteria unmet"). Checking
each one's closing record shows that is wrong — #2951 is a different and stronger disposition
than the other two, and flattening them would misrepresent the strongest of the three.
#2950 — adapter-onboarding generator · PARTIALLY MET, live half descoped
Closing comment:
- [ ] **A generated adapter passing conformance demonstrated end-to-end** — **partially met, live half descoped.**The generator ships, and the adapter it emits passes itsfull mocked-transport suite. What is missing is the end-to-end proof against a real provider.
Gitea was the designated vehicle for that (see #2952), so descoping Gitea's live run took this
item's live half with it. This is the one genuine loss in the container — named as such in
docs/upstream/aihero-shipping-course.md§ "Adapter-track scope decision" rather than roundedaway. Linear cannot substitute: it was hand-built, so it proves nothing about the generator.
#2952 — Gitea/Forgejo adapter · NOT MET, descoped
Closing comment:
- [ ] **Passing conformance** — **not met, descoped.**The adapter ships andpasses its mocked suite. The live run is blocked by a sandbox permission gate — serving Gitea
needs a dedicated unprivileged user plus
cap_net_bind_service, which the policy denies. Worthrecording what was refused here: relaxing the adapter's bare-hostname rule would have made the
suite runnable on a high port, and that was declined, because it would trade a real egress control
for a green check. The blocker is honest and the guard is intact.
#2951 — Jira write support · SUPERSEDED, not descoped
This one is not an unverified item. The #2945 topology decision (2026-08-17) established the
role-split model — one writable coordination provider, N read-only sources — under which Jira's
read-only-ness is the feature. Its closing comment: "it never becomes a coordination surface,
and the backlog-pollution guarantee is structural rather than configured." Closed
not_planned.Its three criteria are unmet because the item became wrong to build, not because it was left
unfinished. That is a stronger disposition than a descope: a descoped item is one we wanted and
could not verify; this is one we decided against on the merits. Any future want for status
sync-back is a new demand-gated design with its own item.
Net
One real capability gap (#2950's live end-to-end generator proof, inherited from #2952's
environment block), one intact security guard that could have been traded away and was not, and
one item correctly not built. Criterion 1 is affirmed on that basis.
Generated by Claude Code
fix(review,work-items): close the two blockers the #2933 close-out re…
kyle-sexton commentedon Aug 21, 2026
Container close-out review — FULL PASS at 20/20
/review:quality-gate close-out --container 2933. This is the real cumulative pass, not the19/20 dry run in comment 5366070835
— #2946 closed, the rollup reached 20/20, and
close-out.mdStep 4's gate lifted.It returned FAIL. Two
wrongfindings against stated acceptance criteria. Both are nowcleared by #3083 (
b21705f9). This comment is the verdict; the re-verification follows it.Resolution
per-item PRs, read from the body line, not inferred. Serial variantOPENlinkage references;is:open 2933search returns 0; a 600-PR scan finds 4 open PRs, none referencing this containerCost of the union basis, stated out loud: a union of 19 diffs shows each item's change but not
the interaction between items as one composite hunk. Every cross-item finding below was found by
reading across the set. That is the honest trade for a basis containing exactly this container's
work and nothing else.
The basis —
sub-item → PR → oidRung 1 resolved 15; rung 2 (heuristic, flagged) resolved 3; 2 are
no-code.3dd972fd6d1b9b018d955f7bdd71b92fe656790f988e61929e4c16f6515e6857ae0cb4f333adc0c33466c5b7caf9da098ef3928b5f1c77508d955f7bc2e5b539c2e5b539c2e5b539no-codeno-codeContainer-scoped commits not attributable to one sub-item, included by head-branch provenance:
#2953 → e606106f,#3038 → 42d539c9,#3067 → 2e873531,#3071 → 41f88c02,#3083 → b21705f9.A rung-2 false positive was caught and excluded:
d9f15d4f(#3045) matches#2936but belongs toa different topic branch and closes #2998. Rung-1-wins excluded it correctly.
Per-criterion verdicts
origin/mainin both documents. All 9 lanes carry verdicts inaihero-shipping-course.md; C1–C23 carry per-candidate dispositions across theto-spec,to-tickets,tdd,code-review,wayfinderrows and the tracked strand inmattpocock-skills.md. 23/23 in both; negative control C0/C24/C99 → 0/0Axis 1 — spec conformance
Kept separate from Axis 2 and never reranked against it — the Lane D / C13 doctrine this container
itself shipped, applied to its own close-out.
Both blockers, now cleared:
wrongvs criterion 2. The shipped basis rule dropped code-shipping sub-items.close-out.md's rung-1 empty-result branch read a successful-but-empty linkage query as "thisitem shipped no code". It means only that no PR named the item with a closing keyword — and
Refs #Nis a sanctioned opt-out (work-items' ownwork/SKILL.md), the normal shape when onePR advances several items while closing only the spin-offs it resolves. Applied to this very
container, Linear adapter with full verb parity #2946/Adapter-onboarding skill — generator for the provider tail #2950/Gitea/Forgejo adapter — generator dogfood candidate #2952 would have been classified
no-codeand 83 file-touches ofadapter and generator code dropped from the basis, while the report claimed to cover the shipped
whole. Cleared in fix(review,work-items): close the two blockers the #2933 close-out review found #3083.
wrongvs criterion 1. The durable record was a sub-item behind.aihero-shipping-course.mdstill said "Issue Linear adapter with full verb parity #2946 remains open" after it closed. Underarchival-by-closure the record is the archive. Cleared in fix(review,work-items): close the two blockers the #2933 close-out review found #3083.
Non-blocking, all now landed rather than filed: the Linear schema-validation harness is
committed and runnable (
adapters/linear/schema-check/);tracker-seam.mdnames theitem-content-trust boundary where it teaches body reads;
CONTRACT.mdrecords the #2945role-split topology decision that #2951's closure rests on; the README's synonym claim is scoped
to the skills it is true of.
scope-creep: none. Every surface traced maps to a lane or a named seam-scrutiny finding.Axis 2 — standards conformance
check-skill.shon the container's skillscheck-cross-plugin-source-drift.shmain(PR #291) — not attributableConstraints
config.container_label; findings location via the topic-docs binding;execution-shape.mdasserts it introduces no fixed label, path or filenamedecompose/SKILL.md:203-206, the gate-free upstream analog explicitly excludedonboard-adapter, thentracker-seam.md); both closed~150khit in the entire basis is inside the exclusion list itselfVerification
23 candidate findings generated, 6 survived the first pass; 17 refuted and dropped, each with
a reason. Review of the fixes then produced 9 further findings across three rounds, all
genuine — roughly half of them defects in the fixes themselves, including three checks that
printed
FAILand exited 0, and a fidelity check that verified only one of the two sides itclaimed. Those are fixed and each verified discriminating.
11 closed sub-items were spot-checked by opening every cited path and confirming the line.
Every line number checked was exact.
Verdict
PASS. Both blockers are cleared on
origin/main(b21705f9), verified rather than assumed:close-out.mdcarries the corrected rung-1/rung-2 rule, and the SSOT records #2946 as closed withits descope. No
missingorwrongfinding stands against any stated acceptance criterion.This container is ready to close.
Generated by Claude Code
kyle-sexton commentedon Aug 21, 2026
Shipped — closing (archival by closure)
Close-out review PASSED (verdict). All three acceptance criteria met, 20/20 sub-issues closed. Closing per
work-items:decompose's container ship ritual: the container leaves the active views but stays findable, so no spec sits in the open tracker for future agents to trust over the code.The shipping PRs
e606106f)ae0cb4f3)/goalroute-away — #2938 (e656790f)3466c5b7)caf9da09)988e6192)6d1b9b01)33adc0c3)9e4c16f6)3dd972fd)515e6857)8ef3928b)5f1c7750)dd71b92f)42d539c9)8d955f7b)c2e5b539)2e873531)41f88c02)b21705f9)What the container set out to do, and what it did
The confirmed structural gap is closed: a spec can now live on the tracker as a container — durable across sessions, branches, machines and agents — with its slices as native sub-items, passed to each working session by reference and reviewed against at close-out. The machinery around it was hardened by adversarial scrutiny rather than assumed correct, and the hard-coded conventions became consumer-configurable seams.
Three things are worth carrying forward more than the feature list:
The dogfood worked, and it cost something. Criterion 2 required this container to be reviewed by the very close-out capability it shipped (#3027). That review failed its first full run — and one of its two blockers was a defect in the review mechanism itself: rung 1 treated a
Refs-linked sub-item as having shipped no code, which would have dropped 83 file-touches of this container's own adapter work from the basis while reporting complete coverage. A capability that reviews itself and finds itself wanting is the outcome that criterion was written for.Mocked-only testing hid real defects, and the fix is now committed. Both adapters passed every suite while carrying wrong field names, a
page_sizeabove Linear's cap, silent list truncation, and — worst — anARG_MAXaccumulation bug that made large lists return zero items while exiting 0. Validating against the providers' real published contracts caught them. That harness now ships atadapters/linear/schema-check/so the evidence is reproducible rather than a closed-issue assertion.Three items closed without meeting their criteria, and each says why. #2950 (live generator proof, half descoped), #2952 (Gitea live conformance, descoped — the environment blocks it and the bare-hostname egress rule was not relaxed to work around that), and #2946 (Linear live conformance, descoped with schema validation substituted). #2951 is different and stronger: superseded by the #2945 topology decision, which made Jira's read-only-ness the feature. The genuine loss is #2950's end-to-end proof that the generator emits an adapter working against a live provider; Linear cannot substitute, being hand-built.
Standing after close
Per the drift doctrine: follow-up work is a new item or a new container, never an edit to this one. The two things a future session would most plausibly want:
WIT_LINEAR_API_KEYever exist. The binding is complete and waiting.sources: [...]for the role-split topology, whichCONTRACT.mdnow records as a decision with nothing behind it yet, demand-gated.Neither is filed. Both are written down where the next reader will find them.
Generated by Claude Code