@nanocollective/roster 0.1.0-alpha.30 → 0.1.0-alpha.31

package/docs/cost.md

@@ -12,9 +12,9 @@ Three separate bills, and they behave differently.
 
 The largest by far, and the one that scales with how much work you ask for.
 
-On a Claude subscription, through a Claude Code OAuth token, it is a flat subscription rather
-than spend per token, and what grows with a session is how much of its usage you take. That is
-how Pip's staff run.
+Roster needs access to a coding agent, not any one provider: Claude Code, Codex, Nanocoder or
+your own. On a subscription plan it is a flat cost rather than spend per token, and what grows
+with a session is how much of its usage you take. Pip's staff run that way.
 
 A session's cost is roughly its length. Ours run 11 to 55 minutes of wall clock, and a longer
 session is a bigger bill as well as a slower one. The lever that matters is not the model

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nanocollective/roster",
-  "version": "0.1.0-alpha.30",
+  "version": "0.1.0-alpha.31",
   "description": "An agent-run org, powered by GitHub. Scaffold AI staff members whose brain is a repo.",
   "type": "module",
   "bin": {

package/templates/portal/js/views/inbox.js

@@ -240,7 +240,9 @@ function inboxScreen(m, opts) {
        request; the inbox is everything else. An inbox that also listed the PRs said the same
        thing twice and made the badge beside it a number you could not act on. */
     const mine = S.inbox.items
-      .filter((i) => (issuesOnly ? products.has(i.repo) : belongsTo(i, whoseStaff)))
+      /* A staff member's link is their tracker: what is in their repo, whoever filed it. Matching
+         on who filed or was named put an issue the CMO filed for the CTO under both of them. */
+      .filter((i) => (issuesOnly ? products.has(i.repo) : !whoseStaff || i.repo === whoseStaff.brain))
       .filter((i) => (i.kind === "pr") === !!opts.prs);
     const isOpen = (i) => i.state === "OPEN";
     const scoped = mine.filter(