tor-to-proposal 2.1.5 → 2.1.7

package/bin/bid-pack.mjs

@@ -240,6 +240,21 @@ function start() {
   const torAbs = path.resolve(String(args.tor));
   if (!fs.existsSync(torAbs)) fail(`--tor not found: ${torAbs}`, 2);
 
+  process.stdout.write(
+    `# Inputs checklist — what this bid needs from you\n\n` +
+      `HAVE NOW (verified before anything runs):\n` +
+      `  [x] ToR document — ${path.basename(torAbs)}\n` +
+      `  ${args.cv ? `[x] Master CV — ${path.basename(String(args.cv))}` : `[ ] Master CV — NOT provided (add --cv <file>; the tailored CV and CV gap report will be skipped without it)`}\n\n` +
+      `PRODUCED BY THE TOOL (automatic): bid screen, compliance matrix, CV gap report,\n` +
+      `  tailored CV, pricing, financial proposal, final PDFs + zip.\n\n` +
+      `PRODUCED BY YOU + YOUR AI ASSISTANT (the tool drafts nothing in your name, then\n` +
+      `  verifies every line — this is the honesty rule):\n` +
+      `  [ ] Cover letter (template: assets/templates.md) — needed before pack\n` +
+      `  [ ] Technical proposal (one section per scored criterion/deliverable) — needed before pack\n` +
+      `  [ ] Your answers to the bid questions — via: bid-pack ask --dir ${dir}\n\n` +
+      `You will see this exact checklist again at pack time; nothing can be packaged while a box is open.\n\n`
+  );
+
   // 0. ToR -> page-tagged text
   run('pdf-extract.mjs', [torAbs, '--out', path.join(outDir, 'tor.txt'), '--signals', path.join(outDir, 'tor-signals.json')], { fatal: true, label: 'pdf-extract (ToR)' });
   state.steps.torExtract = { status: 'done' };
@@ -395,15 +410,19 @@ function apply() {
   const stillYours = fresh.items.filter((i) => i.type !== 'client');
   const stillClient = fresh.items.filter((i) => i.type === 'client');
   const state = readState();
+  state.rounds = (state.rounds || 0) + 1;
+  const round = state.rounds;
   state.steps.questions = { status: 'done', open: fresh.openCount };
   state.steps.pricing = { status: inDir('pricing.json') ? 'done' : 'awaiting-user-numbers' };
   writeState(state);
   renderPreviews();
 
   process.stdout.write(
-    `# Apply: ${applied} answer(s) recorded, ${fresh.openCount} still open\n\n` +
+    `# Apply (round ${round}): ${applied} answer(s) recorded, ${fresh.openCount} still open\n\n` +
       (stillYours.length
-        ? `## Still open — answer these (bid-pack ask)\n${mdTable(['#', 'Question'], stillYours.map((i, ix) => [ix + 1, `**${i.id}** — ${i.question}`]))}\nNEXT STEP: run  npx tor-to-proposal bid-pack ask --dir ${dir}  — it asks each of these in plain language, one at a time.\n`
+        ? `## Still open — answer these (bid-pack ask)\n${mdTable(['#', 'Question'], stillYours.map((i, ix) => [ix + 1, `**${i.id}** — ${i.question}`]))}\n` +
+          `THIS IS NORMAL AND CONVERGES: answering one round can reveal new questions when a document is filled or rendered for the first time (your pricing answer just created the financial proposal, whose gaps are now questions). Each round has fewer questions than the last — keep going until zero.\n` +
+          `NEXT STEP: run  npx tor-to-proposal bid-pack ask --dir ${dir}  — it asks each of these in plain language, one at a time.\n`
         : `NEXT STEP: run  npx tor-to-proposal bid-pack pack --dir ${dir} --fallback-pdf  to build the submission pack.\n`) +
       (stillClient.length
         ? `## Reminders — ACTIONS for you, not answers\n(These describe things to DO outside the tool: contact the client, verify a fact. They never close by typing an answer here.)\n${mdTable(['#', 'Action'], stillClient.map((i, ix) => [ix + 1, `**${i.id}** — ${i.question}`]))}\n`

package/docs/USER-GUIDE.md

@@ -44,6 +44,16 @@ Gather these into one folder on your computer (e.g. `Documents/bids/UNDP-2026-04
 | 3 | Your **money numbers** | Your minimum acceptable yearly income, your monthly costs (for pricing) |
 | 4 | Your **calendar** | So you can honestly answer "can I start when they need me?" |
 
+**Who produces what — important:** the tool prepares, verifies, and packages. It deliberately does not write two documents for you:
+
+| Document | Who produces it |
+| --- | --- |
+| Bid screen, CV gap report, tailored CV, financial proposal, pricing | **The tool** — fully automatic |
+| **Cover letter** and **technical proposal** | **You + your AI assistant** draft them (the tool gives you the template in `assets/templates.md`, the ToR extract, and your tailored CV; the tool then lints and audits every line) |
+| Answers to the bid questions (price, dates, facts) | **You** — via the `bid-pack ask` wizard |
+
+A submission can never be packaged while anything is missing — the `pack` gate will list exactly what is absent.
+
 ---
 
 ## 3. How you use it (one conversation)

package/mcp/server.mjs

@@ -322,7 +322,7 @@ function handle(msg) {
     return {
       protocolVersion: typeof params?.protocolVersion === 'string' ? params.protocolVersion : '2024-11-05',
       capabilities: { tools: {} },
-      serverInfo: { name: 'tor-to-proposal', version: '2.1.5' },
+      serverInfo: { name: 'tor-to-proposal', version: '2.1.7' },
     };
   }
   if (typeof method === 'string' && method.startsWith('notifications/')) return undefined;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "tor-to-proposal",
-  "version": "2.1.5",
+  "version": "2.1.7",
   "description": "The bid tool that refuses to lie. ToR + CV in -> verified bid pack out: cover letter, tailored CV, technical response, financial proposal, submission checklist. Deterministic CLI + agent skill for UN / NGO / government consultants.",
   "type": "module",
   "bin": {