rallysmith 0.1.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Potentially problematic release.


This version of rallysmith might be problematic. Click here for more details.

Files changed (39) hide show
  1. package/.claude-plugin/mcp.json +12 -0
  2. package/.claude-plugin/plugin.json +22 -0
  3. package/.codex-plugin/mcp.json +12 -0
  4. package/.codex-plugin/plugin.json +38 -0
  5. package/LICENSE +201 -0
  6. package/README.md +42 -0
  7. package/assets/rallysmith-icon.png +0 -0
  8. package/assets/rallysmith-icon.svg +31 -0
  9. package/cli.mjs +4 -0
  10. package/docs/dashboard.md +67 -0
  11. package/docs/distribution.md +119 -0
  12. package/docs/host-support.md +44 -0
  13. package/docs/release-policy.md +33 -0
  14. package/docs/server.md +79 -0
  15. package/docs/usage.md +95 -0
  16. package/launcher.mjs +199 -0
  17. package/notices/MCP-SDK-LICENSE +216 -0
  18. package/notices/RUST-1.97.1-COPYRIGHT-library.html +5556 -0
  19. package/notices/THIRD-PARTY-NOTICES.md +1781 -0
  20. package/notices/preview-dependency-notices.zip +0 -0
  21. package/notices/preview-notice-inventory.tsv +630 -0
  22. package/package.json +68 -0
  23. package/skills/independent-review/SKILL.md +8 -0
  24. package/skills/independent-review/agents/openai.yaml +6 -0
  25. package/skills/independent-review/assets/icon.svg +6 -0
  26. package/skills/scoped-delegation/SKILL.md +8 -0
  27. package/skills/scoped-delegation/agents/openai.yaml +6 -0
  28. package/skills/scoped-delegation/assets/icon.svg +6 -0
  29. package/skills/start-team/SKILL.md +34 -0
  30. package/skills/start-team/agents/openai.yaml +6 -0
  31. package/skills/start-team/assets/icon.svg +6 -0
  32. package/skills/start-team/references/board-and-messaging.md +13 -0
  33. package/skills/start-team/references/cli-workflow.md +13 -0
  34. package/skills/submission-handoff/SKILL.md +12 -0
  35. package/skills/submission-handoff/agents/openai.yaml +6 -0
  36. package/skills/submission-handoff/assets/icon.svg +6 -0
  37. package/skills/team-coordination/SKILL.md +14 -0
  38. package/skills/team-coordination/agents/openai.yaml +6 -0
  39. package/skills/team-coordination/assets/icon.svg +6 -0
