Dev to main#594
Merged
Merged
Conversation
…velopment for chart; added nodes links
…nd proposed uptime; added node registration time #525: added forum button
Updates/dev update
update: added token price and token price chart for Aztec fix: token price layout fixes
Updates/dev update
fix: fix chatbot urls generations
… 0% APR when indexer brake
updates/dev-update
… to source of proposals as it can be; added button to show/hide full text description of proposal
updates/dev-update
…y to reduce AI generation costs
…ig sizes of proposals texts
updates/dev-update
Added fullstack agent
- Remove inline Instructions from task-execute.yml and task-execute-content.yml that conflicted with agent-specific prompts (fullstack.md, seo-vi.md) - Workflows now only pass TASK + ISSUE + DETAILS + agent file content - fullstack.md: add UI verification, PR description, commit rules, GitNexus + DeepContext with correct roles (semantic search vs code graph), fix Design System delegation, autonomy levels for CI mode, branch handling for reruns - seo-vi.md: add posting logic, labeling, output formats, remove hardcoded chain list, fix tools section with actual posting scripts - CLAUDE.md and AGENTS.md: add DeepContext + GitNexus tool roles to "When to Use What" - Fix .env.local -> .env in both workflows
- Create .claude/agents/seo-cw3.md for Citizen Web3 content agent (separate container, own channels, RAG access, governance focus) - Add anti-slop content quality rules to seo-vi.md and seo-cw3.md - Save design doc to docs/plans/2026-03-19-seo-cw3-agent-design.md
- Add agent-content-cw3 service to docker-compose.yml with own runner, volumes, and CW3-specific social media keys - Update existing agent-content with TWITTER_HANDLE, RAG_API_TOKEN, RAG_API_URL - Add route job to task-execute-content.yml: seo-cw3 → content-cw3 runner - Parametrize TWITTER_HANDLE in post-twitter.js via env var - Add CW3 env vars and RAG config to .env.example
- Collect PR fix history (previous commits + PR comments) for iteration context - Agent identifies NEW vs REPEATED review comments, changes approach for repeated - Load fullstack.md via --append-system-prompt (Skills, Teams, GitNexus workflow) - Iteration 3 (final): agent explains unresolved issues instead of forcing bad fixes - Increase auto-fix limit from 2 to 3 iterations for bot reviews
RAG endpoint: - Create /api/rag/search with token auth and 404 masking - Extract embedQuery into shared embedding-service.ts - Extract formatSearchResults into podcast-service.ts - Fix contextPrefix fallback (was losing CW3 doc context) - Add search-rag.js CLI wrapper for agents - Fix dead code in value-search-service.ts resolveChainTarget - Update CLAUDE.md, AGENTS.md, .env.example Chatbot: - Rewrite system prompt voice: direct, no filler, no corporate tone - Add podcast/knowledge base citation guidelines - Remove verbose rules, tighten language
Prevents CW3 agent from accidentally posting with ValidatorInfo URLs if TWITTER_HANDLE is not set in the container environment.
# Conflicts: # .env.example
Updates/dev update
The delegation color function had green/red swapped — high self-delegation (good) was shown as red and low self-delegation (bad) as green. Now: - < 1000: red (low, risky) - 1000–2000: yellow (moderate) - >= 2000: green (healthy)
…#481) - Add gRPC health checking via TCP connection test (net.Socket, default port 9090) - Add WebSocket health checking via HTTP upgrade handshake - Add Namada indexer-specific health check using /api/v1/chain/parameters - Remove skip for gRPC and WS nodes in health check job - Add MASP indexer and staking interface node types to ChainNodeType - Fetch MASP indexers and staking interfaces from Luminara-Hub registry - Filter staking interfaces by availability status - Support both mainnet and testnet registries - Add UI node type mappings and localization (en, pt, ru)
Add return before resolve in checkWsHealth .catch handler to prevent double-resolve when error matches upgrade/ERR_INVALID_PROTOCOL condition.
feat: update co-create and support text
feat: Data tables color bug
feat: Update infrastructure validators page
- Fix uptime yellow range: was `>= 80 && <= 80` (dead code, only matched exactly 80), now `> 50 && < 80` for proper red/yellow/green bands - Fix WS health check: only accept HTTP 101 (Switching Protocols) as success, remove 200 and 426 which caused false positives with any HTTP server - Remove fragile substring match on 'upgrade' in catch handler, keep only ERR_INVALID_PROTOCOL
Add OAuth 2.0 support for Twitter posting, document the updated credential requirements, make CW3 RAG URL configuration explicit, and restore PR auto-fix for changes-requested reviews. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Updates/dev update
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
3 participants
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.
No description provided.