tenjin edit: update an existing post's answer card and metadata from the CLI

[vraspar]

Today the CLI can create a piece (tenjin publish) but not touch it afterwards. The API side has supported this for a while: PUT /api/posts/<id> does a merge-update, including the resource answer card, and the CLI already owns everything needed to call it (local wallet, keychain passphrase, buildSiwxHeader). The only way to edit a live card right now is a hand-written script that imports the CLI's internals, which is exactly the kind of thing the CLI exists to avoid.

Concrete case from today: we wanted to add natural-language paraphrases to a published piece's questionsAnswered because lexical lookup was missing organic queries (the tenjin#447 pattern; hybrid retrieval is merged upstream in tenjin PR #452 but still dark, tenjin#458). Enriching the card of an already-published piece had no CLI path at all. Republish-as-new doesn't work either: lookup does not exclude superseded posts, so you end up with duplicate candidates.

Sketch: tenjin edit <postId> reusing publish's existing card flags (--question, --scope, --exclusions, --applies-to, --as-of, ...) plus --price/--title/--body <file>, mapped onto the PUT's merge semantics (omitted flag = keep, explicit empty = clear). A --json echo of the stored card plus cacheEligible would close the loop. The web-side equivalent is the answer-card panel in tenjin PR #411; this is the agent-side twin.

[vraspar]

The one-shot script that motivated this, ran today to enrich a live card. Hardcoded to one post, but it is basically the skeleton of the command: wallet provider + buildSiwxHeader + merge-update PUT, fresh header per request because of the single-use nonce.

// run from the repo root: npx tsx card-update.tmp.mts
import { createLocalProvider } from './src/lib/wallet/local';
import { buildSiwxHeader } from './src/lib/siwx';
import { dataDir } from './src/lib/paths';

const POST_ID = '019f8d4b-ed51-76f6-97e4-dc0ee8a3e622';
const BASE = 'https://tenjin.blog';
const CHAIN = 'eip155:8453';

const QUESTIONS = [
  // merge semantics replace the array, so restate existing entries + add new ones
  '...existing and new questionsAnswered strings...',
];

const provider = createLocalProvider({ dir: dataDir(), env: process.env });
const signer = await provider.getSigner();

async function siwxFetch(method: string, body?: unknown) {
  const header = await buildSiwxHeader(signer, { baseUrl: BASE, chainId: CHAIN });
  const res = await fetch(`${BASE}/api/posts/${POST_ID}`, {
    method,
    headers: {
      'SIGN-IN-WITH-X': header,
      ...(body ? { 'Content-Type': 'application/json' } : {}),
    },
    ...(body ? { body: JSON.stringify(body) } : {}),
  });
  return { status: res.status, json: await res.json().catch(() => ({})) };
}

const before = await siwxFetch('GET');           // 200, echoes stored resource card
const put = await siwxFetch('PUT', { resource: { questionsAnswered: QUESTIONS } });
console.log(put.json?.resource?.cacheEligible);  // true, missing: []

Notes for the implementation: GET-then-PUT is required for list fields since the PUT replaces arrays wholesale (restate + append); the server echoes cacheEligible/cacheEligibleMissing on the PUT response, which is the natural --json output; and each request needs its own SIWX header (nonce burns per write).