Honest paper desk: Signals, Pause vs Flatten, promotion in English - #1
Open
sanjaymaverick-cmd wants to merge 3 commits into
Open
Honest paper desk: Signals, Pause vs Flatten, promotion in English#1sanjaymaverick-cmd wants to merge 3 commits into
sanjaymaverick-cmd wants to merge 3 commits into
Conversation
…glish Paper stays paper. Kite stays disarmed. Header names MOCK capital, mode (Signals / Paper / Paper auto-send / Live locked), ENGINE ON|PAUSED. Pause no longer flattens. Flatten and Reset confirm. Resume is Resume paper — never Arm. Fresh desk boots paused in Signals until Start paper. Paper mode queues Approve / Skip / Size (15s auto-skip). Auto-send is explicit. Signals scan stays live with Would BUY. Book META is n/a until promote. Research returns empty instead of a canned six-pack. Guests cannot drive the shared book. localhost and 127.0.0.1 both sign in.
|
Analysis CompleteGenerated ECC bundle from 1 commits | Confidence: 65% View Pull Request #2Repository Profile
Changed Files (20)
Top hotspots
Top directories
Analysis Depth Readiness (commit-history, 7%)ECC Tools uses this to decide whether recommendations should stay at commit-history/setup guidance or expand into CI, security, harness, reference-set, AI-routing, and team backlog work.
Reference Set Readiness (0/7, 0%)
Likely Future Issues (6)
Suggested Follow-up Work (6)
Copy-ready bodies test: add regression coverage for src/components/auto-engine.tsx + src/components/confirm.tsx ## Summary
- Add regression coverage for the recently touched code paths before more changes stack on top.
## Why
- Backfill regression coverage before another change set lands on the touched code paths.
## Touched paths
- `src/components/auto-engine.tsx`
- `src/components/confirm.tsx`
## Validation
- Add or extend focused tests that exercise the touched paths.
- Run the affected test suite and verify the new coverage closes the gap.test: add integration coverage for src/routes/auto.tsx + src/routes/greeks.tsx ## Summary
- Add integration or end-to-end coverage for the recently changed API surface.
## Why
- Backfill integration or end-to-end coverage for the changed API surface before more contract changes land.
## Touched paths
- `src/routes/auto.tsx`
- `src/routes/greeks.tsx`
## Validation
- Add or extend integration / e2e coverage for the changed API, route, or contract surface.
- Exercise the touched endpoints or route handlers against realistic request / response flows.docs: sync API contract for src/routes/auto.tsx + src/routes/greeks.tsx ## Summary
- Update the API contract artifact that should reflect the recently changed implementation surface.
## Why
- Backfill the missing API contract or spec update before another implementation change lands on top of the same surface.
## Touched paths
- `src/routes/auto.tsx`
- `src/routes/greeks.tsx`
## Validation
- Update the relevant OpenAPI, GraphQL, or contract/spec artifact used by this repo.
- Run the contract validation, docs generation, or API verification flow that depends on that artifact.test: add auth coverage for src/lib/auth/server.ts ## Summary
- Add auth, session, or permission regression coverage for the recently changed security-sensitive surface.
## Why
- Backfill auth or permission regression coverage before another access-control change lands on the touched surface.
## Touched paths
- `src/lib/auth/server.ts`
## Validation
- Add or extend integration / e2e coverage for the changed auth, session, middleware, or permission surface.
- Exercise allowed and denied flows, invalid or expired credentials, or equivalent access-control boundary cases.test: add browser coverage for src/components/auto-engine.tsx + src/components/confirm.tsx ## Summary
- Add browser or end-to-end coverage for the recently changed user-facing surface.
## Why
- Backfill browser coverage before another user-facing UI change lands on the touched surface.
## Touched paths
- `src/components/auto-engine.tsx`
- `src/components/confirm.tsx`
## Validation
- Add or extend browser / e2e coverage for the changed component, page, or flow.
- Exercise the visible user journey that depends on the touched UI surface.security: add scanner evidence for src/lib/auth/server.ts ## Summary
- Add security scanner or code-scanning evidence for the recently changed security-sensitive surface.
## Why
- Backfill explicit scanner or code-scanning evidence before another security-sensitive change lands on the touched surface.
## Touched paths
- `src/lib/auth/server.ts`
## Validation
- Run or add the relevant security scanner, code scanning, secret scanning, or dependency/security review check for the touched surface.
- Attach the scanner output, SARIF/code-scanning result, or focused security regression test to the follow-up PR.
- Confirm the changed auth, billing, webhook, secret-handling, agent, or CI surface has an explicit pass/fail gate.Generated Instincts (7)
After merging, import with: Files
|
Point README, BUILD_PLAN, and a new LINEAGE note at this repo as the only working tree. V3/V4 stay frozen. MeridianV4 is not a working repo.
Owner
Author
|
Identity note added on this branch:
MeridianV4 stays archive. Do not patch V3/V4 trees. |
Operator checkout is D:\work Dir\MeridianFinal-local\MeridianFinal. LOCAL.md and START_HERE point there instead of the old unzip example.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Three-agent paper-desk audit: spectator farm, dead Advisory tape, promotion jargon, Book META 0% + Strong Buy, research
slice(0,6), guest origin lock,:livesuffix. Paper safety (Kite off) held. Mode identity, promotion honesty, hybrid control, and research did not.What
Implements the 19-item UX backlog in docs/UX_BACKLOG.md. Analyzer / paper only. Kite stays disarmed. Never Arm.
Out of scope
Kite remains off. No live orders. Pending queue is paper-only; auto-send is the full-auto path.
Test
npm run typecheckpasses. Sign in (WQ3137/Test@password), confirm header says ENGINE PAUSED, Start paper, then Pause (clips remain) vs Flatten (confirm, clips close).