backend update and fixes

Author: dudcom

Sources/Agentic_System/IkaCore

@@ -0,0 +1 @@
+Subproject commit b2bbef2ec90efe72417fbe6c4554e449b58c0cb3

Sources/Agentic_System/agents/BaseAgent.py

@@ -45,14 +45,14 @@ You MUST use your template tools to compare against existing templates:
 You MUST use RAG DB tools to verify the template aligns with known patterns:
 1. Use `get_runtime_db_ids` to get the list of RAG DB entries for this session
 2. Use `read_rag_db_id` to read relevant entries that contain program template examples, Swift code, FuzzIL code, JS versions, and execution traces
-3. Use `get_rag_doc` to retrieve specific RAG documents that may contain context about the targeted V8 components
+3. Use `search_v8_source_rag_hybrid` to retrieve source context about the targeted V8 components
 4. Compare the generated template against examples in the RAG DB that show successful templates targeting similar components
 5. Verify that the template structure matches patterns that have been proven to work in similar scenarios
 
 ## STAGE 3: V8 TARGETING ACCURACY VALIDATION
 
 You MUST use knowledge base tools to verify V8 targeting:
-1. Use `search_knowledge_base` to search for information about the V8 components, functions, or code paths mentioned in the target context
+1. Use `search_knowledge_base_hybrid` to search for information about the V8 components, functions, or code paths mentioned in the target context
 2. Use `get_knowledge_doc` to retrieve detailed documentation about relevant V8 implementation details
 3. Verify that the template's structure (functions, loops, builds, etc.) would actually exercise the targeted V8 components
 4. Confirm that ProgramBuilder API calls used in the template are appropriate for the intended V8 behaviors
@@ -144,8 +144,9 @@ Your response must follow this JSON structure:
 
 Remember to actively use these tools during validation:
 - Template tools: get_all_template_names, get_template_from_json_by_name, search_template_file_json, search_regex_template_swift, similar_template_swift, search_regex_template_fuzzil, similar_template_fuzzil
-- RAG DB tools: get_runtime_db_ids, read_rag_db_id, get_rag_doc
-- Knowledge base tools: search_knowledge_base, get_knowledge_doc
+- RAG DB tools: get_runtime_db_ids, read_rag_db_id
+- V8 source RAG tools: search_v8_source_rag_hybrid, get_v8_source_rag_doc
+- Knowledge base tools: search_knowledge_base_hybrid, get_knowledge_doc
 - Web search: web_search (when needed for additional V8 or FuzzIL information)
 
 Always ensure your review is thorough, uses available tools, and is constructive. The quality of the generated Swift Program Templates directly impacts the effectiveness of the entire fuzzing campaign.

Sources/Agentic_System/agents/EBG_crash.py

@@ -23,13 +23,13 @@ DO NOT RERUN "get_js_entry_data_by_name" on the entry you got from a get_random_
 ## STAGE 1
 ANALYZE THE DATA ENTRY EXECUTION INFORMATION AND TRY TO THEN SEARCH FOR ADJACENT JS AND FUZZIL CODE USING search_js_file_name_by_pattern. 
 TRY TO CONNECT EXECUTION INFORMATION FROM THE RANDOM DATA ENTRY WITH PARTS OF THE V8 CODE BASE, YOU CAN USE THE VECTOR RAG DATABASE 
-QUERIES TO HELP YOU FIND USEFUL KEY WORDS AND IDEAS. 
+QUERIES TO HELP YOU FIND USEFUL KEY WORDS AND IDEAS. USE `search_v8_source_rag_hybrid` OR `search_knowledge_base_hybrid` FOR THIS. 
 
 ## STAGE 2
 AFTER THAT PLEASE USE THE get_js_entry_data_by_name IN ORDER TO FIGURE OUT THE INTERNAL V8 EXECUTION INFORMATION 
 
 ## STAGE 3
-IN THIS STAGE YOU CAN NOW USE search_knowledge_base AND get_knowledge_doc ON TOP OF get_js_entry_data_by_name WITH THE 
+IN THIS STAGE YOU CAN NOW USE search_knowledge_base_hybrid AND get_knowledge_doc ON TOP OF get_js_entry_data_by_name WITH THE 
 GOAL OF FIGURING OUT A "CODE REGION" OF V8 THAT IS MEANINGFULLY EXPLOITABLE. USE THE EXECUTION DATA FROM THE DATA ENTRIES
 IN COMBINATION WITH THE ASSOCIATED JS AND FUZZIL TO CHOOSE THE CODE REGION.
 
@@ -54,4 +54,3 @@ Here is the JSON object THAT YOU MUST FOLLOW please make sure to include all sec
 
 
 
