R1's identity link, site-side, and R13's first extension slot. A player types /link in game, the plugin hands them a six-character code privately, and they enter it here; the site records who owns which Steam account, and an operator sees that on core's own `/admin/users/:id` page. **The site is the author of record and the game holds nothing.** There is no per-account store in Rust that survives a wipe, and phase 7 needs the site authoritative anyway — it pushes permissions INTO the game keyed by Steam id. A copy in the game would be a second thing to reconcile every wipe, for no question it could answer better. ## D24 — a code is minted by ONE server, so every server is asked Nothing in six characters says where it came from. The fleet is asked in turn and the first `link.ok` wins; the others answer `unknown` and nothing happens there, because a code is only spent at the server that actually holds it. Asking the player to pick was rejected: a wrong pick would come back indistinguishable from a wrong code, and that is the one refusal which must not be ambiguous. **"Every reachable server refused" is not the same answer as "a server was unreachable."** Collapsing them tells a player whose server is down that their code is wrong — so they run /link again on that same server and are told the same thing for as long as it stays down. `unsure` is that case, and it says to try again rather than to fetch a new code. ## D23 — a Steam id another account holds is refused, never moved The primary key is `steam_id`, and it is load-bearing rather than tidy: phase 7 grants permissions against a link and phase 13 hangs entitlements off it, so a silent move is an account takeover performed by typing six characters. The refusal names the holder, because the advice is unusable without it. The INSERT is a plain INSERT for the same reason — `ON DUPLICATE KEY UPDATE` here would BE that move — and the duplicate-key error is the refusal for the race the check above cannot close. The way out is `/unlink` in game, which reaches the site off the ingest feed rather than through a route (the plugin has no link to delete). D25 adds the other way out: staff can sever a link from the admin panel, for a player who cannot reach that Steam account in game. ## The slot, and the hole it found in this repo's own generator `admin.users.detail` is declared in `module.json` AND registered in `index.js` AND filled by the chunk — three places, because the server half and the client half are different registrations that share one name. `swaggerFragment.js` knew only about tier routers, so the two routes under `/admin/users/:id` were generated by nothing: a fragment that was internally consistent and described two routes fewer than the module serves. A slot's mount is core's and cannot be derived here, so it is a fourth constant beside `TIER_BASE` — held to account by the frozen-manifest job, which was verified to catch exactly this by removing the two paths and watching it fail. ## Smaller things worth knowing - **Core's `useAsync` has no `refresh`.** A counter in the deps is how a page re-reads after its own write; it blanks while it re-reads, which is right here and is exactly what made it wrong for a poll. - **Every player-portal nav row needs an `icon`** — core draws one on every row, and the client suite says so. This module had no icons file until now, because the public header is text buttons. - The two new frame kinds are STAFF-only. Neither carries a code, but both name a Steam id beside a website account's activity, and that join is not a public fact about what happened on a server. - The link code route carries its own rate limiter rather than core's `accountChangeLimiter`: this is guessing somebody else's secret, not changing your own password, and a shared counter would let one policy set the other. Protocol 3 on all three declaration sites; 17 new tests, 136 green. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PMH6bw1jXMgbyF3ZWGEzSM
118 lines
4.4 KiB
JavaScript
118 lines
4.4 KiB
JavaScript
// ── The boundary, asserted ────────────────────────────────────────────────
|
|
//
|
|
// `catalogue.js` is the only thing standing between a frame carrying an IP
|
|
// address and a public page, so it gets a suite of its own rather than being
|
|
// covered incidentally by a route test.
|
|
//
|
|
// The most valuable test here is the last one: it holds the classification
|
|
// against the specification in `docs/rust-link/PROTOCOL.md` §8.4. Without it the
|
|
// two drift the first time somebody adds a kind to the protocol, and the drift
|
|
// is silent in the direction that matters — a new kind is simply never served,
|
|
// until the day somebody "fixes" that by adding it to the wrong list.
|
|
|
|
const test = require('node:test')
|
|
const assert = require('node:assert')
|
|
|
|
const catalogue = require('../catalogue')
|
|
|
|
test('an unknown kind is not public — the default is deny', () => {
|
|
assert.equal(catalogue.isPublic('player.death'), true)
|
|
assert.equal(catalogue.isPublic('something.new'), false)
|
|
assert.equal(catalogue.isPublic(''), false)
|
|
assert.equal(catalogue.isPublic(undefined), false)
|
|
|
|
// The shape of the mistake this prevents: a kind a LATER protocol adds, which
|
|
// this build ingests happily and would publish on the day it first arrived if
|
|
// the filter were a deny list.
|
|
assert.equal(catalogue.isKnown('player.location'), false)
|
|
assert.equal(catalogue.isPublic('player.location'), false)
|
|
})
|
|
|
|
test('nothing carrying an IP address, a report or an identity is public', () => {
|
|
for (const kind of [
|
|
'player.login.attempt',
|
|
'player.approved',
|
|
'player.banned',
|
|
'player.unbanned',
|
|
'player.reported',
|
|
'entity.destroyed',
|
|
// Protocol 3. A link request on a public killfeed would tell everyone which
|
|
// Steam id is about to become a named website account, and an unlink would
|
|
// say when somebody stopped being one.
|
|
'account.link.requested',
|
|
'account.unlinked',
|
|
]) {
|
|
assert.equal(catalogue.isPublic(kind), false, `${kind} must not be public`)
|
|
assert.ok(catalogue.STAFF_KINDS.includes(kind), `${kind} must be classified, not merely absent`)
|
|
}
|
|
})
|
|
|
|
test('a viewer with no kinds asked for gets the allowlist, never everything', () => {
|
|
const asPublic = catalogue.kindsFor({})
|
|
const asAdmin = catalogue.kindsFor({ admin: true })
|
|
|
|
assert.deepEqual(asPublic, [...catalogue.PUBLIC_KINDS])
|
|
assert.equal(asAdmin.length, catalogue.ALL_KINDS.length)
|
|
|
|
// The property that makes the route safe by construction: there is no argument
|
|
// a caller can omit that turns the filter off.
|
|
assert.ok(asPublic.length > 0)
|
|
assert.ok(!asPublic.includes('player.banned'))
|
|
})
|
|
|
|
test('a kind a viewer may not see is dropped, not refused', () => {
|
|
const asked = catalogue.kindsFor({ requested: ['player.death', 'player.banned'] })
|
|
|
|
assert.deepEqual(asked, ['player.death'])
|
|
|
|
// Asking for only forbidden kinds answers with nothing to select, which the
|
|
// model turns into an empty list — the events are, as far as this viewer is
|
|
// concerned, not there.
|
|
assert.deepEqual(catalogue.kindsFor({ requested: ['player.banned'] }), [])
|
|
|
|
// And an admin gets what they asked for.
|
|
assert.deepEqual(catalogue.kindsFor({ admin: true, requested: ['player.banned'] }), [
|
|
'player.banned',
|
|
])
|
|
})
|
|
|
|
test('every kind is classified exactly once', () => {
|
|
const seen = new Set()
|
|
|
|
for (const kind of catalogue.ALL_KINDS) {
|
|
assert.ok(!seen.has(kind), `${kind} appears in both lists`)
|
|
seen.add(kind)
|
|
}
|
|
|
|
assert.equal(seen.size, catalogue.PUBLIC_KINDS.length + catalogue.STAFF_KINDS.length)
|
|
})
|
|
|
|
test('the classification covers exactly the kinds protocol 3 defines', () => {
|
|
// The spec lives in another repository, so the list is restated here rather
|
|
// than parsed — and restating it is the point: adding a kind to the protocol
|
|
// without deciding who may see it has to fail somewhere, and this is where.
|
|
//
|
|
// Sourced from docs/rust-link/PROTOCOL.md §8.4.
|
|
const PROTOCOL_3 = [
|
|
'player.connected',
|
|
'player.disconnected',
|
|
'player.respawned',
|
|
'player.death',
|
|
'player.chat',
|
|
'player.tally',
|
|
'entity.destroyed',
|
|
'player.reported',
|
|
'player.banned',
|
|
'player.unbanned',
|
|
'player.login.attempt',
|
|
'player.approved',
|
|
'server.wipe',
|
|
'server.initialized',
|
|
'server.shutdown',
|
|
'account.link.requested',
|
|
'account.unlinked',
|
|
]
|
|
|
|
assert.deepEqual([...catalogue.ALL_KINDS].sort(), [...PROTOCOL_3].sort())
|
|
})
|