@@ -0,0 +1,12 @@
1
+ {
2
+ "mcpServers": {
3
+ "rallysmith": {
4
+ "command": "npx",
5
+ "args": [
6
+ "-y",
7
+ "rallysmith@0.1.4",
8
+ "claude"
9
+ ]
10
+ }
11
+ }
12
+ }
@@ -0,0 +1,22 @@
1
+ {
2
+ "name": "rallysmith",
3
+ "version": "0.1.4",
4
+ "description": "Coordinate independent Codex and Claude chats through a local mailbox.",
5
+ "author": {
6
+ "name": "Piyeycorp",
7
+ "url": "https://github.com/Piyeycorp"
8
+ },
9
+ "homepage": "https://github.com/Piyeycorp/rallysmith#readme",
10
+ "repository": "https://github.com/Piyeycorp/rallysmith",
11
+ "license": "Apache-2.0",
12
+ "icon": "./assets/rallysmith-icon.png",
13
+ "keywords": [
14
+ "teams",
15
+ "coordination",
16
+ "codex",
17
+ "claude",
18
+ "mcp"
19
+ ],
20
+ "skills": "./skills/",
21
+ "mcpServers": "./.claude-plugin/mcp.json"
22
+ }
@@ -0,0 +1,12 @@
1
+ {
2
+ "mcpServers": {
3
+ "rallysmith": {
4
+ "command": "npx",
5
+ "args": [
6
+ "-y",
7
+ "rallysmith@0.1.4",
8
+ "codex"
9
+ ]
10
+ }
11
+ }
12
+ }
@@ -0,0 +1,38 @@
1
+ {
2
+ "name": "rallysmith",
3
+ "version": "0.1.4",
4
+ "description": "Coordinate independent Codex and Claude chats through a local mailbox.",
5
+ "author": {
6
+ "name": "Piyeycorp",
7
+ "url": "https://github.com/Piyeycorp"
8
+ },
9
+ "homepage": "https://github.com/Piyeycorp/rallysmith#readme",
10
+ "repository": "https://github.com/Piyeycorp/rallysmith",
11
+ "license": "Apache-2.0",
12
+ "keywords": [
13
+ "teams",
14
+ "coordination",
15
+ "codex",
16
+ "claude",
17
+ "mcp"
18
+ ],
19
+ "skills": "./skills/",
20
+ "mcpServers": "./.codex-plugin/mcp.json",
21
+ "interface": {
22
+ "displayName": "Rallysmith",
23
+ "shortDescription": "Coordinate AI agent teams",
24
+ "developerName": "Piyeycorp",
25
+ "category": "Developer Tools",
26
+ "capabilities": [
27
+ "MCP Tools",
28
+ "Instructions"
29
+ ],
30
+ "brandColor": "#F26B1D",
31
+ "logo": "./assets/rallysmith-icon.png",
32
+ "composerIcon": "./assets/rallysmith-icon.svg",
33
+ "websiteURL": "https://github.com/Piyeycorp/rallysmith",
34
+ "defaultPrompt": [
35
+ "Set up a Rallysmith team for this project."
36
+ ]
37
+ }
38
+ }
package/LICENSE ADDED
@@ -0,0 +1,201 @@
1
+ Apache License
2
+ Version 2.0, January 2004
3
+ http://www.apache.org/licenses/
4
+
5
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
6
+
7
+ 1. Definitions.
8
+
9
+ "License" shall mean the terms and conditions for use, reproduction,
10
+ and distribution as defined by Sections 1 through 9 of this document.
11
+
12
+ "Licensor" shall mean the copyright owner or entity authorized by
13
+ the copyright owner that is granting the License.
14
+
15
+ "Legal Entity" shall mean the union of the acting entity and all
16
+ other entities that control, are controlled by, or are under common
17
+ control with that entity. For the purposes of this definition,
18
+ "control" means (i) the power, direct or indirect, to cause the
19
+ direction or management of such entity, whether by contract or
20
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
21
+ outstanding shares, or (iii) beneficial ownership of such entity.
22
+
23
+ "You" (or "Your") shall mean an individual or Legal Entity
24
+ exercising permissions granted by this License.
25
+
26
+ "Source" form shall mean the preferred form for making modifications,
27
+ including but not limited to software source code, documentation
28
+ source, and configuration files.
29
+
30
+ "Object" form shall mean any form resulting from mechanical
31
+ transformation or translation of a Source form, including but
32
+ not limited to compiled object code, generated documentation,
33
+ and conversions to other media types.
34
+
35
+ "Work" shall mean the work of authorship, whether in Source or
36
+ Object form, made available under the License, as indicated by a
37
+ copyright notice that is included in or attached to the work
38
+ (an example is provided in the Appendix below).
39
+
40
+ "Derivative Works" shall mean any work, whether in Source or Object
41
+ form, that is based on (or derived from) the Work and for which the
42
+ editorial revisions, annotations, elaborations, or other modifications
43
+ represent, as a whole, an original work of authorship. For the purposes
44
+ of this License, Derivative Works shall not include works that remain
45
+ separable from, or merely link (or bind by name) to the interfaces of,
46
+ the Work and Derivative Works thereof.
47
+
48
+ "Contribution" shall mean any work of authorship, including
49
+ the original version of the Work and any modifications or additions
50
+ to that Work or Derivative Works thereof, that is intentionally
51
+ submitted to Licensor for inclusion in the Work by the copyright owner
52
+ or by an individual or Legal Entity authorized to submit on behalf of
53
+ the copyright owner. For the purposes of this definition, "submitted"
54
+ means any form of electronic, verbal, or written communication sent
55
+ to the Licensor or its representatives, including but not limited to
56
+ communication on electronic mailing lists, source code control systems,
57
+ and issue tracking systems that are managed by, or on behalf of, the
58
+ Licensor for the purpose of discussing and improving the Work, but
59
+ excluding communication that is conspicuously marked or otherwise
60
+ designated in writing by the copyright owner as "Not a Contribution."
61
+
62
+ "Contributor" shall mean Licensor and any individual or Legal Entity
63
+ on behalf of whom a Contribution has been received by Licensor and
64
+ subsequently incorporated within the Work.
65
+
66
+ 2. Grant of Copyright License. Subject to the terms and conditions of
67
+ this License, each Contributor hereby grants to You a perpetual,
68
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
69
+ copyright license to reproduce, prepare Derivative Works of,
70
+ publicly display, publicly perform, sublicense, and distribute the
71
+ Work and such Derivative Works in Source or Object form.
72
+
73
+ 3. Grant of Patent License. Subject to the terms and conditions of
74
+ this License, each Contributor hereby grants to You a perpetual,
75
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
76
+ (except as stated in this section) patent license to make, have made,
77
+ use, offer to sell, sell, import, and otherwise transfer the Work,
78
+ where such license applies only to those patent claims licensable
79
+ by such Contributor that are necessarily infringed by their
80
+ Contribution(s) alone or by combination of their Contribution(s)
81
+ with the Work to which such Contribution(s) was submitted. If You
82
+ institute patent litigation against any entity (including a
83
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
84
+ or a Contribution incorporated within the Work constitutes direct
85
+ or contributory patent infringement, then any patent licenses
86
+ granted to You under this License for that Work shall terminate
87
+ as of the date such litigation is filed.
88
+
89
+ 4. Redistribution. You may reproduce and distribute copies of the
90
+ Work or Derivative Works thereof in any medium, with or without
91
+ modifications, and in Source or Object form, provided that You
92
+ meet the following conditions:
93
+
94
+ (a) You must give any other recipients of the Work or
95
+ Derivative Works a copy of this License; and
96
+
97
+ (b) You must cause any modified files to carry prominent notices
98
+ stating that You changed the files; and
99
+
100
+ (c) You must retain, in the Source form of any Derivative Works
101
+ that You distribute, all copyright, patent, trademark, and
102
+ attribution notices from the Source form of the Work,
103
+ excluding those notices that do not pertain to any part of
104
+ the Derivative Works; and
105
+
106
+ (d) If the Work includes a "NOTICE" text file as part of its
107
+ distribution, then any Derivative Works that You distribute must
108
+ include a readable copy of the attribution notices contained
109
+ within such NOTICE file, excluding those notices that do not
110
+ pertain to any part of the Derivative Works, in at least one
111
+ of the following places: within a NOTICE text file distributed
112
+ as part of the Derivative Works; within the Source form or
113
+ documentation, if provided along with the Derivative Works; or,
114
+ within a display generated by the Derivative Works, if and
115
+ wherever such third-party notices normally appear. The contents
116
+ of the NOTICE file are for informational purposes only and
117
+ do not modify the License. You may add Your own attribution
118
+ notices within Derivative Works that You distribute, alongside
119
+ or as an addendum to the NOTICE text from the Work, provided
120
+ that such additional attribution notices cannot be construed
121
+ as modifying the License.
122
+
123
+ You may add Your own copyright statement to Your modifications and
124
+ may provide additional or different license terms and conditions
125
+ for use, reproduction, or distribution of Your modifications, or
126
+ for any such Derivative Works as a whole, provided Your use,
127
+ reproduction, and distribution of the Work otherwise complies with
128
+ the conditions stated in this License.
129
+
130
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
131
+ any Contribution intentionally submitted for inclusion in the Work
132
+ by You to the Licensor shall be under the terms and conditions of
133
+ this License, without any additional terms or conditions.
134
+ Notwithstanding the above, nothing herein shall supersede or modify
135
+ the terms of any separate license agreement you may have executed
136
+ with Licensor regarding such Contributions.
137
+
138
+ 6. Trademarks. This License does not grant permission to use the trade
139
+ names, trademarks, service marks, or product names of the Licensor,
140
+ except as required for reasonable and customary use in describing the
141
+ origin of the Work and reproducing the content of the NOTICE file.
142
+
143
+ 7. Disclaimer of Warranty. Unless required by applicable law or
144
+ agreed to in writing, Licensor provides the Work (and each
145
+ Contributor provides its Contributions) on an "AS IS" BASIS,
146
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
147
+ implied, including, without limitation, any warranties or conditions
148
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
149
+ PARTICULAR PURPOSE. You are solely responsible for determining the
150
+ appropriateness of using or redistributing the Work and assume any
151
+ risks associated with Your exercise of permissions under this License.
152
+
153
+ 8. Limitation of Liability. In no event and under no legal theory,
154
+ whether in tort (including negligence), contract, or otherwise,
155
+ unless required by applicable law (such as deliberate and grossly
156
+ negligent acts) or agreed to in writing, shall any Contributor be
157
+ liable to You for damages, including any direct, indirect, special,
158
+ incidental, or consequential damages of any character arising as a
159
+ result of this License or out of the use or inability to use the
160
+ Work (including but not limited to damages for loss of goodwill,
161
+ work stoppage, computer failure or malfunction, or any and all
162
+ other commercial damages or losses), even if such Contributor
163
+ has been advised of the possibility of such damages.
164
+
165
+ 9. Accepting Warranty or Additional Liability. While redistributing
166
+ the Work or Derivative Works thereof, You may choose to offer,
167
+ and charge a fee for, acceptance of support, warranty, indemnity,
168
+ or other liability obligations and/or rights consistent with this
169
+ License. However, in accepting such obligations, You may act only
170
+ on Your own behalf and on Your sole responsibility, not on behalf
171
+ of any other Contributor, and only if You agree to indemnify,
172
+ defend, and hold each Contributor harmless for any liability
173
+ incurred by, or claims asserted against, such Contributor by reason
174
+ of your accepting any such warranty or additional liability.
175
+
176
+ END OF TERMS AND CONDITIONS
177
+
178
+ APPENDIX: How to apply the Apache License to your work.
179
+
180
+ To apply the Apache License to your work, attach the following
181
+ boilerplate notice, with the fields enclosed by brackets "[]"
182
+ replaced with your own identifying information. (Don't include
183
+ the brackets!) The text should be enclosed in the appropriate
184
+ comment syntax for the file format. We also recommend that a
185
+ file or class name and description of purpose be included on the
186
+ same "printed page" as the copyright notice for easier
187
+ identification within third-party archives.
188
+
189
+ Copyright [yyyy] [name of copyright owner]
190
+
191
+ Licensed under the Apache License, Version 2.0 (the "License");
192
+ you may not use this file except in compliance with the License.
193
+ You may obtain a copy of the License at
194
+
195
+ http://www.apache.org/licenses/LICENSE-2.0
196
+
197
+ Unless required by applicable law or agreed to in writing, software
198
+ distributed under the License is distributed on an "AS IS" BASIS,
199
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
200
+ See the License for the specific language governing permissions and
201
+ limitations under the License.
package/README.md ADDED
@@ -0,0 +1,42 @@
1
+ # Rallysmith
2
+
3
+ Coordinate independent Codex and Claude chats with shared project rules, tasks, messages, and artifacts. Rallysmith stores project data in a local mailbox.
4
+
5
+ ## Install
6
+
7
+ Requires Node.js 22 or newer and Windows x64 or Linux x64 with glibc 2.34 or newer.
8
+
9
+ ```sh
10
+ npx -y rallysmith setup
11
+ ```
12
+
13
+ Restart Codex and Claude after setup. With a Codex CLI that supports local plugin installation, Rallysmith appears under **Plugins** in Codex. Setup also configures Claude Code and detects an existing standard Claude Desktop configuration on Windows. Run `rallysmith setup-status` to see the registered hosts and mailbox path.
14
+
15
+ ## Start a team
16
+
17
+ 1. Open a manager chat in your project folder. Ask it to create a Rallysmith project and team, or give it an invitation to join an existing project.
18
+ 2. Review the project, roster, and rules in the approval prompt. Approve to create the team and open its member chats.
19
+ 3. Give work to the manager. Use the dashboard to follow tasks and check team readiness.
20
+
21
+ ## Open the dashboard
22
+
23
+ | Command | Opens |
24
+ | --- | --- |
25
+ | `rallysmith --desktop` | Desktop dashboard |
26
+ | `rallysmith --web` | Browser dashboard |
27
+
28
+ The Linux desktop dashboard requires WebKitGTK 4.1. In browser mode, use the link printed by Rallysmith. Press **Q** in the terminal or select **Stop** in the dashboard to end the session.
29
+
30
+ ## Update
31
+
32
+ Close the agent apps and dashboard, then run `npx -y rallysmith@latest setup`. Setup keeps your existing mailbox location.
33
+
34
+ ## Uninstall
35
+
36
+ Close the agent apps and dashboard, then run this command.
37
+
38
+ ```sh
39
+ rallysmith uninstall
40
+ ```
41
+
42
+ Uninstall removes the global npm command, native package, registered integrations, and skills. It keeps your mailbox, saved mailbox location, and existing chats. Use `rallysmith setup-status` before uninstalling to find your mailbox for backup.
Binary file
@@ -0,0 +1,31 @@
1
+ <svg xmlns="http://www.w3.org/2000/svg" width="512" height="512" viewBox="0 0 100 100" role="img" aria-label="Rallysmith">
2
+ <!-- Rallysmith mark, "Forge glow + handoff route". Master for sizes above 32 px; see rallysmith-icon-small.svg. -->
3
+ <defs>
4
+ <radialGradient id="rs-glow" cx="76" cy="24" r="58" gradientUnits="userSpaceOnUse">
5
+ <stop offset="0" stop-color="#F26B1D" stop-opacity="0.55"/>
6
+ <stop offset="0.45" stop-color="#F26B1D" stop-opacity="0.12"/>
7
+ <stop offset="1" stop-color="#F26B1D" stop-opacity="0"/>
8
+ </radialGradient>
9
+ <linearGradient id="rs-heat" x1="30" y1="76" x2="62" y2="26" gradientUnits="userSpaceOnUse">
10
+ <stop offset="0" stop-color="#F4F5F7"/>
11
+ <stop offset="0.7" stop-color="#F4F5F7"/>
12
+ <stop offset="1" stop-color="#FFD3B0"/>
13
+ </linearGradient>
14
+ </defs>
15
+ <rect width="100" height="100" rx="22" fill="#15181D"/>
16
+ <rect width="100" height="100" rx="22" fill="url(#rs-glow)"/>
17
+ <path d="M30 76V26h18a13 13 0 0 1 0 26H30M46 52l18 24" fill="none" stroke="url(#rs-heat)" stroke-width="10" stroke-linecap="round" stroke-linejoin="round"/>
18
+ <g>
19
+ <circle cx="20" cy="88" r="1.8" fill="#F4F5F7" opacity="0.25"/>
20
+ <circle cx="32" cy="89" r="1.9" fill="#F4F5F7" opacity="0.32"/>
21
+ <circle cx="44" cy="89" r="2" fill="#F4F5F7" opacity="0.4"/>
22
+ <circle cx="56" cy="88.5" r="2.1" fill="#F4F5F7" opacity="0.48"/>
23
+ <circle cx="68" cy="87" r="2.2" fill="#FFD3B0" opacity="0.58"/>
24
+ <circle cx="79" cy="82" r="2.3" fill="#FFD3B0" opacity="0.68"/>
25
+ <circle cx="86" cy="72" r="2.4" fill="#FFB27A" opacity="0.78"/>
26
+ <circle cx="89" cy="60" r="2.5" fill="#F26B1D" opacity="0.88"/>
27
+ <circle cx="88" cy="48" r="2.6" fill="#F26B1D"/>
28
+ </g>
29
+ <path d="M75 14Q75 25 86 25Q75 25 75 36Q75 25 64 25Q75 25 75 14Z" fill="#FFF1E6"/>
30
+ <path d="M75 17Q75 25 83 25Q75 25 75 33Q75 25 67 25Q75 25 75 17Z" fill="#F26B1D"/>
31
+ </svg>
package/cli.mjs ADDED
@@ -0,0 +1,4 @@
1
+ #!/usr/bin/env node
2
+ import { launch, reportLaunchError } from './launcher.mjs';
3
+
4
+ launch().catch(reportLaunchError);
@@ -0,0 +1,67 @@
1
+ # Dashboard app (React)
2
+
3
+ The owner's workspace page uses React + TypeScript with Vite. This app lives in
4
+ `apps/dashboard/`. The native executable embeds the dashboard staged by `pnpm ship`
5
+ under the repository's ignored `dist/native-resources/dashboard/` directory.
6
+ Rebuild the Rust executable after shipping the page to include the updated dashboard.
7
+
8
+ ## How it ships
9
+
10
+ `pnpm build` type-checks, bundles, and runs `scripts/package-page.mjs`, which writes:
11
+
12
+ | File | Goes to | Notes |
13
+ |---|---|---|
14
+ | `dist/page/runtime.html` | `../../dist/native-resources/dashboard/runtime.html` | Page shell with the CSS inlined and the native app's placeholders (`__NONCE__`, `__CONNECT__`, `<!--SESSION-->`, `<!--SNAPSHOT-->`, `<!--APP-->`). |
15
+ | `dist/page/runtime.js` | `../../dist/native-resources/dashboard/runtime.js` | One classic script (IIFE), inserted at `<!--APP-->` inside the nonce'd `<script>`. |
16
+ | `dist/page/bundled-notices.md` | `../../packaging/notices/THIRD-PARTY-NOTICES.md` | License texts of the JavaScript and stylesheet dependencies recorded by a plugin in `vite.config.ts`. The build fails on a license outside MIT, 0BSD, ISC, BSD or Apache-2.0. |
17
+
18
+ `pnpm ship` updates the notice section and runs `../../packaging/prepare-native-resources.mjs`,
19
+ which stages the dashboard together with the shared skills and brand assets. The native build
20
+ embeds these resources; it does not run the dashboard build from Cargo. Build or ship the dashboard
21
+ before rebuilding Rust. The page keeps the same Content-Security-Policy: no external resources,
22
+ scripts only via the per-launch nonce, `connect-src` limited to the local app.
23
+
24
+ ## Rules kept from the vanilla page
25
+
26
+ - Agent and mailbox text is untrusted: React renders it as text; `tests/security.test.ts` fails if
27
+ app code writes raw HTML or reaches the network.
28
+ - Writes go through `/api/task`, `/api/task/create` and `/api/stop` with the per-launch CSRF
29
+ header and `expected_revision`; a conflict rereads the workspace.
30
+ - Honest states: "Review requested · no verdict recorded", "Reported complete · not independently
31
+ verified", Done needs reported evidence, Deferred needs a blocker, bounded-snapshot notices only
32
+ when data was cut off, a static snapshot never offers editing.
33
+
34
+ ## Source layout
35
+
36
+ - `src/main.tsx` loads the embedded session and snapshot; `src/App.tsx` selects the browser or snapshot router.
37
+ - `src/app/` contains route definitions, route helpers, filters and the workspace page.
38
+ - `src/features/` groups the activity, board, messages, projects, search, tasks and team views.
39
+ - `src/components/` contains shared dashboard components; `src/components/ui/` contains shadcn components.
40
+ - `src/hooks/` holds custom hooks, `src/data/` handles workspace data and `src/fixtures/` contains the synthetic workspace.
41
+ - Tests live alongside their subjects. `src/App.test.tsx` covers whole-app flows and `tests/` holds project-wide checks.
42
+ - `src/index.css` retains the dashboard theme and imports Tailwind utilities without Preflight. The dashboard uses shadcn buttons, badges, inputs, labels and text areas with that theme.
43
+
44
+ ## Develop
45
+
46
+ Uses pnpm (version pinned in `package.json`'s `packageManager`; `corepack enable` provides it).
47
+
48
+ ```bash
49
+ pnpm install --frozen-lockfile
50
+ pnpm dev # http://127.0.0.1:5173 with the synthetic fixture in src/fixtures/workspace.fixture.ts
51
+ pnpm test # Vitest + Testing Library (jsdom)
52
+ pnpm build
53
+ pnpm ship # build, update notices, then stage ../../dist/native-resources
54
+ ```
55
+
56
+ Dependency versions are pinned exactly in `package.json` and locked in `pnpm-lock.yaml`.
57
+ `pnpm-workspace.yaml` only accepts versions published at least 3 days ago and lets no
58
+ dependency run install scripts. If an install reports a version as too new, pin the newest
59
+ release older than that instead of adding an exemption.
60
+
61
+ On the board, drag empty space with the primary mouse button to scroll horizontally, including the viewport below the lanes. Cards retain task dragging and click-to-open; lane buttons, inputs and links retain their normal behavior. Mouse-wheel, trackpad and native touch scrolling remain available. The cursor changes from grab to grabbing during a pan.
62
+
63
+ Projects, teams and workspace views use React Router and support bookmarks and browser back and forward navigation. The live dashboard uses browser paths such as `/projects/<project-id>/teams/<team-id>/board`; opening one still requires the browser session established by the private startup link. Disconnected HTML snapshots use hash routing with equivalent `#/projects/...` links so their navigation stays within the exported file.
64
+
65
+ Visible labels, tooltips, accessible descriptions, filters and notifications use project, team and member names or task titles. Missing names use readable fallbacks such as “Unnamed member”; IDs stay internal to lookup keys, navigation and API requests. Referenced IDs inside displayed status text resolve to authorized names or a generic reference label. Opening a task preserves its stored content unless the user changes it.
66
+
67
+ Live Activity reads authenticated `/api/activity` pages of 50 entries for the selected project/team and filters. Scrolling near the end loads the next page; **Load more activity** provides the same action for keyboard use or browsers without intersection observation. Filtering searches stored history before selecting a page. New activity merges into the visible list while older loaded pages remain available; failed requests preserve the list and offer Retry. The Activity count has a `+` while more entries are available. Agent views and disconnected exports retain their snapshot bounds; an exported Activity limitation appears only inside Activity, never as an activity warning on the Board.
@@ -0,0 +1,119 @@
1
+ # Build and distribution
2
+
3
+ Rallysmith has one public npm command, `rallysmith`, and host plugins containing its MCP configuration and five shared skills. The Node launcher selects the matching native package for the current OS/CPU and passes arguments, streams and exit status through. The explicit `setup` command uses npm to install the selected version globally when needed. Node 22 or newer is required.
4
+
5
+ Install from npm with `npx -y rallysmith setup`. Public native packages are available for Windows x64 and Linux x64. Check the [support matrix](host-support.md) before advertising another target. The marketplace commands below require a published distribution catalog.
6
+
7
+ ## Host plugin installation
8
+
9
+ For Codex, add the marketplace and install Rallysmith in the desktop app's Plugins Directory:
10
+
11
+ ```sh
12
+ codex plugin marketplace add Piyeycorp/rallysmith --ref distribution
13
+ ```
14
+
15
+ For Claude Code, use its plugin commands:
16
+
17
+ ```sh
18
+ claude plugin marketplace add Piyeycorp/rallysmith#distribution
19
+ claude plugin install rallysmith@rallysmith
20
+ ```
21
+
22
+ The distribution branch contains only generated catalogs at `.agents/plugins/marketplace.json` and `.claude-plugin/marketplace.json`. Each catalog points to an exact published Rallysmith version on the npm registry.
23
+
24
+ The npm package contains both host manifests, their MCP configuration and all five skills. The plugin commands use `npx` to resolve the pinned Rallysmith version and its matching native package. See the official [Codex plugin guide](https://developers.openai.com/plugins/build/plugins) and [Claude marketplace reference](https://code.claude.com/docs/en/plugins/marketplace-reference).
25
+
26
+ The build copies the existing Rallysmith logo from `assets/brand/` into the plugin's `assets/` directory. Codex references it through `interface.logo` and `composerIcon`; Claude's manifest provides the documented `icon` listing field. Each skill keeps its own SVG and `agents/openai.yaml` presentation metadata, included in both plugin packages and native standalone setup. Normal MCP startup also advertises the bundled logo through `serverInfo.icons`, using a data URI with no image download. Rendering is host-dependent: Claude Code ignores the listing icon at load time, and Claude's skill reference does not document per-skill custom icons. Bundling an asset or advertising an MCP icon does not guarantee those Claude screens display it. See the [Claude manifest reference](https://code.claude.com/docs/en/plugins-reference#directory-listing-fields).
27
+
28
+ Claude Desktop's owner-review connection remains separate from the Claude Code plugin. Install the command and select only that additional host when using the plugin:
29
+
30
+ ```sh
31
+ npx -y rallysmith setup --hosts claude-desktop
32
+ ```
33
+
34
+ This does not install Code skills or change the Code plugin. Top-level Desktop chats do not automatically import filesystem Code skills.
35
+
36
+ Claude Desktop project chats select embedded owner-review cards automatically. If the card is unavailable, review remains pending. The Code and Desktop configurations use the same `claude` provider command and require no review environment switches. A direct local connector may display Claude's generic icon even when the server advertises the Rallysmith logo. Claude Desktop documents a separate, user-installed extension format for packaged branding. [Claude Desktop extensions](https://support.claude.com/en/articles/10949351-getting-started-with-local-mcp-servers-on-claude-desktop)
37
+
38
+ ## Account setup
39
+
40
+ To install Rallysmith from npm:
41
+
42
+ ```sh
43
+ npx -y rallysmith setup
44
+ rallysmith setup-status
45
+ rallysmith --desktop
46
+ ```
47
+
48
+ Setup installs the selected version in the global npm prefix and registers the native executable using its absolute path. Codex and Claude then start that executable directly. For a Node installation with an unwritable global prefix, use a user-writable npm prefix. If the host registration step reports a conflict after npm installs the package, resolve the conflict in the host and rerun setup.
49
+
50
+ Account-wide npm setup uses `codex plugin add` when supported by the Codex CLI on PATH. It installs the branded plugin from a local Rallysmith catalog, with its skills and the installed native executable. An upgrade replaces Rallysmith's own direct Codex entry and skills. Setup uses direct Codex registration when plugin installation is unavailable or skills are scoped to a project.
51
+
52
+ Setup also configures Claude Code and detects an existing Claude Desktop configuration on Windows/macOS. Use `--hosts codex,claude-code,claude-desktop` to select hosts explicitly. Setup refuses installations with competing Rallysmith plugin or MCP routes. Remove the competing integration through its host before running setup.
53
+
54
+ Setup runs in Rust, using the same native path and permission checks as the runtime. It uses `toml_edit` to preserve Codex comments/formatting and updates only the Rallysmith JSON entry. It records replaced content and owned skill hashes in a private registration receipt. Conflicts require explicit `--replace`; modified owned files, malformed configuration, unsafe paths and detected concurrent edits fail visibly. Failed setup rolls back staged integration writes.
55
+
56
+ Location options are absolute paths: `--home` creates an isolated account fixture, `--codex-home` selects Codex configuration, `--data-dir` selects the shared data root, and `--project` scopes copied skills to one checkout while MCP registration remains account-wide. Retain the home/Codex location options when inspecting or removing that setup. See [usage](usage.md).
57
+
58
+ Changing the selected hosts or project skill scope requires uninstall followed by setup. Direct Claude Code setup refuses an ambient `CLAUDE_CONFIG_DIR` override instead of guessing its configuration layout; isolated `--home` ignores ambient overrides. A private serialized receipt larger than 4 MiB is rejected before integration writes.
59
+
60
+ Fresh Windows setup creates an account-private mailbox directory at `%LOCALAPPDATA%\Rallysmith\data\mailbox`. Setup keeps an existing saved data directory or a mailbox already present at the original Windows location. The selected data root is saved separately from integration ownership. Normal MCP, CLI and UI processes recover it, including after integration removal. Existing data and host chats are never moved or removed. Older installation receipts are not silently adopted; select the existing data directory explicitly when switching installation routes.
61
+
62
+ ## Local package build
63
+
64
+ Build the server and desktop shell with Rust 1.97.1 and their locked dependencies. The build checks both executables' versions and writes their paths and digests to a JSON manifest. Keep it with the local build outputs. [Tauri system requirements](https://v2.tauri.app/start/prerequisites/#system-dependencies)
65
+
66
+ ```sh
67
+ npm run build:dashboard
68
+ node packaging/build-native.mjs > dist/native-build.json
69
+ node packaging/build-release.mjs --native-build dist/native-build.json --out /absolute/output
70
+ ```
71
+
72
+ The native build remaps account, repository, Cargo cache, Rust toolchain and target-directory source paths to neutral prefixes. It preserves target-specific linker settings, including Windows static CRT, and scans UTF-8/UTF-16 binary content before accepting the executable. `--offline` uses already fetched locked dependencies. Clear ambient compiler flags and `RALLYSMITH_NATIVE_RESOURCES` before a release build. Both npm and native builds use the reviewed skill files listed in [the source allowlist](https://github.com/Piyeycorp/rallysmith/blob/main/packages/skills-files.txt).
73
+
74
+ The package builder stages a root package under `OUTPUT/root`, a native package under `OUTPUT/platforms/OS-CPU`, both npm tarballs directly under `OUTPUT`, and catalogs under `OUTPUT/distribution`. Its JSON result includes `rootDirectory`, `rootTarball`, `platformDirectory`, `platformTarball` and `distributionDirectory`. It checks both binaries against the same native build manifest, including version, OS/CPU and SHA-256 digests. The native package places the server and desktop executables beside each other under `bin/` and includes their SHA-256 metadata and notices. Linker-generated paths still require native checks on each target.
75
+
76
+ Host definitions are source templates under `packages/plugin/`, using neutral filenames. No marketplace or plugin definition lives at a discoverable source-root host path. `prepare-npm.mjs` generates version-aligned `.codex-plugin/plugin.json`, `.codex-plugin/mcp.json`, `.claude-plugin/plugin.json` and `.claude-plugin/mcp.json` only inside the staged npm root. Templates and catalogs are excluded from the npm tarball. Always pack/publish the staged `OUTPUT/root` candidate or its generated tarball; running `npm pack` directly in the source checkout does not generate the plugin files.
77
+
78
+ You can prepare the root package and catalogs without a native executable:
79
+
80
+ ```sh
81
+ node packaging/prepare-npm.mjs --out /absolute/output
82
+ claude plugin validate /absolute/output/root/.claude-plugin/plugin.json --strict
83
+ claude plugin validate /absolute/output/distribution/.claude-plugin/marketplace.json --strict
84
+ ```
85
+
86
+ Publish the qualified native npm packages and the matching launcher first. To release the host marketplace catalogs, publish the contents of `OUTPUT/distribution`, including `.agents` and `.claude-plugin`, to the release-only `distribution` branch. Direct npm setup requires only the npm packages.
87
+
88
+ To test without a public registry, install both generated tarballs together in a disposable prefix:
89
+
90
+ ```sh
91
+ npm install --global --prefix /absolute/test-prefix /absolute/output/piyeycorp-rallysmith-linux-x64-0.1.4.tgz /absolute/output/rallysmith-0.1.4.tgz --offline --ignore-scripts
92
+ ```
93
+
94
+ Run the prefix's `rallysmith` command with `npm_config_prefix` set to that test prefix and `setup --home /absolute/disposable-home`. The automated [native package smoke](https://github.com/Piyeycorp/rallysmith/blob/main/packages/npm-launcher/test/native-smoke.mjs) verifies the one-command setup through a local registry, then launches the registered native executable with the registry offline and checks recovery and uninstall in an isolated account.
95
+
96
+ The root lists exact-version optional packages `@piyeycorp/rallysmith-{win32,darwin,linux}-{x64,arm64}`. Only qualified targets receive published binaries. Missing or mismatched packages fail with a diagnostic; users must not omit optional dependencies. npm owns native package installation, updates and removal. Windows builds use a static CRT.
97
+
98
+ ## Update and removal
99
+
100
+ Close affected MCP/UI processes before npm replaces native files, especially on Windows. Update the npm package using npm, and update the host plugin through that host. Plugin MCP commands pin the release version, so keep plugin and npm release versions aligned. Direct registrations are refreshed by running the new version's `setup`; it preserves the selected data root.
101
+
102
+ Run `rallysmith uninstall` from the global npm installation. The native command first removes unchanged owned integrations and restores replaced entries. If that step succeeds, the launcher waits for the native process to exit and removes the launcher and its platform package through npm. Owner edits can prevent integration removal. Saved data-root selection, databases, credentials, backups and host chats remain.
103
+
104
+ If you run the native executable directly, its `uninstall` command removes host integrations and skills. Remove marketplace plugins through the host's plugin manager.
105
+
106
+ ## Validation and notices
107
+
108
+ ```sh
109
+ npm test
110
+ npm run check:native
111
+ npm run test:native
112
+ python -m unittest discover -s tests/integration -v
113
+ npm run test:desktop
114
+ node packages/npm-launcher/test/native-smoke.mjs --native-build dist/native-build.json --release-dir /absolute/output
115
+ ```
116
+
117
+ Native CI runs each target separately. Platform skips or binary-header fixtures do not qualify native execution. macOS requires its own passing runner and live host qualification. When UI source changes, run `pnpm test` and `pnpm ship` in `apps/dashboard/`, then rebuild the executable. See [apps/dashboard/README.md](dashboard.md).
118
+
119
+ After fetching locked Cargo dependencies for the release matrix, refresh attribution with `python packaging/collect-cargo-notices.py`. The collector records upstream texts and hashes without downloading packages or exposing local source paths. Packages include the [project license](../LICENSE), [third-party notices](../notices/THIRD-PARTY-NOTICES.md) and dependency texts, excluding live data, local settings, logs and internal qualification notes. Follow the [release policy](release-policy.md) before publication.
@@ -0,0 +1,44 @@
1
+ # Host and platform qualification
2
+
3
+ Rallysmith uses the same native program for Codex, Claude and the owner dashboard. Platform support and host integration are separate checks: passing a Linux installer test does not qualify Claude Desktop there. Unsupported capabilities must be reported rather than substituted or bypassed.
4
+
5
+ ## Native platform status
6
+
7
+ | Target | Implementation | Qualification |
8
+ |---|---|---|
9
+ | Windows x64 | Private ACL storage; static CRT; native setup; npm platform package | Debug/release runtime suites and optimized offline npm package roundtrip checked; clean-machine release qualification remains separate |
10
+ | Linux x64 (glibc) | POSIX ownership/modes, XDG data path, native browser launcher/setup, npm platform package | Debug/release Rust and applicable Python checks on Debian 12; both native npm packages and headless UI checked on Debian 13; Desktop host qualification remains separate |
11
+ | macOS arm64/x64 | POSIX ownership/modes plus extended ACL rejection, Application Support paths, native browser launcher, npm setup | Native debug/release runtime suites, applicable Python checks, npm packaging and installed-binary smoke passed on both architectures; Desktop host qualification remains separate |
12
+ | Windows/Linux arm64 | Asset selection and build-format checks | No native runtime qualification or release asset claimed |
13
+
14
+ The native CI matrix covers Windows x64, Linux x64, macOS arm64 and macOS x64 with Rust 1.97.1. All four targets passed their builds, debug/release Rust tests, applicable Python suites, npm package tests and actual installed-binary smoke checks in [native verification run 44026000573](https://github.com/Piyeycorp/rallysmith/actions/runs/44026000573). Each release candidate must pass that matrix; this does not qualify untested Desktop host behavior. Missing platform packages fail visibly.
15
+
16
+ Fresh Windows setup uses `%LOCALAPPDATA%/Rallysmith/data/mailbox`. The macOS default is `~/Library/Application Support/Rallysmith`, and the Linux default is `${XDG_DATA_HOME:-~/.local/share}/Rallysmith`. Setup preserves the saved data location and existing Windows mailboxes at the original location.
17
+
18
+ The Rallysmith desktop dashboard is separate from the Codex and Claude Desktop hosts. It uses WebView2 on Windows, the macOS system webview, or WebKitGTK 4.1 on Linux. The native verification matrix builds the shell, and each advertised platform needs an interactive desktop launch and shutdown check. See the [Tauri system requirements](https://v2.tauri.app/start/prerequisites/#system-dependencies).
19
+
20
+ ## Host capabilities
21
+
22
+ | Capability | Codex Desktop | Claude Desktop local Code chats |
23
+ |---|---|---|
24
+ | MCP startup | `rallysmith codex`, from project workspace | `rallysmith claude`, from project workspace |
25
+ | Manager setup/join | Native review includes names, roster and full rules | The Desktop owner-review connection serves the card. The active manager chat waits for the card decision. |
26
+ | New team members | Native tools open independent chats in same project | Native tools open independent child chats |
27
+ | Binding/onboarding | Saved thread and launch evidence checked | Saved Desktop/Code session and parent/startup evidence checked |
28
+ | Rules/readiness | Each chat adopts its own current revision | Each chat adopts its own current revision |
29
+ | Recovery | Same saved chat recovers its identity | Same saved chat recovers its identity |
30
+ | Automatic wake | Not provided | Not provided |
31
+
32
+ Windows Desktop flows have previous live-chat evidence. macOS Desktop session paths are implemented but require fresh live host qualification. Linux has no claimed Claude Desktop session-record path; independent Claude Code CLI workflows remain distinct. The program does not guess a Desktop binding when host evidence is unavailable.
33
+
34
+ Host plugins bundle MCP configuration and the same five skills. Account-wide npm setup installs a local Codex plugin when the Codex CLI supports it. Native setup supports direct registrations and rejects duplicate plugin routes. Claude Desktop's owner-UI connection can be selected independently on Windows/macOS and is auto-detected when its standard config already exists. Code and owner-UI contexts use the same executable and database. Top-level Desktop chats do not automatically import Code filesystem skills. See [configuration](usage.md#claude-review-connector).
35
+
36
+ Explicit CLI adapters support saved independent Codex/Claude Code sessions and may require operator confirmations. They do not guarantee attachment to an active writer, active-turn steering or sidebar nesting. Optional Codex CLI wake is operator-controlled and rejects Desktop bindings.
37
+
38
+ Readiness means saved bindings and rule adoption, not proof that a chat is running. A stored message cannot wake an idle manager. Use an explicit follow-up when retrieval is needed.
39
+
40
+ ## Release qualification
41
+
42
+ Public npm builds are available for Windows x64 and Linux x64. The checked Linux x64 candidate imports glibc symbols through version 2.34 and requires the system C, math and GCC support libraries. An Alpine/musl build and older distributions are not qualified. Native macOS CI exercises the storage FFI and npm runtime, but does not qualify live Desktop host approvals. Linux mailbox/package checks likewise do not qualify native Desktop host behavior. Keep per-candidate logs and internal qualification records outside the source tree; qualify each native target before adding its release asset.
43
+
44
+ The trust boundary is the local operating-system account. Malicious same-user processes and encryption at rest remain outside the isolation promise. Credentials, live data, diagnostics and private session records do not belong in the package.