-

Sources/Agentic_System/agents/EBG_plateau.py

@@ -16,7 +16,7 @@ NEVER GENERATE MORE THAN ONE PROGRAM TEMPLATE AT A TIME. ALWAYS MAKE SURE THE `c
 ## STAGE 0
 GO THROUGH THE RAG DB WITH ALL THE PROGRAM TEMPLATE EXAMPLES, THEY HAVE PROGRAM TEMPLATE SWIFT CODE BUT ALSO THE RESULTING FUZZIL CODE
 AS WELL AS THE JS VERSION AND EXECUTION TRACE FROM THE V8 ENGINE. THIS SHOULD GIVE YOU A STARTING POINT REGARDING GENERATING A 
-PROGRAM TEMPLATE YOURSELF. PLEASE USE THE VECTOR RAG DB AS YOU NEED TO QUERY INFORMATION REGARDING THE V8 CODE BASE AS WELL AS JS MDN DOCUMENTS. 
+PROGRAM TEMPLATE YOURSELF. USE `search_v8_source_rag_hybrid` AND `search_knowledge_base_hybrid` WHEN YOU NEED SOURCE OR DOC CONTEXT. 
 FINALLY AFTER YOU HAVE CREATED A PROGRAM TEMPLATE SEND YOUR CODE TO THE VERIFICATION AGENT "GEORGE FOREMAN"
 
 MAKE SURE THE PROGRAM TEMPLATE NAME YOU PROVDE DOESN'T ALREADY EXIST BY RUNNING `list_program_templates` TO RETRIEVE THE EXISTING PROGRAM TEMPLATE NAMES LOCATED IN `ProgramTemplates.swift` and `ProgramTemplateWeights.swift`.
@@ -699,4 +699,4 @@ public let ProgramTemplates = [
         // Generate some more random code to (hopefully) use the parsed JSON in some interesting way.
         b.build(n: 25)
     },
-]
+]

Sources/Agentic_System/agents/FoG.py

@@ -56,9 +56,9 @@ If the FULL ANSWER lacks detail, doesn't identify specific code blocks, or shows
 ## STAGE 3: CODE BLOCK VERIFICATION USING TOOLS
 
 You MUST use your available tools to verify the identified code blocks:
-1. Use `search_rag_db` to find relevant information about identified code blocks
-2. Use `get_rag_doc` to retrieve specific RAG database entries referenced in the analysis
-3. Use `search_knowledge_base` to verify understanding of V8 components, functions, or concepts mentioned
+1. Use `search_v8_source_rag_hybrid` to find relevant V8 source chunks for identified code blocks
+2. Use `search_knowledge_base_hybrid` to verify understanding of V8 components, functions, or concepts mentioned
+3. Use `get_v8_source_rag_doc` to retrieve full chunk sequences for specific files when needed
 4. Use `get_knowledge_doc` to retrieve detailed V8 documentation for identified code regions
 5. Use `ripgrep` or `fuzzy_finder` to locate and verify identified code blocks in V8 source if needed
 6. Use `web_search` if additional information about V8 engine behaviors is needed for validation
@@ -121,7 +121,7 @@ For an analysis to be APPROVED, it must:
 When providing feedback (especially for REJECTED cases):
 - Be specific about what aspects of GOAL or FULL ANSWER need improvement
 - Reference specific identified code blocks that need better explanation
-- Point to RAG DB entries or knowledge base documents that should be consulted
+- Point to V8 source RAG chunks or knowledge base documents that should be consulted
 - Suggest specific functions, concepts, or areas to investigate in Stage 3
 - Provide examples of what a strong analysis should look like
 - Guide code_analyzer to re-query v8_search with more targeted TASK/REASON if needed

Sources/Agentic_System/prompts/FoG-prompts/george_foreman.txt

@@ -7,7 +7,7 @@ partially random FuzzIL code which will then be used in a complex fuzzing campai
 The point of making these custom Agentic Program Templates is to provide a level of directed fuzzing.
 
 
-THIS IS NOT AFL+++, THERE ARE NO HARNESSES, PROGRAM TEMPLATES ARE AN INTERNAL COMPONENT OF FUZZILLI. PLEASE USE THE search_knowledge_base TO UNDERSTAND THEM.
+THIS IS NOT AFL+++, THERE ARE NO HARNESSES, PROGRAM TEMPLATES ARE AN INTERNAL COMPONENT OF FUZZILLI. PLEASE USE THE search_knowledge_base_hybrid TO UNDERSTAND THEM.
 
 ## CRITICAL RULES:
 
@@ -122,4 +122,3 @@ public class ProgramTemplate: Contributor {
         f(b)
     }
 }
-